Changelog and versioning
What changed in the BetterFans Link API, MCP server and webhooks, newest first, and which kinds of change can reach your code without a new version.
Product page: OnlyFans, Fansly and Fanvue API coverage
This page lists the changes your code or your AI agent can notice: new routes, fields and tools, changed behavior, and fixes that change an answer. Dashboard changes are not listed.
Versioning
Every REST path starts with /v1. Within v1, these changes ship at any time, without notice:
- New routes, MCP tools, webhook event types and optional query parameters.
- New fields in responses, in webhook payloads and in an MCP tool's
structuredContent. - New values in a field with a fixed list of values, such as a transaction's
typeor an account'sstatus. Code that branches on one of these fields should have a path for a value it does not know. - New error codes. Handle a code you do not know by its
error.type. - New wording in
error.message,statusReasonand other sentences written for people. Never match on them.
These changes would break working code, so they never ship within v1:
- Removing or renaming a route, a field, an MCP tool or a tool argument.
- Changing a field's type, or letting a field that is never null become null.
- Making an optional query parameter, body field or tool argument required.
- Changing how a webhook signature is computed.
If one of them is ever needed, it ships under a new version, announced on this page first, and v1 keeps working beside it.
What versioning does not cover
Call OnlyFans, Call Fansly, Call Fanvue and the MCP tool call_api return the platform's own response. OnlyFans and Fansly change their endpoints without notice, so those answers can change shape at any time, and so can the query parameters each endpoint takes. describe_endpoint marks an endpoint the platform has stopped using with removed, and gives removedOn when the date is known. Move to another endpoint for the same data before it goes.
November 2026
November 11
- Fanvue accounts work across the REST API, hosted links, webhooks and the MCP server, in Beta. A creator connects with Fanvue's own sign-in, and every read of a Fanvue account is live. See Fanvue.
- Fanvue accounts send the shared webhook events and the
fanvue.*events, Fanvue's own notifications passed on. - Call Fanvue reads a Fanvue endpoint from the reviewed list, and
search_api,describe_endpointandcall_apiwork with Fanvue accounts.
November 9
- Where Fansly data differs lists every field a Fansly account answers differently, with the values it can take on each platform.
- The API reference and
/openapi.jsonshow a Fansly example beside the OnlyFans one on every route both platforms serve. - Call OnlyFans and Call Fansly refuse a query parameter the platform endpoint does not take. The answer is
invalid_parameter, witherror.paramnaming it. describe_endpointreturnssincewhen the platform started using an endpoint recently, andremovedandremovedOnwhen it has stopped.
November 8
- The REST API and the webhook events are described in OpenAPI 3.1 at
/openapi.json. - MCP tools lists every tool's arguments, an example call and what it returns.
search_api,describe_endpointandcall_apiwork with Fansly accounts. Passplatform, or anaccountIdto use that account's platform.- A Fansly account's
statusfollows its connection, as an OnlyFans account's does. It stayshealthywhile Fansly answers, and becomesneeds_relinkwhen Fansly signs the session out. Before, a late refresh turned it tosyncing, which sentaccount.status_changedevents that needed no action.
October 2026
- The
RateLimit-Limit,RateLimit-RemainingandRateLimit-Resetheaders describe whichever limit is closer, the key's or the workspace plan's. See rate limits. - Hosted links open in a popup or a modal on any site with the connect script. See Connect in your app.
- Fansly accounts work across the REST API, hosted links, webhooks and the MCP server, including online fans. See Fansly.
- An owner or admin can let a key auto-approve its writes. See API keys and scopes.
- Call OnlyFans reaches only the reviewed endpoint list, and removes tokens, passwords, emails and phone numbers from each answer.