BetterFans Link: the OnlyFans APIBetterFans Link

Read other Fanvue endpoints

Read a Fanvue API endpoint from the reviewed list that no other route covers, for a linked Fanvue account with a live key. Reads only.

Product page: Fanvue API

Prefer the dedicated routes, which return documented objects. This one calls Fanvue and returns its JSON as Fanvue sent it, with emails, phone numbers and tokens removed. Every route can also return the authentication errors, rate_limited and internal_error.

RouteMethod and pathPlatforms
Call FanvueGET /v1/accounts/{accountId}/fanvue/{path}Fanvue

Call Fanvue

GET /v1/accounts/{accountId}/fanvue/{path}

Runs a read-only Fanvue API GET for an account, with the access the creator gave BetterFans Link. Use it for data the other routes do not cover. Fanvue support is in Beta.

Needs the read scope. Always a live read. Works for Fanvue accounts only. Other accounts get not_supported_on_platform.

data is the JSON Fanvue returned, with emails, phone numbers and tokens removed. Fanvue returns many more fields than this example shows.

Query parameters are passed on to Fanvue, so .../fanvue/chats?size=10 reads chats?size=10. Each endpoint takes only the query parameters its Fanvue reference lists. Any other returns invalid_parameter, with error.param naming it. The MCP tool describe_endpoint lists the ones worth sending.

Only GET works. To change anything on Fanvue, create an action.

It needs a live key. Test keys never reach Fanvue, so with a test key this route returns resource_not_found.

Path parameters

NameDescription
accountIdThe account's id, which is the creator's Fanvue user id, a UUID. Get it from GET /v1/accounts.
pathThe Fanvue API path to read, for example users/me. The MCP tools search_api and describe_endpoint help find paths.

Returns

200 with the Fanvue response in data. meta.source is live and meta.asOf is null.

Example request

curl "https://betterfans.link/v1/accounts/7c1e4b52-93d8-4f0a-b6e1-2d5a8c90f417/fanvue/users/me" \
  -H "Authorization: Bearer $BFL_KEY"

Example response

{
  "data": {
    "uuid": "7c1e4b52-93d8-4f0a-b6e1-2d5a8c90f417",
    "handle": "noalind",
    "displayName": "Noa Lind",
    "isCreator": true
  },
  "meta": {
    "source": "live",
    "asOf": null,
    "requestId": "req_7Hq2LmX9pRt4VbN8cKe3WzYa",
    "platform": "fanvue"
  }
}

Errors

CodeStatusWhen
account_not_found404The account is not linked to your workspace, your key's account list leaves it out, or, with a test key, it is not a sandbox creator.
not_supported_on_platform400The account is not on Fanvue.
resource_not_found404The key is a test key, or the endpoint is one BetterFans Link does not pass through. Webhook, agency and app endpoints are never passed through.
account_unavailable409The account's status stops live calls. See error.accountStatus.
fanvue_error502Fanvue returned an error.
fanvue_timeout502Fanvue did not answer in time.
invalid_parameter400path is not a Fanvue API path, for example because it has .. in it or is over 512 characters. Or a query parameter is one the endpoint does not take, and error.param names it.
method_not_allowed405Any method other than GET.

On this page