The Only API docs
Proxy

Generic platform API proxy

Send any authenticated request to the connected account's platform API. Use this to reach an endpoint not covered by the dedicated CRM routes. Auto-relogins on session expiry.

POST
/accounts/{of_user_id}/request

Send any authenticated request to the connected account's platform API. Use this to reach an endpoint not covered by the dedicated CRM routes. Auto-relogins on session expiry.

Both platforms. The account's platform decides where the request goes and what path must look like:

platformhostpath example
onlyfansonlyfans.com/api2/v2/users/me
fanslyapiv3.fansly.com/api/v1/account/me

On Fansly the path must carry the /api/v1 prefix: the request signature hashes the pathname, so it cannot be rewritten for you. Optional base_url targets Fansly's upload host (https://mediav2.fansly.com); no other host is accepted, because a signed request carries the account's bearer token.

Any method other than GET is gated by allow_of_write_actions on the account.

Guide: Proxies

X-API-Key<token>

Your CRM panel API key

In: header

Path Parameters

of_user_id*string

Creator account ID of the connected account (OnlyFans or Fansly). Use GET /accounts to list connected accounts and their IDs.

Header Parameters

X-Proxy?string

Proxy URL — HTTP or SOCKS5 (e.g. http://user:pass@host:port or socks5://user:pass@host:port). Optional on post-connection routes, where it overrides the proxy saved at login time. Required on the connection routes (POST /accounts/login, POST /accounts/login/cookies, POST /accounts/login/verify-otp) for OnlyFans accounts; optional for Fansly.

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

curl -X POST "https://example.com/accounts/string/request" \  -H "Content-Type: application/json" \  -d '{    "path": "string"  }'
{  "success": true,  "status_code": 0,  "data": {}}