Skip to main content
OFAuth is a suite of services that each solve a specific piece of the OnlyFans integration puzzle. This page helps you understand which services you need and how they fit together.

​
The Integration Journey

Every OFAuth integration follows the same lifecycle:
  1. Link authenticates the user and produces a Connection ID
  2. Webhooks notify you when that connection is ready (or later expires)
  3. Access uses the Connection ID to read and write OnlyFans data
  4. Media Proxy provides access to OnlyFans media through proxied URLs

​
Which Services Do You Need?

Most integrations use Link + Access + System Webhook Events. Media Proxy is automatic (URLs in Access responses are already proxied). Realtime OnlyFans Events is opt-in for event-driven activity use cases.
Secure, hosted authentication for OnlyFans accounts. Users enter credentials on OFAuth’s pages — you never handle passwords. After authentication, you receive a Connection ID.

Link Authentication Guide

Step-by-step integration with redirect and popup modes

​
Access API

Make OnlyFans API requests using Connection IDs. Handles request signing, proxy routing, and session management so you don’t need to build that infrastructure.

Access Overview

Endpoint reference and permissions

Proxy Endpoints

Raw passthrough for advanced use cases

​
System Webhook Events

Webhook notifications when connections are created, updated, expire, or when Dynamic Rules change. Eliminates polling for connection lifecycle state.

System Webhook Events

Event types, payloads, and signature verification

​
Realtime OnlyFans Events

Supported OnlyFans activity events delivered to your webhook endpoint in real time.

Realtime OnlyFans Events

Event contract, delivery model, and documented schemas

​
Media Proxy

OnlyFans media cannot be accessed directly — CDN URLs are signed, short-lived, and block cross-origin requests. Media Proxy transforms them into stable media.ofauth.com URLs with extended validity, CORS headers, and global edge caching. This happens automatically — URLs in Access API responses are already proxied.
Bandwidth is billed per KB transferred. Cache hits (within 7 days) are free.

​
Account API

Administrative interface for managing your organization, connections, and settings. Use it to verify your API key, list connected accounts, or disconnect users.

Account API Reference

Complete endpoint documentation

​
Vault+

Persistent media storage that survives session expiry. Unlike Media Proxy (temporary edge caching), Vault+ stores media permanently and serves it by ID.

Media Storage Guide

Media Proxy vs Vault+ — when to use which

​
Dynamic Rules

Request signing parameters for direct OnlyFans API calls. Signing rules change frequently — sometimes multiple times per day.
Most integrations don’t need this. If you use the Access API, signing is handled automatically.

Dynamic Rules Reference

Complete endpoint documentation

​
Next Steps

Quickstart

Get your first API call working

How OFAuth Works

Core concepts and architecture

Integration Checklist

Production readiness guide

TypeScript SDK

Type-safe development experience