THE ONLYFANS API

The OnlyFans API for agencies and developers — Fansly included

OnlyFans has no public developer API. The Only API is the third-party OnlyFans API that closes that gap — 500+ documented REST endpoints for messaging, mass DMs, fans, subscribers, earnings, payouts, posts, the vault, campaigns, and data export. The same API covers Fansly, normalized to identical request and response shapes. Paid slots have no monthly call quota, and a free plan with 1 account and 1,000 calls per month lets you build and verify before you pay.

Start free See the endpoints

DIRECT ANSWER

Does OnlyFans have an API?

OnlyFans does not publish a public developer API or issue developer keys. The Only API is an independent, third-party REST API and CRM that provides authenticated access to messaging, fans, subscribers, earnings, campaigns, exports and automation. It also normalizes supported Fansly data into the same integration.

Limitations: The Only API is not affiliated with or endorsed by OnlyFans or Fenix International. Platform behavior can change without notice, and some Fansly capabilities remain OnlyFans-only; those return an explicit PLATFORM_NOT_SUPPORTED response.

Reviewed by The Only API team · Updated 2026-09-24Sources:OpenAPI specification API documentation Pricing and limits

How third-party API access works

Not officially. OnlyFans does not publish a developer API, issue API keys, or run a developer portal. So when agencies and developers search for an "OnlyFans API," what they actually need is a reliable third-party layer that turns the platform into clean, authenticated REST endpoints — without scraping the web app or maintaining brittle browser automation.

That is exactly what The Only API provides. We handle login (email and password with automatic Cloudflare Turnstile captcha solving, 2FA/OTP challenges, or direct session-cookie connection), session management, per-account proxy binding, request signing, and human-realistic pacing, then expose 500+ documented API operations under a single API key. You write normal HTTP requests; we keep the connection alive and safe.

The same API covers Fansly. Connect a Fansly account with its session credentials and the endpoints you already call — single DMs, earnings, transactions, subscribers, fans, exports — return the same normalized shapes, so you write the integration once. A handful of capabilities remain OnlyFans-only (mass DMs, payout requests, campaign claimers, PPV stats) and return an explicit 501 PLATFORM_NOT_SUPPORTED rather than failing quietly.

What the OnlyFans API covers

Every endpoint group below is available on all plans — no feature is locked behind a higher tier. The free plan includes 1,000 API calls per month; paid slots are unlimited. Rows note where a capability is OnlyFans-only.

OnlyFans and Fansly API endpoint coverage by The Only API
Feature	The Only API	Official OnlyFans API
Messaging & single DMs	Send a DM or PPV to one fan via POST /accounts/{of_user_id}/chats/{with_user_id}/messages, with OnlyFans vault media (mediaFiles), free teaser previews, and a price for PPV. Text messaging is available on both platforms; media attachments are currently OnlyFans-only.	—
Mass DMs (OnlyFans only)	Resolve an audience from the subscriber cache — active, all, or expired, plus min_spent, a subscribed_at date window, or explicit fan_ids — then send. Runs as a dry-run preview by default, returning recipient counts and a sample before anything is delivered.	—
Posts & vault	Create feed posts and stories, schedule them per timezone, set paywall pricing, and manage vault media for reuse across accounts.	—
Fans & subscribers	List and segment fans, read spend and engagement, tag fans, and pull active/expired subscriber lists. Cached subscriber and stats endpoints cost zero platform requests and normalize OnlyFans and Fansly rows to the same shape.	—
Earnings & payouts	Read earnings by period and category, plus transaction-level history (tips, PPV, subscriptions, refunds) on OnlyFans and Fansly. Requesting and tracking payouts is OnlyFans-only.	—
Campaigns & automations	Create campaigns, build rules (trigger → conditions → action), and run win-back and tip-auto-reply flows. Per-campaign claimer enumeration is OnlyFans-only.	—
Data export	POST /accounts/{of_user_id}/exports queues a full account export — messages, tips, subscribers, and earnings — by date range, in CSV or JSON. List jobs, poll status, download the result, or cancel a running job.	—
MCP server for AI agents	A hosted MCP server resolves an API key to your panel via GET /api/whoami, so Claude and ChatGPT can query your accounts, fans, and earnings directly in natural language.	—
Events & webhooks	Subscribe to HMAC-SHA256-signed webhooks for every event, with [5s, 30s, 5m, 30m, 2h] retries and auto-deactivation, plus an SSE stream. Webhooks on a not-yet-approved domain start as 'pending' until a one-time domain review clears them.	—
Platform coverage	OnlyFans and Fansly through one normalized API. Both platforms: single DMs, earnings, transactions, subscribers, fans, and exports. OnlyFans-only: mass DMs, payout requests, campaign claimers, and PPV stats — these return HTTP 501 PLATFORM_NOT_SUPPORTED for Fansly accounts.	—

Messaging & single DMs

The Only API

