The cheapest and fastest OnlyFans API

The Only API is a third-party REST API for OnlyFans and Fansly. 500+ documented API operations cover messaging and mass DMs, fan and subscriber management, earnings and payouts, campaigns and tracking links, webhooks, automations, and data export — all under one API key, with flat per-slot pricing and no per-call metering. Built for agencies and developers.

Slot-based: $20/month per connected account slot. Once you reach 15 slots, ALL your slots drop to $15/month — not just the new ones. Stripe applies the volume tier automatically the moment you cross 15. Paid slots have no monthly call quota. There is also a Free plan — 1 account and 1,000 API calls/month, no card required — so you can test before paying. Agencies at 50+ accounts can contact sales for Enterprise pricing below $15/slot.

A slot is a 30-day right to keep one OnlyFans or Fansly account connected. When you add an account, a new slot is created on your subscription and you are charged prorated for the rest of the current period. Disconnecting an account frees the slot immediately — you can attach a different account to it at no extra charge. The slot itself stays on your subscription until you release it, and releasing it stops billing at the next renewal.

No — no credits, no per-call billing. Paid slots have no monthly call quota. Two things to know: a per-minute anti-flood ceiling applies on every plan (1,000 requests/minute by default, lower on authentication and other sensitive routes), and many read endpoints have cached variants (/subscribers/cached, /transactions/cached, /campaigns/{campaign_id}/claimers/cached and more) that cost zero platform requests, so high-frequency polling does not burn your OnlyFans rate budget. The Free plan is the only plan with a monthly call cap (1,000/mo), to keep abuse off the free tier.

As many as you need — each connected account uses one slot, and you can add or remove slots anytime. The Free plan includes 1 account. Each account carries its own proxy (which you supply on connect via the X-Proxy header) and its own managed session, so accounts stay fully isolated from each other. Perfect for agencies managing anywhere from 5 to 500+ creators.

Paid slots start with a 14-day free trial — full access to all 500+ documented API operations with no monthly call quota (the 1,000 requests/minute anti-flood ceiling still applies). Cancel before the trial ends and your card is never charged. After the trial, slots are $20/mo each, and once you reach 15 slots EVERY slot drops to $15/mo (not just the new ones). The Free plan needs no card at all and is not time-limited.

500+ documented API operations covering messaging and mass DMs, fan lists with tags and notes, earnings analytics and payout status, subscriber and transaction data (live plus zero-cost cached reads), campaigns and tracking links, PPV stats, webhooks and automations, and CSV/JSON data export. Every endpoint is reachable on every plan — there is no plan-based feature gating. One safety default to know: write actions (sending DMs, mass DMs) are OFF by default on every connected account. Enable them per account with PATCH /api/crm/{crm_id}/accounts/{of_user_id}/polling {"allow_of_write_actions": true}.

Yes. No-code integrations with Zapier, Make (Integromat), and n8n work on every plan — including the free tier. Automate fan engagement, mass messaging, and analytics reporting without writing code. There is no plan-based feature gating anywhere in the API: every endpoint is reachable on every plan.

No provider can guarantee an account outcome. You bring your own proxy — every OnlyFans account connect requires an X-Proxy header, and each account keeps its assigned proxy for all subsequent calls (GET/PATCH /api/crm/{crm_id}/accounts/{of_user_id}/proxy). We provide request signing, session management, paced platform traffic, and a proxy reachability tester (POST /api/crm/{crm_id}/proxy/test), and we strongly recommend a dedicated residential proxy per account. As a further safety default, write actions (sending DMs, mass DMs) are OFF by default on every connected account; enable them per account with PATCH /api/crm/{crm_id}/accounts/{of_user_id}/polling {"allow_of_write_actions": true}. Operators remain responsible for platform terms, proxy quality and usage.

Flat per-slot pricing with no credits and no per-call metering — most competitors meter by call or by credit bundle, which gets expensive at agency volume. Paid slots have no monthly call quota; a per-minute anti-flood ceiling (1,000 requests/minute default, lower on auth and other sensitive routes) applies on every plan. You also get 500+ documented API operations, no-code integrations, and both OnlyFans and Fansly on every plan, plus a free plan so you can test before you buy.

Yes — The Only API supports both OnlyFans and Fansly, and Fansly data is normalized to the same response shapes as OnlyFans. Connect Fansly with email/username + password (2FA supported) or with existing session credentials (fansly_session_id + fansly_client_id) via POST /api/crm/{crm_id}/accounts/login/cookies. Two OnlyFans-only exceptions: creating payout requests, and per-campaign claimer enumeration. Support for additional creator platforms is on our roadmap.

Send your key in an X-API-Key header on every request. Keys are minted per CRM panel: a primary key you can rotate yourself (POST /api/crm/{crm_id}/rotate-key) plus secondary keys (POST /api/crm/{crm_id}/api-keys, primary-key only, returned exactly once). Per-key usage is broken out at GET /api/crm/{crm_id}/api-keys/{key_id}/usage.

Yes. We host an MCP server that turns your API key into a panel identity (GET /api/whoami) and exposes the API as tools to Claude, ChatGPT, and any MCP client. Read tools work out of the box; non-GET requests through the generic OnlyFans proxy tool are off by default and enabled per panel via PATCH /api/crm/{crm_id}/mcp/unsafe-proxy.

Webhook endpoints on unrecognized domains start in a pending state and go live after a quick review; well-known event sinks (Discord, Slack, Telegram) auto-approve, as does any domain already approved for your panel. Check status on GET /api/crm/{crm_id}/webhooks and test delivery with POST /api/crm/{crm_id}/webhooks/{webhook_id}/test.