BetterFans Link: the OnlyFans APIBetterFans Link

OnlyFans, Fansly and Fanvue API reference

OnlyFans, Fansly and Fanvue API reference for BetterFans Link: the base URL, API key authentication, the response envelope, pagination and routes.

Product page: OnlyFans, Fansly and Fanvue API coverage

Every route, grouped the way the sidebar groups them. This page covers what all routes share.

Base URL

https://betterfans.link/v1

The OpenAPI 3.1 description covers every route, its parameters, responses and errors, and the webhook events.

Authentication

Send your key as a bearer token in the Authorization header. The x-api-key header works too. Keys that start with bfl_live_ read linked accounts; keys that start with bfl_test_ read the sandbox creators. See keys and scopes.

curl https://betterfans.link/v1/me \
  -H "Authorization: Bearer $BFL_KEY"

Responses

A single object comes back in data, with meta next to it:

{
  "data": {
    "id": "412345678",
    "username": "jessrivers"
  },
  "meta": {
    "source": "synced",
    "asOf": "2026-09-28T13:58:40Z",
    "requestId": "req_7Hq2LmX9pRt4VbN8cKe3WzYa",
    "platform": "onlyfans"
  }
}

A list adds hasMore and nextCursor:

{
  "data": [
    {
      "id": "38291045"
    },
    {
      "id": "51820377"
    }
  ],
  "hasMore": true,
  "nextCursor": "q8ZtR2vN5xWcL7mK4pBd",
  "meta": {
    "source": "synced",
    "asOf": "2026-09-28T13:58:40Z",
    "requestId": "req_7Hq2LmX9pRt4VbN8cKe3WzYa"
  }
}

Meta

FieldTypeDescription
sourceenumsynced for synced data, live for a read straight from the platform, sandbox in test mode.
asOftimestamp or nullWhen the data was last synced from the platform; null for live reads, which every Fanvue read is.
requestIdstringThe request id, also sent in the x-request-id response header.
platformenumOptional. The account's platform, on every route that takes an accountId. One of onlyfans, fansly or fanvue.
sideEffectsarray of enumsOptional. Present only when a live read changed something on the platform. thread_marked_read means a fresh=true chat read on OnlyFans could not restore the unread state. Each one of thread_marked_read.

Lists

FieldTypeDescription
dataarrayThe items on this page.
hasMorebooleanWhether another page follows.
nextCursorstring or nullPass it as cursor to get the next page. null on the last page.

Pagination

Routes that take cursor and limit return one page at a time. limit is 25 by default. A limit above 100 is treated as 100; a limit below 1, or one that is not a whole number, is invalid_parameter. Pass nextCursor back as cursor until hasMore is false. A cursor belongs to one list with one set of filters: keep the other parameters the same while you page.

async function allFans(accountId: string) {
  const fans = [];
  let cursor: string | null = null;
  do {
    const url = new URL(`https://betterfans.link/v1/accounts/${accountId}/fans`);
    url.searchParams.set("limit", "100");
    if (cursor) url.searchParams.set("cursor", cursor);
    const res = await fetch(url, { headers: { Authorization: `Bearer ${process.env.BFL_KEY}` } });
    const body = await res.json();
    if (!res.ok) throw new Error(`${body.error.code}: ${body.error.message}`);
    fans.push(...body.data);
    cursor = body.hasMore ? body.nextCursor : null;
  } while (cursor);
  return fans;
}