Send a DM or PPV to one fan via POST /accounts/{of_user_id}/chats/{with_user_id}/messages, with OnlyFans vault media (mediaFiles), free teaser previews, and a price for PPV. Text messaging is available on both platforms; media attachments are currently OnlyFans-only.

Official OnlyFans API

—

Mass DMs (OnlyFans only)

The Only API

Resolve an audience from the subscriber cache — active, all, or expired, plus min_spent, a subscribed_at date window, or explicit fan_ids — then send. Runs as a dry-run preview by default, returning recipient counts and a sample before anything is delivered.

Official OnlyFans API

—

Posts & vault

The Only API

Create feed posts and stories, schedule them per timezone, set paywall pricing, and manage vault media for reuse across accounts.

Official OnlyFans API

—

Fans & subscribers

The Only API

List and segment fans, read spend and engagement, tag fans, and pull active/expired subscriber lists. Cached subscriber and stats endpoints cost zero platform requests and normalize OnlyFans and Fansly rows to the same shape.

Official OnlyFans API

—

Earnings & payouts

The Only API

Read earnings by period and category, plus transaction-level history (tips, PPV, subscriptions, refunds) on OnlyFans and Fansly. Requesting and tracking payouts is OnlyFans-only.

Official OnlyFans API

—

Campaigns & automations

The Only API

Create campaigns, build rules (trigger → conditions → action), and run win-back and tip-auto-reply flows. Per-campaign claimer enumeration is OnlyFans-only.

Official OnlyFans API

—

Data export

The Only API

POST /accounts/{of_user_id}/exports queues a full account export — messages, tips, subscribers, and earnings — by date range, in CSV or JSON. List jobs, poll status, download the result, or cancel a running job.

Official OnlyFans API

—

MCP server for AI agents

The Only API

A hosted MCP server resolves an API key to your panel via GET /api/whoami, so Claude and ChatGPT can query your accounts, fans, and earnings directly in natural language.

Official OnlyFans API

—

Events & webhooks

The Only API

Subscribe to HMAC-SHA256-signed webhooks for every event, with [5s, 30s, 5m, 30m, 2h] retries and auto-deactivation, plus an SSE stream. Webhooks on a not-yet-approved domain start as 'pending' until a one-time domain review clears them.

Official OnlyFans API

—

Platform coverage

The Only API

OnlyFans and Fansly through one normalized API. Both platforms: single DMs, earnings, transactions, subscribers, fans, and exports. OnlyFans-only: mass DMs, payout requests, campaign claimers, and PPV stats — these return HTTP 501 PLATFORM_NOT_SUPPORTED for Fansly accounts.

Official OnlyFans API

—

“Official OnlyFans API” column is “—” because OnlyFans publishes no equivalent public developer API as of 2026.

A real OnlyFans API request

Send a welcome DM with a vault attachment. Authentication is a single X-API-Key header. Note that crm_id, of_user_id and the fan id are path parameters, not body fields, and that write actions must be enabled once per account before a send succeeds. Message text is delivered verbatim — there is no per-fan token substitution, so personalize by sending per-fan text from your own code.

# 1. One-time per account: enable write actions.
#    Without this, sending returns 403 {"code": "WRITES_DISABLED"}.
curl -X PATCH https://theonlyapi.com/api/crm/$CRM_ID/accounts/$OF_USER_ID/polling \
  -H "X-API-Key: $YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "allow_of_write_actions": true }'

# 2. Send a welcome DM with a vault attachment.
#    price > 0 makes it a PPV; "previews" is the free teaser subset.
curl -X POST https://theonlyapi.com/api/crm/$CRM_ID/accounts/$OF_USER_ID/chats/$FAN_ID/messages \
  -H "X-API-Key: $YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Hey, thanks for subscribing!",
    "mediaFiles": [987654],
    "previews": [],
    "price": 0
  }'

The same route sends on Fansly — connect a Fansly account and the request shape is unchanged.

Why developers pick The Only API

Unlimited calls on every paid slot

Paid slots are not metered — poll subscriber lists every minute, run analytics at 3 a.m., blast a campaign, and your bill stays per connected account. The free plan includes 1,000 API calls a month so you can build and verify before you pay.

500+ documented API operations, one key, two platforms

Messaging, mass DMs, posts, vault, fans, subscribers, earnings, payouts, campaigns, and exports — all behind a single API key with multi-account support, across OnlyFans and Fansly.

Cached reads, signed webhooks

Cache-backed endpoints (cached subscribers, cached transactions, subscriber stats and refresh status) cost zero platform requests. Every event streams to your URL via HMAC-SHA256-signed webhooks with [5s, 30s, 5m, 30m, 2h] retries.

Account-isolation controls

Every account is bound to its own dedicated proxy — assignable and testable through the proxy endpoints — with isolated sessions, signed requests and paced platform traffic. These controls reduce avoidable risk; they cannot guarantee an account outcome.

Multi-platform support & data portability

The same API powers Fansly alongside OnlyFans, and lets you export a full copy of any account's data. Two guides to get you started:

