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

# Rate limiting

> How request limits work and when to try again.

OFAuth limits how many requests you can make. Available requests return steadily over time, up to the maximum. You can use them in a short burst.

## Request limits

| Request type | Shared by | Limit |
| - | - | - |
| Token and revoke requests | Client IP address | Up to 120 requests, restored steadily over 60 seconds. |
| Failed client authentication | Client ID | After 10 failed checks of your app's ID and secret in 10 minutes, requests are blocked until that window ends. A successful check clears the failure count. |
| Linked-account and Access requests | Authorization and environment | Up to 600 requests, restored steadily over 60 seconds. Sandbox is included. |

OnlyFans also has its own limits. Accounts shared through the same authorization use the same OFAuth request limit.

## Response headers

| Header | Meaning |
| - | - |
| `RateLimit-Limit` | Maximum number of available requests. |
| `RateLimit-Remaining` | Number of requests still available after this call. |
| `RateLimit-Reset` | Seconds until all available requests have been restored. |
| `Retry-After` | Seconds before retrying a rejected request. |

When you use all available requests, the API returns `429`, `error: "rate_limited"`, and `recovery.action: "retry"`. Token and revoke endpoints use OAuth error fields instead. See [Errors](https://docs.ofauth.com/v3/api-reference/errors.md).

Wait for the delay given in `Retry-After`. `RateLimit-Reset` tells you when all available requests return. It does not tell you to retry sooner.

## Daily Test limit

Test also limits how many Access operations you can use each day. When you reach that limit, the API returns `429 quota_exhausted` with `recovery.action: "retry_after_reset"`. `Retry-After` gives the seconds until the daily UTC reset. This limit is separate from the request limit above.

## Reduce rejected calls

Wait for `Retry-After` before trying again. Add a small random delay so app instances do not all retry at once. If no delay is given, limit attempts and wait longer after each failure. Save repeated read results and spread out background work to avoid bursts.

If a network error leaves you unsure whether a change succeeded, check its result before sending it again. See [error handling](https://docs.ofauth.com/v3/reference/error-handling.md).


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