Skip to main content
GET /v2/access/proxy/{path}

curl -X GET 'https://api.ofauth.com/v2/access/proxy/users/me' \
  -H 'apikey: YOUR_API_KEY' \
  -H 'x-connection-id: conn_abc123'

{
  "id": 12345,
  "username": "example_user",
  "name": "Example User",
  "email": "[email protected]",
  "avatar": "https://cdn.onlyfans.com/...",
  "cover": "https://cdn.onlyfans.com/...",
  "subscribersCount": 150,
  "favoritesCount": 25
}
​
path
string
required
The OnlyFans API path to proxy to. This can be any valid OnlyFans API endpoint path.Examples:
  • users/me - Get current user information
  • chats - Get chat conversations
  • users/12345/posts - Get posts for user 12345
  • subscriptions/subscribers - Get subscribers
Base URL: https://api.ofauth.com/v2/access/proxy

​
Authentication

HeaderRequiredNotes
apikeyYesAPI key from the OFAuth dashboard
apikey: YOUR_API_KEY
All Access API requests require a connection. Pass the connection ID in the x-connection-id header alongside your API key.
​
apikey
string
required
Your OFAuth API key
​
x-connection-id
string
required
The connection ID from Link authentication or import

​
Status Codes

CodeDescription
200Request successful - response from OnlyFans API
400Bad request - invalid parameters or path
401Unauthorized - invalid API key or expired session
429Rate limit exceeded
500Internal server error
502Bad gateway - proxy or OnlyFans API error
The specific response structure and status codes depend on the OnlyFans API endpoint being accessed. OFAuth passes through responses transparently while handling authentication and proxy management.

​
Rate Limits

Rate limits are applied per connection ID or session:
  • Standard: 60 requests/minute (burst: 90)
  • Scale: No OFAuth limits
OFAuth rate limits are separate from OnlyFans’ native rate limits. You may still encounter OnlyFans rate limiting even when within OFAuth limits.

Link API

Authenticate users and get connection IDs

Access Guide

Detailed guide with examples and best practices