Automate chats, mass DMs and scheduling across every creator account — without babysitting logins or risking bans. One dashboard, one bill, all your models.
Run campaigns and conversations across every model — from one place, without the manual grind.
POST /accounts/{id}/mailings/{id}/preview returns the exact recipient count and credit cost; /trigger sends. Dispatch is paced at one message per 500 ms.
A message.received webhook fires on every inbound DM, so your bot reacts instead of polling. Replies go out over POST /chats/{chatId}/messages.
Encrypted sessions and tiered egress: a shared pool on Free, a dedicated proxy per linked account on Starter and Pro.
Pro links 5 accounts. Every route has an /accounts/{accountId}/… twin, so one code path serves the whole roster.
A 5,000-fan mailing is a single POST, not 5,000. Preview the cost first; recipients the run skips are refunded when it completes.
Most calls weigh 1 credit. Media upload is 5, a scheduled post or message 3, an account-scoped send 2. Every debit and refund lands in the ledger against its request id.
X-Ofapis-Signature carries t=<unix>,v1=<HMAC-SHA256>. Dedupe on X-Ofapis-Delivery; failures retry at 1m, 5m, 30m, 2h and 6h.
Link a creator once — no refresh cron on your side. If a session does lapse you get 424 OF_SESSION_EXPIRED and the credit back, not a silent wrong answer.
/accounts/{accountId}/chats, …/mailings, …/scheduled/posts, …/lists — the same shapes, scoped per model.
OpenAPI 3.0 across 47 public routes, plus a live playground — point a generator at it for a typed client in any stack.
There is no official OnlyFans API, so every answer below starts from that. Here is the honest version of each, with the full argument a click away.
No. OnlyFans publishes no public API, no developer portal and no partner programme. Every product in this category, ofapis included, is an unofficial integration over the same private endpoints the web app calls.
Why there isn't oneAutomating an account you own, with credentials you hold, is not a criminal matter in any jurisdiction we're aware of. The live question is contractual: OnlyFans' terms don't grant third-party API access, so this sits between you and the platform. Use it on your own or your clients' accounts, and keep consent for anything you send.
The terms, read properlyNobody can promise zero risk, and a vendor who does is selling you something. What we control: encrypted sessions, a dedicated proxy per linked account on paid plans, and a 500 ms gap between mailing messages so a blast doesn't land as a burst. What you control is volume and pacing — the Free plan's shared proxy pool is for evaluation, not production.
What actually gets accounts flaggedUpstream breakage is the real cost of an unofficial integration — it happens, and it is our repair rather than your rewrite. You code against our contract: /api/public/v1, one Bearer token, a {"data":…} envelope and a fixed error-code set. Calls that die on an upstream fault come back 424 or 5xx and are refunded automatically.
Why this beats running your own scraperofapis is OpenAPI-native, so it plugs straight into MCP bridges and GPT Actions. Point Claude, ChatGPT or Manus at it and let an agent read chats, segment fans and send DMs — with your token, your rules.
Quickstarts, capabilities and integration recipes for the OnlyFans REST API.
What OnlyFans automation can and cannot do: which jobs have an endpoint, which have none, what to automate first, and what it costs per month to run.
Node.js OnlyFans API guide: verify the HMAC signature on the raw body, dedupe deliveries, ack inside ten seconds, then reply through undici with a timeout.
Read and send OnlyFans direct messages over a clean REST API: page a thread with a message cursor, reply, and lock a PPV send behind a price.
Drive the OnlyFans API from AI agents: ofapis is REST + OpenAPI 3.0, so an MCP bridge turns endpoints into typed tools. Tool shapes, scoping and real costs.
How an OnlyFans agency is actually structured: roles, the chatter-to-system handoff, the five layers of the stack, and the credit maths behind a roster.
The best OnlyFans API depends on your shape: one creator, a three-creator agency or a fifty-creator operation. Picked by use case, with honest limits.
Chats, mailings, scheduling and fan segments — a plain REST API, billed by the call. No headless browsers, no cookie juggling. Success is {"data": …}, failure is {"error": {"code", "message"}}, and every response carries X-RateLimit-Remaining and your X-Request-Id back.
# your first call curl https://api.ofapis.com/api/public/v1/me \ -H "Authorization: Bearer ofapis_sk_…"▐
{ "data": { "id": 100000001, "username": "demo_creator", "name": "Demo Creator", "subscribersCount": 12500, "isAuth": true } }
All 47 routes live under /api/public/v1 and authenticate with a single Bearer token. Lists paginate on limit + offset (default 20, clamped 1–100); message history walks backwards on olderThanMessageId. Here's the shape of it.
Generate a scoped ofapis_sk_ key in the dashboard. The per-minute limit is counted per token, so you can isolate a risky job behind its own key.
ofapis_sk_live_8f3a…
Connect a creator session once. ofapis keeps it alive — no refresh cron on your side.
status: active
Send Bearer-authed requests. Most routes meter 1 credit; media upload 5. A 401, 402, 403 or 429 is refused before anything is debited.
GET /v1/chats → 200 · −1
Every plan includes all 47 routes. Credits refill monthly and don't roll over; the per-minute limit is a burst cap, not a second budget.
We're built to minimize the risk: encrypted sessions, a dedicated proxy per linked account on paid plans, and mailing dispatch paced at one message per 500 ms so a blast doesn't arrive as a burst. The Free plan uses a shared proxy pool, so upgrade before running real volume. No service can guarantee against bans — this is an unofficial integration and the residual risk is yours.
One linked account on Free and Starter, five on Pro, and a negotiated roster on an Enterprise quote. Each one is addressable under /accounts/{accountId}/…, so adding a model doesn't change your code.
For ready-made automations via n8n, Make or Zapier — no. For custom workflows against the API — a developer helps. Both use the same account.
No. ofapis is an independent product, not affiliated with, endorsed by or sponsored by OnlyFans / Fenix International Limited. There is no official OnlyFans API to be a partner of.
Credits are weighted, not flat. Most calls cost 1; a media upload costs 5, a scheduled post or message 3, an account-scoped chat send 2. A mailing trigger costs 0 at the call and the run then debits one credit per recipient, so a 5,000-fan blast is 5,000 credits — preview it first for the exact figure.
A Bearer token: Authorization: Bearer ofapis_sk_…. No request signing, no OAuth dance. Create and revoke keys in the dashboard; the rate limit is counted per token, so a runaway job can't starve the rest of your integration.
A complete OpenAPI 3.0 document covering all 47 public routes, plus a live playground — point your generator at it for a typed client.
Free plan, 250 credits, no card. Connect your first creator and run campaigns in minutes.
Get started