# CreatorAPI

> One API for OnlyFans, Fansly, 4based and Fanvue. Native access for OnlyFans, Fansly and 4based, plus Fanvue through its official API. One key; available platforms and account limits depend on your plan. Base URL https://api.creator-api.com. Authenticate with header `X-API-Key`. All native routes are reached through `{METHOD} https://api.creator-api.com/v1/{account}/native/{path}`.

## Fanvue billing

All available features for connected Fanvue accounts are included in the creator slot, with 0 additional credits. Plan/slot pricing, access permissions and rate limits still apply. Fan AI summaries and CreatorAPI export jobs do not currently support Fanvue; free pricing does not enable them. Other platforms retain their credit prices.

## Get started

- [Create an account](https://creator-api.com/signup): 1,000 trial credits after email confirmation, no card required
- [Pricing](https://creator-api.com/pricing): current plans and credit costs
- [Platform coverage](https://creator-api.com/): native OnlyFans, Fansly and 4based; Fanvue requires approved API access

## Docs

- [Quickstart](https://creator-api.com/docs/quickstart): auth, connecting accounts, billing, errors
- [Team and lifecycle](https://creator-api.com/docs/workspaces): staff permissions, workspace categories and owner-bound export/summary events; bounded verification
- [Profitability](https://creator-api.com/docs/profitability): OF/Fansly native net, explicit commission/cost inputs, async batch/history; forecasts not implemented
- [SDK and automation](https://creator-api.com/docs/sdk): installable server JavaScript/TypeScript SDK, n8n and Zapier previews; no hosted marketplace validation
- [OnlyFans write workflows](https://creator-api.com/docs/reference/onlyfans#onlyfans-write-workflows): concrete messages/PPV, upload-to-post, targeted queues and native campaigns; scope and uncertainty handling
- [OnlyFans reference](https://creator-api.com/docs/reference/onlyfans): 315 catalog entries; operation-specific coverage and limitations
- [Fansly reference](https://creator-api.com/docs/reference/fansly): the apiv3 surface
- [4based reference](https://creator-api.com/docs/reference/4based): native access, no official API
- [Fanvue reference](https://creator-api.com/docs/reference/fanvue): official API, one unified surface
- [Full docs in one file](https://creator-api.com/llms-full.txt): the entire API for Claude or Codex

## Solutions

- [OnlyFans CRM API](https://creator-api.com/onlyfans-crm-api), [Fansly](https://creator-api.com/fansly-crm-api), [4based](https://creator-api.com/4based-crm-api), [Fanvue](https://creator-api.com/fanvue-crm-api)
- [OnlyFans webhooks](https://creator-api.com/onlyfans-webhooks), [Fansly](https://creator-api.com/fansly-webhooks), [4based](https://creator-api.com/4based-webhooks), [Fanvue](https://creator-api.com/fanvue-webhooks)
- [OnlyFans mass messaging](https://creator-api.com/onlyfans-mass-messaging-api), [Fansly](https://creator-api.com/fansly-mass-messaging-api), [4based](https://creator-api.com/4based-mass-messaging-api), [Fanvue](https://creator-api.com/fanvue-mass-messaging-api)

## Machine readable

- [OpenAPI spec](https://creator-api.com/openapi.json)
- [Swagger UI](https://creator-api.com/docs)
- [OnlyFans capability catalog](https://creator-api.com/docs/capabilities/onlyfans.json)
- [Fansly capability catalog](https://creator-api.com/docs/capabilities/fansly.json)
- [Fanvue capability catalog](https://creator-api.com/docs/capabilities/fanvue.json)

## OnlyFans tracking links and revenue

- [Customer guide and runnable revenue-table example](https://creator-api.com/docs/reference/onlyfans#tracking-links-and-revenue)
- Existing native links: GET /v1/{account}/native/campaigns; join campaign IDs to /v1/{account}/tracking-links/{campaign_id}/transactions or /spenders with fixed date_start/date_end. data.summary contains revenue_gross_total and revenue_net_total for the full verified selection; both null when attribution_complete=false. known_revenue_gross_total/net_total and unresolved_gross_total/net_total remain separate. unresolved_rows retain signed ledger evidence without subscription_at or attribution_method; paginate that list separately by unresolved_pagination. 202 + Retry-After means collecting; polls free, each completed report one read credit.
- Native reports require current membership and verified observed subscription starts; native fan-profile 404 keeps actual ledger rows unresolved and overall totals null; other invalid or incomplete financial evidence still fails. Timestamps do not guarantee historic link-join dates, overlapping memberships are not unique attribution. Historic click:null; no retroactive UTMs.
- CreatorAPI Smart Links: GET /api/smart-links lists all stored gross revenue without date filters. GET /api/smart-links/{id}/conversions filters conversion_at; OMIT conversion_type to include paid acquisitions and later payments. summary.revenue_total is gross; sum amount_net once per stable ID over every page for net. Pending subscriber evidence is explicit, not zero.
- Click report: /api/smart-links/{id}/clicks. Advertise /go/{id}; readonly reporting, full key for creation. Seven-day eligible-click matching; subsequent recorded payments retain acquisition click. Poll and reconcile overlapping periods.

## Revenue metrics

OnlyFans revenue analytics expose gross/net/fees, fan revenue, transaction counts and daily/monthly monetary history. Historical subscription-event totals and new/renewed counts are available with daily reconciliation. Optional historical-price details return known paid/free counts and an explicit unknown remainder; unknown includes missing history, not just deleted fans. Use detailed=false for chart-only reads. See the OnlyFans reference for parameters and completeness rules.

- Native incoming-fan lifetime relationship totals: GET /v1/{account}/analytics/fans/{fan_id}/lifetime. Only subscribedOnData totals are used. amount_basis=provider_reported_relationship_totals; these are not guaranteed buyer gross amounts and no net/fees are inferred. Missing totals are null; real reported zeros stay zero. Missing native profiles return canonical JSON 404, other provider failures 503.
- Smart Link spenders and cohort ARPS report recorded attribution only, not a complete lifetime earnings history.

- OnlyFans Smart Link polling persists page progress and deduplicates recorded transactions. Initial history is silent; campaign attribution is not a complete historical backfill. Failed receiver deliveries retry with stable event identities for up to 12 attempts or 24 hours; external acceptance is not guaranteed.

Earnings, transaction summary/by-type/count, day/month history, fan period revenue, comparisons, forecasts and subscription metrics support async_report=true for bounded background collection. Repeat the same GET with unchanged parameters while HTTP 202 carries Retry-After: 2; final HTTP 200 has the normal complete report shape. Matching financial collection windows share a complete key/account-scoped ledger. Subscription reports use separate window/detailed identities and daily charts of up to 366 days; dated subscribe, return and prolong prices classify known paid/free events while missing history stays unknown. Reports are retained for five minutes. Reporting is free. Synchronous behavior remains available when the flag is omitted. See the full reference for the shared two-worker limits, 900-second collection budget and separate detailed-history limits.
Fan AI summary: use numeric fan_id,90s client request timeout and retry only HTTP503 error.code=summary_generating. Cached200 is free. Complete cURL/Python/JavaScript examples appear in the reference and /docs/workspaces.