---
title: "Rate limits"
method: GET
path: "/guides/rate-limits"
tags: ["Rate limits"]
---

# Rate limits

`GET /guides/rate-limits`

## Request

- Base URL: `https://developers.chatway.app/api/v1`
- URL: `https://developers.chatway.app/api/v1/guides/rate-limits`
- Auth: none required

# Rate limits

The Chatway API enforces per-key rate limits to keep the platform stable for all customers.

## Limits

| Limit | Window | Scope |
|---|---|---|
| **60 requests** | Per minute | Per API key |

Every authenticated API request counts toward the limit for the key used in the `X-API-KEY` header.

## When you exceed the limit

Requests over the limit receive:

```
HTTP/1.1 429 Too Many Requests
```

The response body includes a JSON error message. When provided, honor the **`Retry-After`** header (seconds until you should retry).

Example response:

```json
{
  "message": "Too many requests."
}
```

The response may include a **`Retry-After`** header (seconds until you should retry).

## Recommended client behavior

Pace requests across all workers using the same API key. On a `429` response, wait at least the number of seconds in `Retry-After` when that header is present. Otherwise, increase the delay between retries and add a small random delay so workers do not all retry together.

Set a maximum retry count. Cache reusable read results and use webhooks for new-message notifications instead of frequent polling.

Use separate keys to identify integrations and manage their access. Keep each integration within its documented quota.

Be careful when retrying writes after a timeout or connection failure. Check whether the message, invitation or change already exists before repeating the request. This guide does not document duplicate protection for repeated writes.

## Webhooks vs polling

Webhook deliveries are separate from REST API rate limits. Design integrations to react to webhook events rather than calling list endpoints on a short interval.

## Related pages

- **Testing the API**: safe ways to exercise endpoints without hitting limits unexpectedly.
- **Errors**: full error body reference, including `429` and `Retry-After`.
- **Customer support**: include timestamps and paths if you believe a limit was applied incorrectly.

## Response `200`

Documentation.

---

[API](https://skmtc.dev/chatway/apis/chatway-developer-docs.md) · [All operations](https://skmtc.dev/chatway/apis/chatway-developer-docs/llms.txt) · [OpenAPI document](https://skmtc.dev/chatway/apis/chatway-developer-docs/revisions/ca1a1da291cc?raw)