Skip to main content
Connect OnlyFans accounts to your platform securely. OFAuth handles credentials on hosted pages—you receive a Connection ID for API access.
Use Sandbox for testing! Before testing with real OnlyFans accounts, use Sandbox test credentials. Too many login attempts on production accounts can trigger OnlyFans “suspicious activity” detection.

Choose Your Integration

Redirect Flow

Redirect users to OFAuth’s authentication pages. Simple to implement.

Popup Flow

Show authentication in a popup. Best user experience.

How It Works

  1. Create a Link session with your redirect URL
  2. Redirect the user to OFAuth’s secure authentication page
  3. User authenticates on OFAuth (2FA and captcha handled automatically)
  4. Receive Connection ID via callback URL or webhook

Prerequisites

1

Complete Platform Profile

Set up your platform profile (app name, description, website, privacy policy) in the OFAuth Dashboard.
2

Create a Client App

Create a client app in Dashboard > Client Apps. Choose your app type (Redirect, Embed, or Whitelabel) and configure allowed redirect URIs or origins. Copy your clientAppId.
3

Get API Key

Get your API key from Dashboard > API Keys.
4

Set Permissions

Configure which OnlyFans data your platform can access in Dashboard > Client Apps > Settings > Access Permissions.

Redirect Flow

The simplest integration—redirect users to OFAuth’s hosted authentication pages.
Response:

Session Options

Step 2: Redirect User

The user will enter their credentials, complete 2FA if enabled, and solve captchas—all handled automatically by OFAuth.

Step 3: Handle the Callback

After authentication, users are redirected to your URL:

Callback Parameters


Keep users in your app with a popup authentication experience.

Installation

JavaScript Library Usage

Configuration Options

Success Metadata

Global Script (No Build)


Use the Connection

Once you have a Connection ID, make API calls:

Reconnecting Expired Connections

When a connection expires, reconnect without creating duplicates:
The existing connection is updated with fresh session data—same Connection ID, no duplicates.

Security Best Practices

Server-Side Verification

Always verify session status server-side, never trust client-side data

HTTPS Only

Use HTTPS for all redirect URLs and API communications

Session Expiry

Link sessions expire after 1 hour. Create a new session if expired.

Allowed URIs

Configure exact redirect URLs in your dashboard. No wildcards.

Troubleshooting

Link sessions expire after 1 hour. Create a new session with /v2/link/init.
Add the URL to your client app’s Allowed Redirect URIs in Dashboard > Client Apps.
Add your domain to your client app’s Allowed Origins in Dashboard > Client Apps.

Next Steps

Handle System Webhook Events

Get notified when connections change

API Reference

Full Link API documentation