Backfill historical data (async)
Kick off a historical backfill for this account, walking further back than the routine refresh. Returns 202 — track progress via the refresh-status routes or GET…
Kick off a historical backfill for this account, walking further back than the routine refresh. Returns 202 — track progress via the refresh-status routes or GET /events/stream.
Guide: Cached reads
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.
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 POST "https://example.com/accounts/string/backfill"{ "already_running": true, "days": 0, "platform": "string", "state": null, "success": true}Cache & Sync
Async refresh, backfill, and job-status routes that populate the local cache. Refresh routes return 202 — poll the matching `/refresh/status` route or listen on `GET /events/stream`.
List active refresh jobs GET
All refresh/backfill jobs currently running across the panel. Zero platform requests.