Fansly API for developers

Manage Fansly and OnlyFans accounts — messages, earnings, tips, and fans — through one normalized API and dashboard.

Read the guide →

Export your OnlyFans & Fansly data

Download a full copy of your data — messages, tips, subscribers, and earnings — by date range, in clean CSV and JSON.

Read the guide →

OnlyFans API — FAQ

The questions agencies and developers ask before building.

OnlyFans does not offer a public, official developer API. There is no documented endpoint set, API key issuance, or developer portal from OnlyFans itself. The Only API fills that gap: it is a third-party OnlyFans API that exposes 500+ documented API operations — messaging, mass DMs, posts, the vault, fans, subscribers, earnings, payouts, campaigns, and full data export — behind a single authenticated key. The same API also covers Fansly, normalized to the same request and response shapes, so one integration serves both platforms.

Create a free account on The Only API, generate an API key, then connect an OnlyFans or Fansly account through our login flow. For OnlyFans we support email and password login with automatic Cloudflare Turnstile captcha solving, 2FA/OTP challenges via POST /accounts/login/verify-otp, and direct session-cookie connection via POST /accounts/login/cookies (which also accepts fansly_session_id and fansly_client_id for Fansly). Connecting an account requires an X-Proxy header — each account is bound to its own proxy. From there you call any of the 500+ documented API operations with an X-API-Key header. The free plan covers one account and 1,000 API calls per month, which is enough to verify the full integration before you pay.

Yes. The Only API publishes an OpenAPI specification at /api/openapi.json, and a public API reference at /api-reference rendered with Scalar — no login required. The reference lets you send requests to endpoints live in the browser and generates client snippets in multiple languages from the spec. Every endpoint is documented with request and response schemas, authentication requirements, required headers, and rate-limit guidance.

No official OnlyFans developer API is publicly available as of 2026. Teams that need programmatic access — to automate messaging, sync earnings into a CRM, or run analytics — use a third-party OnlyFans API such as The Only API. We handle authentication (email and password with Turnstile captcha solving, OTP verification, or session-cookie connection), session management, per-account proxy binding, and request signing, so you interact with clean REST endpoints instead of reverse-engineering the OnlyFans web app. The same layer covers Fansly.

There are three plans. Free forever costs $0 and includes 1 account and 1,000 API calls per month, with access to all 500+ documented API operations. Slots costs $20 per month per connected account slot, and every slot drops to $15 per month once you reach 15 or more slots — the discount applies to all your slots, it is not a separate plan. Slots include unlimited API calls, and billing is prorated the day you add a slot. Enterprise is custom pricing for agencies running 50+ accounts, with volume rates below $15 per slot, a dedicated account manager, custom integrations, and SLAs. There are no credits, no per-call fees, and no overage bills on paid plans — your cost depends on how many accounts you connect.

Common builds include agency CRMs, mass-DM and PPV campaign tools, welcome-message and win-back automations, earnings and LTV dashboards, fan segmentation systems, and chatter tooling. Because every tip, PPV unlock, subscription, and message can be streamed to your stack via HMAC-SHA256-signed webhooks, you can also drive real-time automations through Make, Zapier, n8n, or your own event bus. You can queue a full account export (messages, tips, subscribers, earnings) by date range in CSV or JSON, and point Claude or ChatGPT at the hosted MCP server to query the API in natural language. Since the API covers both OnlyFans and Fansly with normalized shapes, one codebase can serve creators on either platform.

No third-party API can guarantee an account outcome. The Only API reduces avoidable risk by binding each connected account to its own proxy, isolating sessions, signing requests and pacing platform traffic. An X-Proxy header is required to log in and for live platform reads such as notifications, earnings, and balances, and you manage each account's proxy through GET and PATCH /accounts/{of_user_id}/proxy with a reachability probe at POST /proxy/test. Cache-backed endpoints (cached subscribers, cached transactions, subscriber stats and refresh status) avoid additional platform requests. Operators remain responsible for platform terms, proxy quality and how they use write actions.

Most developers send their first authenticated read request within 10 minutes: sign up, generate a key, connect an account, and call an endpoint. Three prerequisites are worth knowing up front. First, connecting an account requires an X-Proxy header — POST /accounts/login and POST /accounts/login/verify-otp both require it. Second, write actions such as sending a DM are disabled by default per account and return 403 with code WRITES_DISABLED until you enable them with PATCH /accounts/{of_user_id}/polling and body {"allow_of_write_actions": true}. Third, a webhook pointing at a domain that is not yet approved starts in 'pending' status and goes live after a one-time domain review, so budget for that on your first deployment rather than expecting instant delivery. Reads, the API reference playground, and the OpenAPI spec are available immediately.

Build on the OnlyFans API today

Free plan: 1 account, 1,000 API calls a month, all 500+ documented API operations, no credit card. Paid slots are $20/mo with unlimited calls.

Start free▶

Talk to us