List referral payout requests
Paginated list of referral payout transactions. Uses marker-based pagination.
Paginated list of referral payout transactions. Uses marker-based pagination.
OnlyFans only. Requests made with a user-id belonging to a Fansly account are rejected — use the platform-neutral CRM data routes (/notifications, /balances, /chats, /purchases, /subscribers/cached, ...) which are Fansly-aware.
Guide: The two surfaces
Authorization
apiKey Your CRM panel API key
In: header
Query Parameters
date-timedate-time0Pagination marker from previous response
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.
Response Body
application/json
curl -X GET "https://example.com/api2/v2/payouts/requests/referral" \ -H "user-id: 509955039"{ "list": [ {} ], "marker": 0, "hasMore": true}Create payout request POST
OnlyFans only. Requests made with a user-id belonging to a Fansly account are rejected — use the platform-neutral CRM data routes (/notifications, /balances,…
List Stripe payout requests GET
Returns the creator's Stripe payout requests, paginated by lastPayoutId. The dynamic path segment is actually the querystring. OnlyFans only — Fansly accounts are rejected…