Skip to main content
PostlyBee applies one shared limit to the Public API to protect workspace publishing, provider capacity, and account data.

​
Current limit

Workspace resource endpoints allow 100 requests per workspace in a one-hour window. GET /public/v1/workspaces uses the same limit per API token. The tracker uses the workspace ID embedded in the request path. Different workspaces do not share a counter, but all tokens targeting the same workspace consume the same workspace allowance. Workspace discovery has no target workspace, so its counter uses the token ID.

​
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