List connected channels
List the org's connected channels (mediums). Use a returned `id` as the key in a scheduled post's `channels` map. With the optional `workspaceId` filter only the channels connected to that workspace are returned (the discovery step for the workspace-scoped VIP routes). Tokens are never returned.
/channelsAuthorization
x-api-key x-date x-signature Your API key (the ApiKeys document id).
In: header
Current timestamp in ISO-8601 (must be fresh — within −5s..+60s of server time).
In: header
HMAC-SHA256 of the x-date string keyed by your secret, lowercase hex.
In: header
Query Parameters
Restrict to the channels connected to this workspace.
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/channels"[ { "id": "string", "type": "FB_PAGE", "name": "string" }]{ "message": "string"}{ "message": "string"}{ "message": "string"}List accessible organizations
List the organizations the caller can access. For an API-key caller this is the single org the key belongs to. Supports an optional case-insensitive `q` name filter and a `limit` cap, both applied in memory. This is the org-discovery entrypoint and does not require an organization to be in scope.
List published posts
List posts already live on a channel, most recent first, with engagement metrics and the full attached superpower (or `null`). Only genuine published page posts are returned — those the channel itself authored and published, matching what the in-app feed shows; ads, unpublished/dark posts, and visitor posts are excluded. Published posts are stored per channel: pass `mediumId` to scope to one channel, or omit it to aggregate across all channels (merged, newest first). Optional `type`, `startDate`, and `endDate` filters are applied in memory before the limit.