Developers
Run it from a script,or from Claude.
Everything you can do in the app, you can do over HTTP. There is also an MCP server, so Claude can draft ideas, schedule posts and read your results using a key you control.
How will you connect?
API and MCP access come with Pro and above.
$ REST API
JSON over HTTPS with a bearer key. The OpenAPI document is available to any key holder, so you can generate a client or paste it into a tool.
Keys with roles
Create a key per use. Give it a role (admin, editor or viewer) and limit it to some brands. An editor key’s publishes go through approval if you require it.
Rate limits by plan
Requests per minute scale with the plan, and you get a clear 429 with a Retry-After header, not silent failures.
Honest errors
A plan limit returns 402 with the metric and the limit. Another workspace’s record returns 404, the same as a missing one.
OpenAPI spec
Fetch /api/openapi.json with your key.
Same rules as the app
Plan allowances, approvals and platform limits apply to API calls exactly as they do in the app.
Hashed keys
Keys are stored only as a hash. You see a key once, when you make it.
Use it from Claude
Add the MCP server once and Claude can work in your workspace with the permissions of the key you give it.
API keys
One command to add it
claude mcp add --transport http anyposter \
https://your-workspace.example/api/mcp \
--header "Authorization: Bearer syn_..."Automation without surprises
A key per job
Revoke one integration without touching the others.
Approvals still apply
An editor key’s posts wait for an owner if your workspace requires approval.
Allowances still apply
API and Claude use count against the same plan limits as the app, so a runaway script cannot run up a bill.
Get a key in five minutes
Pick a plan, open Settings, create an API key and make your first request.