What counts as a credit?

One successful API call. If a request fails — expired session, upstream error — it isn't charged. Mass DMs are the exception: a mailing bills one credit per recipient, and you can preview the exact cost before sending.

How do I authenticate?

A Bearer token: Authorization: Bearer ofapis_sk_…. Create and revoke keys in the dashboard.

Can I manage multiple creators?

Yes. Link several accounts and address each by id under scoped routes. Account count scales with your plan.

Do you have an OpenAPI spec?

A complete OpenAPI 3.0 document and a live Swagger playground — point your generator at it for a typed client.

OnlyFans API Reference

Every route lives under https://api.ofapis.com/api/public/v1 and authenticates with a single Bearer token. Successful responses are wrapped in a data object; errors return {"error":{"code","message"}}. Billing is one credit per successful call — failures are never charged.

Get a free token Authentication Error codes Rate limits Guides

Profile & fans

Read the linked creator profile and the audience around it.

GET/me
GET/subscribers
GET/following
GET/users/by-username/{username}
GET/users/{targetUserId}

Guide →

Chats & messages

List conversations, read history, and send — including priced PPV messages.

GET/chats
GET/chats/users
GET/chats/{chatId}/messages
POST/chats/{chatId}/messages

Guide →

Mailings (mass DM)

Create a campaign, preview its reach and cost, dispatch it, then track the run.

GET/accounts/{accountId}/mailings
POST/accounts/{accountId}/mailings
POST/accounts/{accountId}/mailings/{mailingId}/preview
POST/accounts/{accountId}/mailings/{mailingId}/trigger
GET/accounts/{accountId}/mailings/{mailingId}/runs

Guide →

Fan segments

Group fans into lists and address a whole cohort in one send.

GET/accounts/{accountId}/lists
POST/accounts/{accountId}/lists
GET/accounts/{accountId}/lists/{listId}/users
POST/accounts/{accountId}/lists/{listId}/users

Guide →

Scheduling

Queue feed posts and messages ahead of time, and manage the queue.

GET/accounts/{accountId}/scheduled/posts
POST/accounts/{accountId}/scheduled/posts
GET/accounts/{accountId}/scheduled/posts/counters
POST/accounts/{accountId}/scheduled/messages

Guide →

Media & activity

Upload to the vault, then reference media by id; poll activity or use webhooks.

POST/accounts/{accountId}/media
GET/vault/media
GET/notifications
GET/notifications/count
GET/mentions

Guide →

Account-scoped variants of the read endpoints exist under /accounts/{accountId}/… so an agency can address each creator by id under one token. The full interactive reference — with schemas, a live playground and multi-language samples — is below.