Skip to main content

​
API key authentication

REST API requests use an API key passed via the X-API-Key header. MCP clients can use an API key or user-approved OAuth with PKCE. AI agents can start with Auth.md for OAuth discovery, client registration, user consent, token refresh, and CLI API-key provisioning.

​
Generate an API key

1

Log in to your dashboard

Go to Social media studio and log in.
2

Open API settings

Navigate to Settings > API tab.
3

Create a new key

Click New API Key, give it a name, and copy the key.
The full key is shown only once. Store it securely. If you lose it, revoke the key and create a new one.

​
Permissions

Only workspace owners can create, list, and revoke API keys. A key acts on behalf of the workspace it was created in, scoped to that workspace’s data. If an owner leaves or their access changes, revoke and reissue any keys they created.

​
Using your API key

​
REST API

Pass the key in the X-API-Key header:

​
MCP Server

The MCP server uses the same API key. Pass it in the X-API-Key header of your MCP configuration:

​
Plan requirements

API and MCP access is available on the Standard, Advanced, and Lifetime plans. The Free and Lite plans do not include API access. For full plan details, see Billing overview.

​
Rate limiting

API requests are rate-limited per workspace, with the exact limit determined by your plan. When you exceed the limit, you’ll receive a 429 Too Many Requests response — wait for the window to reset and retry. MCP tool calls also consume credits based on your plan. Check your usage in Settings > API, and see AI credits for how credits work.
Higher-tier plans get higher rate limits and monthly API usage allowances. See Billing overview for the limits that apply to your plan.