> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/developers/api-reference/rate-limits.md).

# Rate limits

Every API key is assigned a **rate-limit tier**. Limits are per-key, per-rolling-60-second window.

## Tiers

| Tier        | Requests per minute |
| ----------- | ------------------- |
| `standard`  | 60                  |
| `premium`   | 300                 |
| `unlimited` | 10,000              |

Your tenant admin assigns a tier when issuing the key.

## Headers

Every response includes:

| Header                  | Meaning                                         |
| ----------------------- | ----------------------------------------------- |
| `X-RateLimit-Limit`     | Your bucket's max for the current window        |
| `X-RateLimit-Remaining` | Requests left in the current window             |
| `X-RateLimit-Reset`     | Unix timestamp (seconds) when the bucket resets |

## When you exceed the limit

You get `429 Too Many Requests`:

```json
{ "error": "Rate limit exceeded. Try again later." }
```

`X-RateLimit-Reset` tells you when to retry. Sleep until then, then retry.

## Best practices

* Honor `Retry-After` when present.
* Cache `GET /api/v1/manifest`, `/catalog`, `/capabilities`, and `/pricing/resolve` responses for at least 60 seconds — they don't change often.
* For batch jobs, prefer fewer, larger calls — use filter parameters (e.g. `?status=active`, `?accountId=...`) on list endpoints to fetch the rows you need in one request rather than many small ones.
* Webhook deliveries do not consume your API rate limit.

## Tier upgrades

Ask your account team to lift your tier. Justify the request with expected RPS and burst patterns; we are happy to right-size.

## Related

* [Authentication](/developers/api-reference/authentication.md)
* [Errors](/developers/api-reference/errors.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/developers/api-reference/rate-limits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.