Base URL and auth
Ids
Profiles, accounts, posts and engagement items return their id as_id.
Conversations and messages return it as id. Single resources come wrapped
in a key named after them ({ "post": { … } }, { "account": { … } }); lists
come as a named array, plus pagination on paginated lists
({ "posts": [ … ], "pagination": … }). Conversations use data instead of a
named array.
Unknown fields are rejected
Request bodies are validated strictly. A field the endpoint doesn’t know — a typo, or an option from another endpoint — returns400 with
code: "validation_failed" instead of being silently ignored. The
API Reference lists the accepted fields of every endpoint.
Errors
Every error, whatever the status, has the same body:Pagination
List endpoints takepage (from 1) and limit (default 20, max 100) and return:
pagination.nextCursor as before to get the next
page.
Idempotency
Send anIdempotency-Key header (any unique string, e.g. a UUID) to make a
retry safe. A second request with the same key gets the first response back
instead of acting twice. Keys are kept 24 hours. Reusing a key with a
different body is refused.
Supported on the calls that act on a platform:
POST /postsPOST /posts/{id}/publishPOST /inbox/conversations/{id}/messages
Rate limits
Limits apply over a one-minute window, per connected account when the request targets one (anaccountId in the path, query or body, the targets of a
post, the account of a conversation), and per PlugKit account otherwise (all
your keys together):
Every response carries
x-ratelimit-limit, x-ratelimit-remaining and
x-ratelimit-reset (Unix seconds). A 429 carries retry-after (seconds) and
details.scope (account or user). A post published to several accounts
counts once on each of them.
On top of these, each platform enforces its own quotas (for example 100
Instagram publications per account per 24 hours). A platform quota error comes
back as a 429 with retry-after when the platform says how long to wait.