Skip to content
Fans API logo, the company behind this Fanvue API

Fans API · APIs and developer tools

Fanvue API: Chats, Subscribers and Earnings

TL;DR

  • API for Fanvue is the Fanvue API inside Fans API. It reads and sends chat messages, lists subscribers and followers, and pulls earnings and top spenders for connected Fanvue creators.
  • It uses your existing Fans API key, credits and plan, with no extra charge per platform. Access is rolling out team by team, so you email Fans API to have it switched on.
  • Skip it if your creators aren't on Fanvue, or if you need posts, media uploads or mass messages, which the endpoints don't cover yet.
Price
Fans API plans: free, $69 or $299/mo
Product
Fans API
Platforms
Fanvue, on the same key as OnlyFans and Fansly
Free trial
Fans API has a free plan; Fanvue access is switched on per team on request

What the Fanvue API is

API for Fanvue is the Fanvue API inside Fans API. It lets developers read and act on connected Fanvue creator accounts from their own software. You can work with chats and messages, subscribers and followers, earnings and top spenders, and webhook events. It uses the same API key, credits and plans as the OnlyFans API and the Fansly API.

Access is not open to everyone yet: as of November 2026, Fans API switches Fanvue on team by team, and you request it by email. Once it is on, a Fanvue tab appears on the Accounts page. A creator connects by signing in on Fanvue in the browser, and you then use the account ID in your requests. It sits in our OnlyFans developer tools category with the other building blocks for agencies.

Key features

The Fanvue endpoints cover the work an agency does every day: answering fans, keeping subscribers and reporting on revenue. The Fanvue API reference lists 26 endpoints as of November 2026.

Chats and messages

You can list chats, read message history and send messages. You can also delete a message, mark a chat as read and show a typing indicator. These cover a shared inbox, a support tool or a follow-up queue that your chatters work from.

Subscribers, followers and smart lists

List subscribers with their subscription status, price, auto-renew setting and period end date. You can also list followers, read Fanvue’s smart lists and see which fans are online. Per-fan insights show what a single subscriber has spent.

Expiring subscribers

Fanvue itself has no filter for subscribers who are about to leave. Fans API adds one. List Expiring Subscribers returns fans whose subscription ends within 1 to 90 days and who have auto-renew turned off. Results are sorted by the soonest end date, so your team can reach them before they go.

Earnings and top spenders

Pull an earnings list, an earnings summary, a subscriber trend and your top spenders. Amounts arrive in minor units, so 1999 means $19.99 for a USD account. That is enough to feed a revenue dashboard or a weekly report.

Webhooks

Fanvue events cover payments, subscriptions, messages, follows, refunds, disputes and account connections. Every event name starts with fanvue., so it never collides with OnlyFans or Fansly events. The Fanvue webhook events page lists all 26. How delivery and retries work is covered on the OnlyFans webhooks page.

MCP tools and ad tracking

Every endpoint is also a tool on the Fans API MCP server, so Claude, ChatGPT or Manus can work Fanvue chats in plain English. The MCP connector page explains the setup. Smart Links also supports Fanvue creators, if you need to track which ads bring in paying fans.

Fanvue API code sample

This request lists subscribers whose subscription ends in the next seven days with auto-renew off. The path and Bearer header come from the Fans API documentation. Replace the account ID with one from List Accounts, and put your own key in FANS_API_KEY.

curl "https://app.fansapi.com/api/fanvue/fanvue_acct_XXXXXXXXXXXXXXX/fans/expiring?withinDays=7" \
  --header "Authorization: Bearer $FANS_API_KEY"

The response wraps Fanvue’s subscriber objects in a data key. A _meta block adds what the call cost. This is the documented example, shortened to one subscriber:

{
  "data": {
    "data": [
      {
        "uuid": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
        "handle": "sarah-jones",
        "displayName": "Sarah Jones",
        "isTopSpender": false,
        "subscription": {
          "status": "active",
          "price": 399,
          "currentPeriodEnd": "2026-09-24T10:28:59.873Z",
          "autoRenewalEnabled": false
        }
      }
    ],
    "nextCursor": null
  },
  "_meta": { "_credits": { "used": 3 } }
}

Two details matter. First, an empty data list with a nextCursor doesn’t mean nobody is expiring. It means nothing matched yet, so keep sending the cursor back until it is null. Second, one call reads up to 20 pages, so it can cost up to 20 credits.

Is the Fanvue API safe to use?

The integration works through Fanvue’s own API rather than around it. A creator connects by signing in on Fanvue in the browser and granting permissions, such as reading and writing chats. Connecting happens only in the browser, so your code never handles the password, and you can disconnect an account at any time.