Conventions

  • Every account lives on one platform, OnlyFans, Fansly or Fanvue. The same routes serve every platform. Each route lists the platforms it works for; an account on any other platform gets not_supported_on_platform. Routes that take an accountId say the account's platform in meta.platform.
  • Ids are strings, even when they look like numbers. An account id is the creator's user id on its platform; a fan id is the fan's user id on that platform and also the chat id. Fansly ids are too large for a JavaScript number to hold exactly, and Fanvue ids are lowercase UUIDs, so never parse an id into a number.
  • Every read of a Fanvue account asks Fanvue at that moment: meta.source is live, meta.asOf is null and the read counts as a live call.
  • Timestamps are ISO 8601 strings in UTC. from and to take a date (2026-09-01) or a timestamp.
  • Money is an object with integer cents and a currency. See money.
  • Unknown query parameters are ignored, except on Call OnlyFans, Call Fansly and Call Fanvue, which refuse a query parameter the platform endpoint does not take. A known parameter with a bad value is invalid_parameter.
  • Every response has an x-request-id header. Errors repeat it as requestId.

Errors

Errors come back with an HTTP status and a JSON body with a stable error.code. Every route can also return the authentication errors, rate_limited and internal_error. Each route lists its own errors. The errors page explains every code.

Routes

Workspace

RouteMethod and pathScopePlatforms
Who am IGET /v1/mereadOnlyFans, Fansly and Fanvue

Accounts

RouteMethod and pathScopePlatforms
List accountsGET /v1/accountsreadOnlyFans, Fansly and Fanvue
Create linkPOST /v1/linksreadOnlyFans, Fansly and Fanvue
Get linkGET /v1/links/{linkId}readOnlyFans, Fansly and Fanvue
Get accountGET /v1/accounts/{accountId}readOnlyFans, Fansly and Fanvue

Fans

RouteMethod and pathScopePlatforms
List fansGET /v1/accounts/{accountId}/fansreadOnlyFans, Fansly and Fanvue
Get fanGET /v1/accounts/{accountId}/fans/{fanId}readOnlyFans, Fansly and Fanvue
Fan listsGET /v1/accounts/{accountId}/listsreadOnlyFans, Fansly and Fanvue
Online fansGET /v1/accounts/{accountId}/online-fansreadOnlyFans, Fansly and Fanvue

Chats

RouteMethod and pathScopePlatforms
List chatsGET /v1/accounts/{accountId}/chatsreadOnlyFans, Fansly and Fanvue
List messagesGET /v1/accounts/{accountId}/chats/{fanId}/messagesreadOnlyFans, Fansly and Fanvue
Search messagesGET /v1/accounts/{accountId}/messages/searchreadOnlyFans and Fansly
Show typingPOST /v1/accounts/{accountId}/chats/{fanId}/typingwriteOnlyFans, Fansly and Fanvue

Money

RouteMethod and pathScopePlatforms
Revenue summaryGET /v1/accounts/{accountId}/revenuereadOnlyFans, Fansly and Fanvue
List transactionsGET /v1/accounts/{accountId}/transactionsreadOnlyFans, Fansly and Fanvue

Content

RouteMethod and pathScopePlatforms
Mass messagesGET /v1/accounts/{accountId}/mass-messagesreadOnlyFans and Fanvue
Top contentGET /v1/accounts/{accountId}/postsreadOnlyFans, Fansly and Fanvue
Tracking linksGET /v1/accounts/{accountId}/linksreadOnlyFans, Fansly and Fanvue
VaultGET /v1/accounts/{accountId}/vaultreadOnlyFans, Fansly and Fanvue

Call OnlyFans

RouteMethod and pathScopePlatforms
Call OnlyFansGET /v1/accounts/{accountId}/onlyfans/{path}readOnlyFans

Call Fansly

RouteMethod and pathScopePlatforms
Call FanslyGET /v1/accounts/{accountId}/fansly/{path}readFansly

Call Fanvue

RouteMethod and pathScopePlatforms
Call FanvueGET /v1/accounts/{accountId}/fanvue/{path}readFanvue

Actions

RouteMethod and pathScopePlatforms
Create actionPOST /v1/accounts/{accountId}/actionswriteOnlyFans, Fansly and Fanvue
Get actionGET /v1/actions/{actionId}readOnlyFans, Fansly and Fanvue
List actionsGET /v1/actionsreadOnlyFans, Fansly and Fanvue

On this page