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

# Rate limits

> Limits and how to handle 429 responses.

Rate limits are policy-driven by route and authenticated caller. A route without
an active policy is not rate limited. Configured limits may differ between read
and write operations, so do not build against a single global
requests-per-second value.

When a limit is exceeded, Slash returns HTTP `429` with a plain-text body.

## Client behavior

1. Stop sending immediate retries.
2. Retry with exponential backoff and random jitter.
3. Cap concurrent requests and increase concurrency gradually.
4. Use cursor pagination rather than issuing parallel requests for every
   resource id.

A `429` response is returned before a create operation consumes its
`X-Idempotency-Key`, so the request can be sent after backoff with that key. If
the connection fails without a response, do not assume the key remains
available: follow the [idempotency guidance](/docs/v2/get-started/idempotency)
and reconcile through the resource's list and retrieve endpoints.