Skip to main content
Use linked accounts to track the OnlyFans accounts shared with your app. Each account belongs to its owner. An authorization records the accounts and permissions that the owner approved.

Map accounts to your users

Start authorization while the user is signed in to your app. Save the pending state value under that user. After exchanging the code for tokens, save the credentials and environment under the same user. Fetch account IDs through List linked accounts, following every page. authorization_id is optional in a token response; use GET /v3/authorization when your application needs the authorization resource. Do not use the callback as an account list. The callback returns a code and state. Account IDs come from linked-account routes and lifecycle events. A signed-in application user can have an authorization containing several shared accounts. Store those accounts under the authorization and select one linked account per API request.

Keep the identifiers distinct

In chat routes, the recipient’s OnlyFans ID identifies the fan. It is separate from the linked account ID that selects the creator sending the message.

Read current account state

For an account’s full record, use GET /v3/linked-accounts/{id}. The linked-account reference defines pagination, fields, settings, and status values.

Keep account access current

Subscribe to account and access events to track removed accounts, expired sessions, and revoked authorizations. Fetch the linked-account list again when you need current status or permissions. Follow Handle account reconnects when an account expires. Follow Request more access when a feature needs additional scopes or accounts.

Remove a shared account

A successful call returns 204. This removes the account from the current authorization. The owner’s account and other applications’ access remain. To end an OAuth credential, use revocation.