Referral balance + chart

Referral money summary in one response, fanned out to two OnlyFans endpoints (still one quota call).

balance and chart hold the raw upstream bodies — no field mapping. The two documentation sources disagree about the chart body, and the balance endpoint appears in no capture at all, so mapping fields would fabricate a contract.

Partial failure is tolerated: a source that fails comes back null and sources records its status. If both fail, the route returns the upstream status with success: false — an expired session must not be indistinguishable from "no referral earnings".

OnlyFans only — Fansly returns 501.

Guide: Earnings & transactions

Authorization

apiKey

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.

Query Parameters

startDate?string

Chart range start (forwarded to the chart call)

endDate?string

Chart range end

withTotal?string

Include totals. Defaults to the value the OnlyFans web client sends.

Default"1"

withChart?string

Include the chart series. Defaults to the value the OnlyFans web client sends.

Default"true"

filter?string

Chart filter; forwarded verbatim when supplied.

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.

Response Body

`application/json`

curl -X GET "https://example.com/accounts/string/referrals/earnings"

{  "success": true,  "balance": null,  "chart": null,  "sources": {    "balance": {      "ok": true,      "status": 0    },    "chart": {      "ok": true,      "status": 0    }  }}