Skip to main content
Use the V3 API to read data and take actions on OnlyFans accounts shared with your app. A linked account is an account its owner has shared. An authorization records the accounts and permissions that owner approved.

Base URLs

Your app’s client ID and secret select its mode: Sandbox, Test, or Live. Changing the hostname does not change that mode. See environments.

Authenticate requests

Use an official SDK for your application. Get an access token through authorization. The token proves your app has permission. For Access and Vault+ requests, send the token and the ID of an account shared with it:
To manage linked accounts, select the account in the URL and send the token in the Authorization header. Each operation lists the permissions it needs, called scopes. See authentication and permissions.

Use the right access details

The token endpoint checks your app’s client ID and secret. Access requests check the access token returned by sign-in. Use the format listed above for each request.

Find an operation

Dynamic Rules provides the values needed to sign requests sent directly to OnlyFans.

Account: shared linked accounts

The Account API lists and manages accounts shared through the same authorization as your token. You cannot use it to access another authorization’s accounts. Send the token in the Authorization header and select an account in the URL when required. See Linked accounts for list, read, removal, settings, pagination, and status fields. Follow Authorize for request and callback fields and Tokens and refresh for token responses, refresh, and ending access.

Access: account operations

Access operations use /v3/access/* for profiles, chats, subscribers, users, posts, stories, media, earnings, promotions, and queued content. Each reference lists the HTTP method, permissions, input fields, and response. Send only the input fields listed for the operation. Protected media may include a playback descriptor. Follow Play DRM video for player setup and renewal.

Read responses

Each operation’s reference shows its response fields. Profile reads and requests that create an item return the object directly. Access lists usually return items and page. Linked-account lists return data, has_more, and next_cursor. See Pagination to read every page. Media URLs expire. Read the post, message, or media item again to get fresh URLs. Save media IDs when you need to find the same item later.

Handle errors and limits

Access, Vault+, and linked-account errors include error, recovery.action, and requestId. Read recovery.action to choose the next step. Save x-request-id from the response headers if you need support. OAuth endpoints return different error fields. See error codes and Handle failed requests. If you hit a rate limit, wait for the time given in Retry-After. If a network error leaves you unsure whether a change succeeded, check its result before you send it again. For a complete app example, follow quickstart.