Skip to main content
Your backend is the server that runs your app’s private code. It sends an access token to prove that your app has permission to make a request. OAuth is the process that asks an account owner to approve this access. The owner chooses which accounts and permissions to share. OFAuth saves that approval as an authorization. Follow Connect an account to get tokens and linked account IDs.

Headers

The SDKs send these headers for you. Set the access token and linked account when creating the client:
The account ID selects an account. The token grants access. An account ID alone does not authorize a request. Linked-account management routes identify the account in the URL and need only the bearer token. To get or revoke tokens, your backend sends its client ID and secret using client_secret_basic or form client_secret_post, one method per request. It sends form fields, not JSON. See Tokens and refresh.

Access tokens

Access tokens are opaque and expire after 15 minutes. Code exchanges include a stable client-bound refresh token. Independent servers can refresh concurrently and retry a lost refresh response. See Tokens and refresh.

Scopes

A scope names a permission, such as messages:read. Read and write scopes are separate. Request both when your feature reads and writes a resource. An inbox that reads conversations and sends messages requests both messages:read and messages:write. Write access does not include read access. Request only the scopes you need. The user sees each permission on the approval screen. identity:read grants the person’s OFAuth profile. This scope does not grant an OnlyFans account action. Each operation’s reference page shows its required scope. The OAuth discovery document lists every supported scope in scopes_supported.

Missing permissions

missing_scope means the token does not include a required scope. additional_consent_required means the selected account has not granted it. Follow Request more access to ask the owner to approve the required scopes. Keep credentials and accounts separate by environment. See Security for storage and callback requirements.

Developer and Operator authority

Developer OAuth connects other people’s accounts using the application’s Developer entitlement and billing. Owners need no Operator subscription. Losing only an owner’s Operator plan does not end Developer grants. Operator requests share Access URLs and methods but use the authorized holder’s Operator allowance, exact accounts, live membership, capabilities, and confirmations. Operator authority excludes Realtime and Vault+. OnlyFans vault operations in Access are distinct from Vault+. The account header selects a resource and cannot choose the payer. An MCP token needs the correct API audience; recognizing its issuer alone does not authorize API access.