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 Multi Account Management

OnlyFans multi account management from one system comes down to two problems: addressing the right creator on every call, and isolating each account so one model's activity never leaks into another's. ofapis solves both with scoped routes under a single token — accountId is your tenant key, and each connected account gets its own encrypted session and dedicated proxy.

The roster model

Connect each creator once in the dashboard. From then on every endpoint has an account-scoped form — same route, one extra path segment:

GET  /accounts/{accountId}/subscribers
GET  /accounts/{accountId}/chats
POST /accounts/{accountId}/mailings
POST /accounts/{accountId}/scheduled/posts

Store the accountId of each connected model in your own table and treat it as a foreign key on every row you persist. One collector, one worker, one bill — the only thing that changes per creator is that path segment:

# Same code, different tenant
for ID in acct_11 acct_22 acct_33; do
  curl "https://api.ofapis.com/api/public/v1/accounts/$ID/notifications/count" \
    -H "Authorization: Bearer ofapis_sk_..."
done

Isolation, handled server-side

Multi-account tooling that drives raw browser sessions eventually gets accounts flagged for cross-contamination. ofapis avoids that:

One encrypted session per account, kept alive server-side — no refresh cron on your side, no shared cookies.
A dedicated proxy per creator, so each account keeps a stable, consistent network fingerprint.
No cross-talk — a call scoped to acct_11 can never touch acct_22's data, because the session and proxy are bound to the id.

This is what makes a roster safe to run from a single codebase. More on the model: is the OnlyFans API safe?.

One token, one bill

Every account on the roster shares the same API key and the same metered pool. Billing is per successful call regardless of which creator it targets, and failed calls (expired session, upstream error) are never charged — so cost tracks real activity, not seat count or headcount. Plan limits cap how many accounts you can connect:

Plan	Accounts	Notes
Free / Starter	1	Single creator
Pro	5	Small roster
Enterprise	Unlimited	SLA, custom limits

Build outline

Link each creator in the dashboard and record its accountId.
Keep a accounts table (account_id, display_name, status) as your roster.
Make every worker take accountId as a parameter and template it into the path.
Fan out jobs — sync, broadcast, schedule — across the roster in a loop.
Attribute credit spend per accountId from your own logs for per-creator cost reporting.

This is the foundation the agency automation patterns build on.

FAQ

How do I target a specific creator on each call?

Put the creator's accountId in the path: /accounts/{accountId}/.... Every endpoint has this scoped form, so the same code serves any model by swapping the id.

Are accounts isolated from each other?

Yes. Each connected account has its own encrypted session and dedicated proxy, bound to its accountId. A scoped call can only read or write that one account's data — there is no shared session state.

Do I need a separate token or bill per account?

No. One API key covers the whole roster and everything draws from a single metered credit pool. You are charged per successful call, not per account or per seat.

How many accounts can I connect?

Free and Starter cover one account, Pro links up to five, and Enterprise is unlimited with an SLA. See pricing for the full breakdown, then create a free account to start.

Is ofapis affiliated with OnlyFans?

No. ofapis is an independent, unofficial product, not affiliated with OnlyFans. It connects each creator's own account through encrypted sessions you authorise.

Related: Running an agency at scale