Skip to main content
PostlyBee limits high-impact Public API routes to protect workspace publishing and media capacity.

​
Current limit

The following route families allow 100 requests per workspace in a one-hour window:
  • /public/v1/posts
  • /public/v1/posts/*
  • /public/v1/upload
  • /public/v1/upload-from-url
The tracker uses the authenticated workspace ID, so different API keys for different workspaces do not share a limit. Account discovery and connection-check endpoints are not currently counted against this limit.

​
Response headers

Rate-limited responses include:

​
Exceeded limit

When the limit is exceeded, the API returns 429 Too Many Requests. Wait for the number of seconds in Retry-After before sending another request.
Posting quotas imposed by a subscription plan and third-party social platforms are separate from the Public API request limit.

​
Reduce request volume

  • Create posts for several destinations in one create-post request.
  • Reuse the result of the connected-accounts request instead of fetching it before every post.
  • Upload each media file once and reuse its returned media object.
  • Apply backpressure in queues so retries do not arrive in a burst.
Last modified on August 26, 2026