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.

Build OnlyFans Chatter Software

Chatter software is for humans, not bots. A chat team needs a shared inbox across creators, a way to assign conversations so two people don't reply to the same fan, and canned replies to move fast without sounding robotic. ofapis supplies the messaging plumbing over REST — read chats, stream new messages via webhooks, and send replies — while your app owns the inbox, routing and team layer. For an automated bot instead of a staffed desk, see build an OnlyFans chatbot.

Architecture

webhook: message.received  →  inbox DB  →  assignment engine  →  chatter UI  →  send via API

Ingest. Subscribe to message.received webhooks, verify each payload against the signing secret, and write it to a conversations / messages store. Webhooks give you a live inbox without polling every chat.
Assign. Route each thread to one chatter (round-robin, per-creator ownership, or by fan value) and lock it so it can't be double-handled.
Send. When a chatter hits reply, POST the message through the messaging API.

The inbox

Hydrate the inbox and back-fill history from the chat endpoints, all account-scoped so one desk covers a whole roster:

GET  /accounts/{id}/chats                 # conversation list
GET  /accounts/{id}/chats/{chatId}/messages  # thread history
POST /accounts/{id}/chats/{chatId}/messages  # send a reply

Store account_id, chat_id, assignee, status and last_message_at on each conversation so the UI can filter by creator, unread state or owner.

Send a reply

curl -X POST \
  https://api.ofapis.com/api/public/v1/accounts/42/chats/98765/messages \
  -H "Authorization: Bearer ofapis_sk_..." \
  -H "Content-Type: application/json" \
  -d '{"text":"Hey love, that set just dropped — want the link? 💕"}'

Canned replies are just templates in your database that fill this text field — keep tokens like {fan_name} and substitute them client-side before the send. Because failed calls (expired session, upstream error) aren't billed, a mistyped chat id or a dropped session costs nothing.

Why per-call billing fits chat teams

Chatter software is usually priced per seat, which punishes you for scaling the team. ofapis bills one credit per successful call, not per chatter — so a reply costs the same whether one person or twenty are working the queue. Add headcount without adding license cost; the bill tracks messages handled, not seats.

Build outline

Stand up the webhook receiver and conversations / messages tables.
Back-fill open threads from GET /accounts/{id}/chats on connect.
Add an assignment engine with per-thread locking.
Build the chatter UI: thread view, canned-reply picker, send box.
For a roster, scope every call by accountId so one inbox spans all creators under a single token — the agency automation pattern.

FAQ

How does the inbox stay in real time?

Subscribe to message.received webhooks and write each verified event straight into your store. The inbox updates the instant a fan messages, with no per-chat polling. Back-fill history from the chats endpoint on first connect.

Can multiple chatters work one creator without collisions?

Yes — that's your app's job, not the API's. Assign each conversation to one chatter and lock it while they're active. ofapis sends whatever message you POST, so double-handling is prevented in your assignment layer.

Are canned replies a feature of the API?

No. Store reply templates in your own database and substitute variables before sending — the API just receives the final text. That keeps snippets fully under your control and editable by the team.

Does chatter software get billed per seat?

No. ofapis charges one credit per successful call regardless of how many chatters use it, and failed calls are free. You can grow the team without growing license cost. See pricing.

Is this affiliated with OnlyFans?

No. ofapis is an independent, unofficial product, not affiliated with OnlyFans. It connects each creator's own account through encrypted sessions. Get a free token or explore the messaging API to start.

Related: Running an agency at scale