List subscribers
Get subscribers with pagination and type filtering. Includes total spent data.
Get subscribers with pagination and type filtering. Includes total spent data.
Paging: advance with the nextOffset from the response, and stop when hasMore is false — not when list is empty. offset does not mean the same thing on both platforms: OnlyFans filters by type server-side so its offset counts rows returned, while Fansly filters client-side so its offset counts rows consumed, which can exceed count. Computing offset + list.length yourself silently skips subscribers on Fansly, and a page whose rows were all filtered out comes back with an empty list and more still behind it. nextOffset + hasMore are correct on both.
Guide: Subscribers & fans
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
value <= 100100"all"Value in
- "all"
- "active"
- "expired"
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/subscribers"{ "success": true, "list": [ {} ], "hasMore": true, "count": 0, "offset": 0, "nextOffset": 0, "limit": 0}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.
Refresh the subscriber cache (async) POST
Start an async subscriber sync for this account. Returns 202 immediately — poll GET /accounts/{of_user_id}/subscribers/refresh/status or listen on GET /events/stream…