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

# Rate limits

> Understand limits and implement safe, jittered backoff.

Current default authenticated limits are measured per endpoint, independently for the business and API key.

| Operations | Requests per 60 seconds |
| - | -: |
| Most customer, account, and transaction reads | 600 |
| Customer and account writes | 120 |
| Transfer destinations, recipients, FX quotes, previews, and transfers | 120 |

Authentication also has separate IP and credential limits. A request must pass every applicable limit.

```json theme={null}
{
  "statusCode": 429,
  "message": "Too many API requests. Try again later.",
  "code": "api_key_rate_limit_exceeded",
  "retryAfterSeconds": 17
}
```

<Warning>
  The current implementation does not set the standard `Retry-After` response header. Read `retryAfterSeconds` from the JSON body until the public header contract is decided.
</Warning>

Wait at least the indicated number of seconds, add random jitter, then retry. Cap concurrency and backoff centrally so parallel workers do not create a retry storm. Rate-limit storage fails closed; an unavailable limiter may return `api_key_rate_limit_unavailable` rather than permitting unmetered traffic.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.