Fans API refreshes Fanvue’s short-lived access tokens for you. If Fanvue rejects a refresh, the account is marked needs_reauth and stops making calls until someone reconnects it. Errors from Fanvue are passed back with Fanvue’s own status and message, so you can see a missing permission instead of guessing. We know of no independent security audit for this integration, so judge it on the setup described here.

Pricing

Fanvue costs nothing extra, because a connected Fanvue account is billed exactly like an OnlyFans or Fansly account, on the same plan and credit balance. As of November 2026, the plans on Fans API pricing are:

Plan Price Accounts included Monthly credits
Free $0 1 100 welcome credits (one-off)
Basic $69/month 1 20,000
Pro $299/month 5, then $29 per extra 100,000, plus 10,000 per extra
Enterprise On request Custom Custom

Webhooks appear in the Basic and Pro plan lists but not in Free. Most Fanvue calls cost one credit, so 20,000 credits covers a lot of inbox and reporting traffic for one creator. The expiring-subscriber scan is the expensive call, at up to 20 credits each time it runs.

Who it’s for, and who should skip it

API for Fanvue is for agencies and developers who already manage creators on OnlyFans or Fansly and are adding Fanvue. It suits teams that want one inbox, one revenue report and one webhook handler across platforms. It is also a good fit if you want win-back campaigns built on the expiring-subscriber list.

Skip it if none of your creators are on Fanvue. Skip it as well if you need to publish posts, upload media or send mass messages through code, because the endpoints don’t cover those yet. And if you need to start today, remember that access is enabled on request, so allow time for your team to be switched on.

Pros and cons

Pros

  • One API key, one dashboard and one bill for Fanvue, OnlyFans and Fansly accounts
  • A ready-made endpoint for subscribers who are about to lapse with auto-renew off
  • Responses pass Fanvue's own JSON through unchanged, so Fanvue's reference stays the field-level source of truth
  • Webhook events for payments, subscriptions, messages and follows, prefixed so they never clash with other platforms
  • Token refresh is handled for you, and every endpoint is also available as an MCP tool

Cons

  • Access isn't instant; Fanvue is enabled team by team, and until then every Fanvue endpoint returns 404
  • Coverage is narrower than on OnlyFans, with no endpoints for posts, media uploads or mass messages
  • Data shapes differ from the OnlyFans and Fansly endpoints, so shared code needs a mapping layer
  • Fanvue's own rate limit of 200 requests per minute per account still applies, whatever your Fans API plan

Frequently Asked Questions

Short answers to the questions agencies ask most.

Is there an official Fanvue API?

Yes. Fanvue publishes its own API, and creators grant access by signing in on Fanvue. Fans API sits on top of it. Each Fans API endpoint calls one Fanvue endpoint and returns Fanvue's response under a data key, adding its own credit and cache details. The advantage is that you manage Fanvue next to OnlyFans and Fansly with one key, one dashboard and one bill.

How do I get access to the Fanvue endpoints?

Email hello@fansapi.com and ask for Fanvue to be enabled for your team. Fans API is rolling Fanvue out gradually. Until it is on, the Fanvue tab doesn't appear on the Accounts page, the Fanvue endpoints answer 404 and the Fanvue webhook events aren't offered. Once it is on, you connect creators in the browser.

How many credits does a Fanvue request cost?

Each request that Fanvue answers costs one credit, including an error such as a missing permission. A rate-limit response, a Fanvue server error or a timeout costs nothing. The exception is List Expiring Subscribers, which reads up to 20 pages of subscribers in one call and charges one credit per page. Each successful response reports what it used.

Can I send Fanvue messages from my own tools?

Yes. You can list chats, read message history, send a message, delete a message, mark a chat as read and show a typing indicator for a connected Fanvue account. That is enough to build a shared inbox or a follow-up tool. There is no mass-message endpoint yet, so broadcasts to many fans still happen inside Fanvue.

Does it work with AI assistants like Claude or ChatGPT?

Yes. Every documented Fanvue endpoint is also a tool on the Fans API MCP server, with names that start with fanvue_. There is no separate server. Once Fanvue is enabled for your team, reconnect your existing connector and the tools appear. You still connect each creator account in the browser first.

What happens when a Fanvue connection expires?

Fanvue access tokens last about an hour, and Fans API refreshes them for you. If Fanvue permanently rejects the refresh, the account moves to needs_reauth and calls for it return 401 until someone reconnects it from the dashboard. The account ID stays the same after reconnecting, so your code doesn't need to change.

Verdict

API for Fanvue is the practical choice if your agency already builds on Fans API and is adding Fanvue creators. You keep one key, one credit balance and one billing model, and you get chats, subscriber data, earnings and webhooks. It is not yet a full mirror of the OnlyFans endpoints, so check the endpoint list against your plans before you request access.

Best for: Agencies adding Fanvue creators to their stack

Fans API logo

API for Fanvue

Fans API plans: free, $69 or $299/mo

Visit Site