Skip to main content
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

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

Response headers

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. 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.