List referral payout requests
Referral payout history — the referral twin of GET /accounts/{of_user_id}/payout-requests, shaped identically.
Referral payout history — the referral twin of GET /accounts/{of_user_id}/payout-requests, shaped identically.
The row shape inside requests is unverified; rows pass through untouched and the raw upstream body is echoed under data.
OnlyFans only — Fansly returns 501.
Guide: Earnings & transactions
Authorization
apiKey Your CRM panel API key
In: header
Path Parameters
Creator account ID of the connected account (OnlyFans or Fansly). Use GET /accounts to list connected accounts and their IDs.
Query Parameters
Range start, YYYY-MM-DD or YYYY-MM-DD HH:MM:SS
Range end, same format as startDate
Pagination cursor returned by OnlyFans
Header Parameters
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.
Response Body
application/json
curl -X GET "https://example.com/accounts/string/referrals/payout-requests"{ "success": true, "requests": [ {} ], "count": 0, "marker": null, "data": null}Referral balance + chart GET
Referral money summary in one response, fanned out to two OnlyFans endpoints (still one quota call).
Subscribers
Subscriber reads. Live routes hit the platform; `/subscribers/cached`, `/subscribers/new`, and `/subscribers/stats` cost zero platform requests and normalize OnlyFans + Fansly rows to the same shape.