Skip to main content
The Access API provides two flavors of access to OnlyFans:
  • Managed endpoints (/v2/access/*) - Stable, typed routes for common operations
  • Proxy endpoints (/v2/access/proxy/*) - Forward any OnlyFans API request
Need a Connection ID? Complete the Link flow first to authenticate users.

​
Base URL

https://api.ofauth.com/v2/access

​
Authentication

Every request requires your API key plus a connection method: 
apikey: YOUR_API_KEY
x-connection-id: CONNECTION_ID
Use the connection ID from the Link API. OFAuth manages the underlying session.

​
Option 2: Direct Session Headers

apikey: YOUR_API_KEY
x-of-cookie: ONLYFANS_SESSION_COOKIE
x-of-user-agent: ONLYFANS_USER_AGENT
Use when you handle authentication separately. You manage session expiry and rotation.

​
Managed Endpoints

curl -H "apikey: YOUR_API_KEY" \
     -H "x-connection-id: conn_abc123" \
     "https://api.ofauth.com/v2/access/self/me"
Returns OFAuth-curated JSON with stable field names.

​
Proxy Endpoints

Forward any OnlyFans API path: 
curl -H "apikey: YOUR_API_KEY" \
     -H "x-connection-id: conn_abc123" \
     "https://api.ofauth.com/v2/access/proxy/users/me"
Returns the raw OnlyFans response.

​
Media Proxy

API responses automatically include media.ofauth.com/* URLs that are embeddable without CORS issues.
  • Enabled by default - No setup required
  • Extended validity - URLs last longer than OnlyFans CDN links
  • Edge cached - Faster loads, cache hits are free
Media proxy bandwidth is billed per KB transferred. Only cache misses are charged.

​
Next Steps

API Reference

Full endpoint documentation

TypeScript SDK

Convenient wrapper with error handling

Rate Limiting

Limits, best practices, monitoring

Error Handling

Error codes and debugging