Social API

The Social Planner manages a subaccount’s connected social channels and scheduled posts. Per-platform OAuth is brokered by Postiz in its own UI — the CRM holds no platform tokens. Endpoints are under /api/v1/social and are org-scoped via X-Org-Id.

Connected accounts

Method	Path	Description
GET	/social/accounts	The org’s synced channels, a Postiz connect deep-link, and a configured flag.
POST	/social/accounts/sync	Pull channels from Postiz and upsert one row per channel (platform-normalized).
DELETE	/social/accounts/{account_id}	Forget a channel locally (does not disconnect inside Postiz).

POST /social/accounts/sync returns 503 when Postiz is not configured and 502 on a Postiz error. Vanished integrations are marked inactive (kept, not deleted).

Posts

Method	Path	Description
GET	/social/posts	List scheduled / posted posts.
POST	/social/posts	Create a post (201).
PATCH	/social/posts/{post_id}	Update a post.
DELETE	/social/posts/{post_id}	Delete a post.

A scheduling beat publishes due posts via Postiz, resolving each channel’s integration id. A post fails cleanly (without crashing the batch) when no account is connected for its platform.

Note

Postiz deployment and the per-platform OAuth apps are an operator setup step. Until a channel is connected in Postiz, the planner can hold a draft but cannot publish it.