Skip to main content
The REST API enforces limits at three levels so one account can’t starve another and the platform stays within OnlyFans’ tolerances. Your exact limits depend on your plan. Read them live:
The response includes current usage plus each window’s limit, remaining, and reset (Unix seconds):

When you hit a limit

You receive a 429 with an RFC 9457 problem body and a Retry-After header:
Branch on retryable and wait retryAfterSec before retrying. The reason field tells you which limit you hit (org_rpm, account_write_rpm, …).

Upstream rate limits

OnlyFans itself may rate-limit a busy account. When it does, the platform relays it as a 429 problem with code: "upstream/rate-limited" and a retryAfterSec. Treat it the same way — back off and retry.
Spread bursty work (mass DMs, bulk fetches) over time and honor retryAfterSec. A steady call rate is both faster overall and safer for the connected account.