Record cookie consent
Stores the user's accepted cookie/consent preferences. OnlyFans only — Fansly accounts are rejected on /api2/v2/.
Stores the user's accepted cookie/consent preferences. OnlyFans only — Fansly accounts are rejected on /api2/v2/*.
Guide: The two surfaces
Authorization
apiKey Your CRM panel API key
In: header
Header Parameters
Creator account ID of the account to act as (e.g. 509955039). Required — omitting it returns 400 user-id header is required. Use GET /accounts to list your connected accounts. On /api2/v2/* the account must be an OnlyFans account; Fansly accounts are rejected there.
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
opaque object; fields not statically visible (cookie consent payload)
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X POST "https://example.com/api2/v2/accepted-cookies" \ -H "user-id: 509955039" \ -H "Content-Type: application/json" \ -d '{}'{ "success": true, "status_code": 0, "data": null, "relogin": true}User
Direct proxy to OnlyFans user profile & settings endpoints. **OnlyFans only.** Requires `X-API-Key` + `user-id` headers.
Start age verification POST
Initiates the age verification flow. Grouped with iv/start and face-id/start identity checks. OnlyFans only — Fansly accounts are rejected on /api2/v2/.