OnlyFans Lists API

Lists are OnlyFans' native way to group fans — the built-in ones like Fans, Following, and Friends, plus any custom collection a creator makes. The ofapis lists endpoints expose that primitive over REST: enumerate a creator's lists, read who's inside one, add and remove members, and — most usefully — pass a listId as the target of a message or mailing so a send lands on exactly that collection. Every route is account-scoped; a list belongs to one creator.

What you can do

• List every list on an account, built-in and custom.
• Read the members of a list (paginated).
• Create a custom list.
• Add fans to a list, or remove one fan.
• Delete a custom list.

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}

Read a list's members

curl "https://api.ofapis.com/api/public/v1/accounts/42/lists/9/users?limit=50&offset=0" \
  -H "Authorization: Bearer ofapis_sk_..."

The members route paginates — walk offset by your limit for a big collection. Each successful page is one credit; failures are free.

Add fans to a list

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]}'

userIds are OnlyFans user ids — resolve handles first with the creator profile API.

Addressing sends to a list

The point of a list is targeting. Once a listId holds the right fans, hand it to a broadcast: create a mailing against that list with the mass DM API and the dispatch reaches only those members. The list is the addressable object; the mailing is the send. This split lets you reuse one curated collection across many campaigns without re-specifying recipients each time.

Lists vs. segments

A list is the raw OnlyFans grouping. If you want strategy on top — churn-risk scoring, spend tiers, auto-rebuilt cohorts — read the fan segments API, which is the same underlying resource framed for targeting logic. Use lists when you care about the collection object itself; use segments when you care about the audience math.

Gotchas

• Built-in lists are read-mostly. System lists like Fans and Following reflect OnlyFans state — you enumerate them, but you manage membership on your own custom lists.
• Membership is explicit, not a query. A list holds exactly the fans you put in it; it never auto-updates. Re-sync from your own logic on a schedule.
• Resolve ids before adding. Enumerate your audience with the subscribers API to get the userIds you need.
• Billing and rate limits. One credit per successful call; pace to your plan's requests-per-minute — see pricing.

FAQ

Can I send a message to everyone on a specific list?

Yes. Create a mailing that targets the list's listId and the dispatch reaches only its members. The list is the addressable target; the mass DM endpoint performs the send.

Do the built-in OnlyFans lists show up in the API?

Yes. Enumerating an account's lists returns both the native lists — Fans, Following, Friends and the like — and any custom collections. Membership management applies to your custom lists.

Are lists shared between creators on an agency plan?

No. Every list route is scoped by accountId, so each linked creator's lists stay isolated even under one API key.

How is this different from the fan segments API?

They sit on the same list resource. The lists API is about the collection object and addressing sends to it; the fan segments API frames the same routes around targeting strategy like spend tiers and win-back cohorts.

Start free · Build a CRM · Pricing