Skip to main content
Link opens an OFAuth page where an account owner signs in, selects accounts, and approves your app’s permissions. Your backend (your app’s server) receives tokens to work with those accounts. For your first API request, start with the Quickstart.

Understand the access you receive

A linked account is an OnlyFans account shared with your app. An authorization records the accounts and permissions an owner grants. One authorization can include several accounts. Save the authorization, tokens, account IDs, and environment under the signed-in user in your app who started the request. An account ID alone does not grant access. Use a standard OAuth adapter or the OAuth helper. Your application owns session-bound callback state and ordinary token persistence. If you use Better Auth, follow Generic OAuth configuration. The owner approves accounts and permissions. Your backend checks the callback, exchanges its code, and selects a shared account for API requests.
  1. Build an authorization URL with your registered callback URL and the permissions your feature needs.
  2. Open the URL in the user’s browser.
  3. Complete the callback with the current app user and browser session. Check that they match the session that started the request before consuming state.
  4. Exchange the one-use code and save the tokens under that customer registration.
  5. Let the user choose from the linked accounts.
Keep your client secret and tokens on the backend. For mobile apps, follow native app callbacks.

Make a request

Use the access token and the ID of an account shared by that authorization:
The owner must have approved the operation’s permissions.

Keep access working

Every successful code exchange includes a refresh token. Refresh tokens to keep that access without asking the owner to sign in again. Ask for additional access when your app needs more accounts or permissions. If the OnlyFans session expires, ask the owner to reconnect the account. Guest account connection does not require an OFAuth signup or fabricated verified email. Profile-based linking has separate identity requirements. Owners grant account access, never an Operator subscription. Your application’s Developer entitlement pays for the delegated requests.