The Integration Journey
Every OFAuth integration follows the same lifecycle:- Link authenticates the user and produces a Connection ID
- Webhooks notify you when that connection is ready (or later expires)
- Access uses the Connection ID to read and write OnlyFans data
- Media Proxy provides access to OnlyFans media through proxied URLs
Which Services Do You Need?
| I need to… | Service | Required? |
|---|---|---|
| Connect a user’s OnlyFans account | Link API | Core |
| Read/write OnlyFans data (posts, messages, fans) | Access API | Core |
| Get notified when connections change | Webhooks | Recommended |
| Access OnlyFans media (images, videos) | Media Proxy | Automatic |
| Manage connections and org settings | Account API | As needed |
| Store media permanently beyond session expiry | Vault Cache | Optional |
| Sign requests for direct OnlyFans API calls | Dynamic Rules | Advanced |
Most integrations use Link + Access + Webhooks. Media Proxy is automatic (URLs in Access responses are already proxied). Everything else is opt-in.
Link API
Secure, hosted authentication for OnlyFans accounts. Users enter credentials on OFAuth’s pages — you never handle passwords. After authentication, you receive a Connection ID.| Integration Mode | Best For |
|---|---|
| Redirect (Hosted) | Simple setup, server-rendered apps |
| Popup (Embed) | Best UX, SPAs — user stays in your app |
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.| Method | Use When |
|---|---|
Managed Endpoints (/v2/access/*) | Common operations — typed responses |
Proxy Endpoints (/v2/access/proxy/*) | Any OnlyFans API path we haven’t wrapped yet |
Access Overview
Endpoint reference and permissions
Proxy Endpoints
Raw passthrough for advanced use cases
Webhooks
Real-time push notifications when connections are created, updated, or expire. Eliminates polling.Webhooks Reference
Event types, payloads, and signature verification
Media Proxy
OnlyFans media cannot be accessed directly — CDN URLs are signed, short-lived, and block cross-origin requests. Media Proxy transforms them into stablemedia.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 Cache
Persistent media storage that survives session expiry. Unlike Media Proxy (temporary edge caching), Vault Cache stores media permanently and serves it by ID.Media Storage Guide
Media Proxy vs Vault Cache — when to use which
Dynamic Rules
Request signing parameters for direct OnlyFans API calls. Signing rules change frequently — sometimes multiple times per day.Dynamic Rules Reference
Complete endpoint documentation