Skip to main content
A linked account is one OnlyFans account. When an owner approves access, they choose the accounts and permissions to share with your app. OFAuth saves this approval as an authorization. Each Access request works with one linked account. All routes on this page use an access token sent as Authorization: Bearer <access_token>. Each route returns only accounts shared through that token’s authorization. No route lists accounts from all authorizations.

Where linked account ids come from

The same OnlyFans account in Sandbox, Test, and Live has different ids.

List linked accounts

Accounts are ordered by id. A bad limit or cursor returns 400 invalid_request.

Get a linked account

Returns one account with the fields shown above. An account ID that is not part of this authorization returns 404 linked_account_not_found with recovery.action list_linked_accounts.

Remove a linked account

Removes this authorization’s access to one account and returns 204. The account itself, the rest of the authorization, and other apps’ access are unaffected. Repeating the call succeeds. Your webhook destinations receive linked_account.disconnected with reason: "developer_deleted". To end the whole authorization instead, revoke its sessions.

Reconnect a linked account

Use client.linkedAccounts.createReconnect({ id, body: { redirect_uri, state } }) to create a short-lived journey for an account that needs reconnecting. Open the returned url, verify the app session and state on return, then read current account status. See Handle account reconnects.

Linked account settings

Use the API to manage settings for each account, such as Vault+.
PATCH accepts vault_plus.enabled, vault_plus.overrides, or both, and returns the updated settings. Send only the settings you want to change:
Set an override field to null to use the integration setting again. Set "overrides": null to clear all account overrides. The PATCH reference lists the supported settings.
  • PATCH needs the vault:write scope on that account, or it returns 403 missing_scope.
  • Vault+ must be on for the environment. Test accounts need a paid Developer plan (403 subscription_required).
  • Sandbox accounts always have Vault+ on. PATCH in Sandbox returns 409 linked_account_settings_fixed.
  • If another request changes the settings at the same time, the API returns 409 linked_account_settings_conflict with recovery.action retry.
See Vault+.

Linked account status

Select a linked account

Send the linked account id on every Access and Vault+ call.
Missing header: 403 linked_account_required. An account that is not part of this authorization: 403 linked_account_not_granted. See Errors.

Several accounts per authorization

One authorization can cover several linked accounts, for example an agency that manages several creators. Save the account IDs under their authorization_id. Let the user choose which account to use. The access token works for every account in the authorization; only the header changes. Keep your list current with account and access events: authorization.updated reports added and removed accounts, and linked_account.disconnected reports a single removed account.