Rate Limits
Every plan, including Free, includes unlimited PostBoost API calls: there are no per-request fees and no monthly call quota. Posts published to X (Twitter) count against a monthly X allowance, because X charges for every post.
Current limits
| Plan | API calls | Notes |
|---|---|---|
| Free | Unlimited | Fair use policy applies |
| Pro | Unlimited | Fair use policy applies |
| Pro Max | Unlimited | Fair use policy applies |
| Agency | Unlimited | Fair use policy applies |
On every plan the API accepts up to 60 requests per minute (counted per signed-in user, or per IP address); a request over that gets a 429. Scheduled posts also have a daily cap per account and network, below each network's own limits: see Agent guardrails.
For high-volume automation (thousands of requests per minute), contact us to confirm your use case has sufficient headroom.
Free Tools API limits
The Free Tools endpoints (/tools/...: character counter, thread maker, UTM builder and the other free tools) work without a token. They have their own limits:
| Caller | Per minute | Per UTC day |
|---|---|---|
| No token (per IP address; IPv6 per /64) | 30 | 500 |
| API token, Free plan (per user) | 300 | 1,000 |
| API token, paid plan (per user) | 300 | No daily cap |
Tools that fetch a web page allow 20 calls per day without a token and 200 with one. AI tools need a token and use your workspace's AI credits.
Every response carries X-RateLimit-Limit and X-RateLimit-Remaining for the limit closest to running out. A 429 response adds a Retry-After header and a JSON body with retry_after (seconds), plus register_url (no token: sign up for higher limits) or upgrade_url (Free plan daily cap reached).
Platform-level limits
Note that individual social platforms impose their own publishing rate limits (e.g., Instagram limits posts per account per day). PostBoost respects these limits and will return an error if a platform-level limit is reached. These are separate from PostBoost API rate limits.
X (Twitter) allowance
X bills every post created through its API, and a post with a link costs about 13 times a plain one. Each plan therefore includes a monthly number of X posts and X posts with a link. Check usage with GET /{workspaceUuid}/usage/x; the full rules are in the X policy.
Best practices
- Use the queue —
"queue": truelets PostBoost distribute posts at optimal times, naturally staying within platform limits. - Batch media uploads — upload media assets before creating posts to avoid waterfall requests.
- Webhook-driven workflows — avoid polling post status; subscribe to webhooks instead.
Error response
If a rate limit is ever exceeded, PostBoost returns:
{
"message": "Too Many Requests."
}
with HTTP status 429. Back off and retry after the Retry-After header interval.