CRM API

Connect a creator account (OnlyFans or Fansly) and complete 2FA. All three routes accept platform: "onlyfans" | "fansly" and are rate limited to 10 requests/minute.

Manage connected creator accounts (OnlyFans and Fansly), their polling settings, proxies, and slots.

Panel signup, health, key→panel resolution, and plan/usage counters. Works for OnlyFans and Fansly panels alike.

Primary + secondary API key management. POST /api-keys and DELETE /api-keys/{key_id} are PRIMARY-KEY ONLY (a secondary key gets 403). The primary Default key cannot be revoked — rotate it via POST /rotate-key.

Revenue & earnings data, including the cross-account GET /earnings/summary aggregation. Fansly-aware.

Payout & purchase transactions, live and cached.

Withdrawal requests and payout account details. Creating a withdrawal is OnlyFans only.

OnlyFans referral programme — who the account referred, what it earned, and referral payout history. OnlyFans only: Fansly accounts get 501 platform_not_supported (feature: "referrals"). Live reads, no cache; one quota call per request. OnlyFans' referral response bodies are passed through with minimal normalization — only the list/hasMore/marker envelope keys are read, and the raw body is echoed under data. Fields inside a referral row are unverified: do not depend on them without checking against a live account.

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.

Fan CRM across all accounts in the panel — tags, notes, per-fan cached transactions, profile refresh. Fansly-aware.

Chats, single DMs/PPVs, mass DMs, and PPV performance stats. Fansly-aware.

Media upload. Runs OnlyFans' four-stage signed-S3 pipeline server-side and returns a reference you attach to a post, message or story via mediaFiles. OnlyFans only.

Tracking link campaigns, claimers, campaign tags, and the tracked-campaign allowlist.

Account notifications. Fansly-aware.

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.

Real-time event feed — GET /events for polling, GET /events/stream for Server-Sent Events (rate-limit exempt).

Outbound webhook subscriptions, test fires, and delivery history.

Event-triggered automations, manual runs, and run history.

Async data export jobs producing a downloadable ZIP. Progress streams over GET /events/stream.

Third-party integrations. One Telegram channel per panel: pair it once, then matching events are delivered to that chat. The bot token is encrypted at rest and is never returned by any route.

Account settings, subscription price & proxy management

Generic authenticated OnlyFans API proxy (POST /accounts/{of_user_id}/request). OnlyFans only.

Hosted MCP server support. GET /api/whoami turns a bearer token into a tenant; PATCH /mcp/unsafe-proxy toggles non-GET tool access (off by default).

Connect many creator accounts from one pasted list. POST /import/preview validates without side effects; POST /import/jobs runs the import in the background and streams import.progress / import.complete over GET /events/stream. Rows that hit a 2FA prompt park as needs_2fa until you supply a code.