> ## Documentation Index
> Fetch the complete documentation index at: https://docs.postlybee.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rate limits

> Understand the one-hour workspace limit for posts and media uploads.

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:

| Header                  | Description                                |
| ----------------------- | ------------------------------------------ |
| `X-RateLimit-Limit`     | Maximum requests in the current window.    |
| `X-RateLimit-Remaining` | Requests remaining before throttling.      |
| `X-RateLimit-Reset`     | Seconds until the current counter expires. |
| `Retry-After`           | Seconds to wait after receiving a `429`.   |

## 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.

<Note>
  Posting quotas imposed by a subscription plan and third-party social platforms
  are separate from the Public API request limit.
</Note>

## 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.