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 Fan Segments API

Not every fan should get the same message. The ofapis lists endpoints let you group subscribers into segments — VIPs, big spenders, churn-risk, new joiners — and then target each group precisely. Segments map to OnlyFans "lists," and everything is scoped per linked account so agency rosters stay clean.

What you can do

List a creator's fan segments.
Create a new segment.
List the fans inside a segment (paginated).
Add fans to a segment, or remove one fan.
Delete a segment.

Endpoints

GET    /api/public/v1/accounts/{accountId}/lists
POST   /api/public/v1/accounts/{accountId}/lists
GET    /api/public/v1/accounts/{accountId}/lists/{listId}/users
POST   /api/public/v1/accounts/{accountId}/lists/{listId}/users
DELETE /api/public/v1/accounts/{accountId}/lists/{listId}
DELETE /api/public/v1/accounts/{accountId}/lists/{listId}/users/{targetUserId}

Every route is account-scoped — there is no global segments form, because a list belongs to exactly one creator.

Add fans to a segment

curl -X POST \
  https://api.ofapis.com/api/public/v1/accounts/42/lists/9/users \
  -H "Authorization: Bearer ofapis_sk_..." \
  -H "Content-Type: application/json" \
  -d '{"userIds":[101,102,103]}'

A successful call debits one credit; failures are free.

Create a segment

curl -X POST \
  https://api.ofapis.com/api/public/v1/accounts/42/lists \
  -H "Authorization: Bearer ofapis_sk_..." \
  -H "Content-Type: application/json" \
  -d '{"name":"VIP spenders"}'

Use cases

Spend tiers. Score fans in your own system by lifetime spend, then keep a "whales" segment in sync so a premium PPV goes only to them via the mass DM API.
Win-back. Build a churn-risk segment from fans whose subscriptions are about to lapse and target them with a discount mailing — the pairing at the heart of an OnlyFans CRM.
Onboarding. Drop new subscribers into a "just joined" segment and run a welcome sequence, then move them out once they convert.

Gotchas

Segments are membership, not queries. A list holds the fans you put in it; it does not auto-update. Re-sync from your own scoring on a schedule to keep it current.
Resolve ids first. userIds are OnlyFans user ids. Resolve handles with the profile API and enumerate your audience with the subscribers API before building a list.
Billing and pagination. One credit per successful call; page through lists/{listId}/users with the returned cursor for large segments.
Rate limits follow your plan's requests-per-minute — see pricing.

FAQ

Can I target a mailing at a single segment?

Yes. Point a mailing at the listId and the mass DM goes only to the fans in that segment.

Are segments shared across creators?

No. Every list route is scoped by accountId, so each creator's segments stay separate — clean for agency workflows.

Do segments update themselves as fans change?

No. A segment is an explicit membership list. You keep it current by adding and removing fans from your own scoring logic, typically on a schedule.

How do I get the fan ids to add?

Use the subscribers API to list your audience, or the profile API to resolve a username to an id, then pass those ids to the add-fans route.

Start free · Pricing · Build a CRM

Related: Lists API