Per-channel effective capabilities + provider manifests
/capabilitiesAuthorization
bearerAuth In: header
Query Parameters
Organization slug (OAuth actors with several orgs); API keys imply theirs.
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/capabilities"{ "property1": null, "property2": null}{ "error": { "code": "string", "message": "string", "reason": "string", "index": 0, "request_id": "string" }}{ "error": { "code": "string", "message": "string", "reason": "string", "index": 0, "request_id": "string" }}Turn picked destinations into publishable channels POST
Previous Page
List posts (keyset paginated) GET
Newest first, keyset-paginated via `next_cursor`. Narrow with `statuses`, a scheduled-time range, `campaign`, `label`, or `channel` (a channel id or a provider name like `linkedin`) — so "my scheduled LinkedIn posts" is one call, not a range pulled down and filtered locally. Rows are excerpts and carry no fit verdict unless you ask: `include=ready` adds `ready` per row — absent means "not checked", which is not the same as `false` — and caps the page at 25, because each judged row then costs a full post read. Read one post in full with `GET /posts/{id}`.