BetterFans Link: the OnlyFans APIBetterFans Link

Synced and live reads

Reads come from synced data by default. Use fresh=true on the three routes that support it when the answer must be current.

Product page: OnlyFans, Fansly and Fanvue API coverage

BetterFans Link keeps a synced copy of each linked OnlyFans and Fansly account. Reads come from that synced data by default. They are fast, they do not use the creator's session on OnlyFans or Fansly, and they keep working when the platform asks the creator to sign in again. Fanvue accounts are the exception: see Fanvue reads are always live.

meta.asOf says how old the synced data in a response is. On a Fansly account, new messages, sales and subscribers usually arrive within a minute, and meta.asOf is when the last full sync finished, about every 30 minutes. The data can be newer than meta.asOf.

How old is the data

Every response says where its data came from in meta. A response for one account also names its platform in meta.platform, onlyfans, fansly or fanvue.

meta.sourceMeaningmeta.asOf
syncedRead from the synced copy.When the data was last synced from the platform, or null for data that is not synced from the platform, such as actions and links.
liveRead straight from the platform for this request.null
sandboxTest mode data from the sandbox creators.See test mode.

An account also has lastSyncedAt. Check it, or meta.asOf, before you tell someone that nothing happened recently.

Reading live with fresh=true

Three routes take fresh=true and read straight from the platform instead of synced data.

RouteMCP toolPlatformsUse it when
List messagesget_chatOnlyFans and FanslyYou are about to reply and need the last few messages.
Get fanget_fanOnlyFans and FanslyYou need the fan's current subscription or profile.
Online fansonline_fansOnlyFans and FanslyYou want to know who is online right now.

On a Fansly account, a live read of messages works only for a chat the account already has with that fan, a live read of a fan returns the fan's profile, and a live read of online fans checks up to 500 fans. Every other Fansly read comes from synced data.

Fanvue reads are always live

BetterFans Link keeps no copy of a Fanvue account. Every read of one asks Fanvue at that moment, so meta.source is live, meta.asOf is null, the account's lastSyncedAt is null, and each read counts as one live call. fresh=true changes nothing on a Fanvue account. A Fanvue read never marks a chat read. When Fanvue errors or is slow, the read fails with fanvue_error or fanvue_timeout, and there is no synced copy to fall back on.

Live reads are slower and each one calls the platform with the creator's session. Use them for the one answer that must be current, not for bulk reads or reports. Other routes ignore fresh.

A live read can fail where a synced read would not.

Chats stay unread

On OnlyFans, opening a chat marks it read, which would hide a new message from the creator. A live read of an OnlyFans chat's messages keeps the thread's unread state as it was. In the rare case that BetterFans Link cannot restore it, the response says so:

"meta": {
  "source": "live",
  "asOf": null,
  "requestId": "req_7Hq2LmX9pRt4VbN8cKe3WzYa",
  "platform": "onlyfans",
  "sideEffects": ["thread_marked_read"]
}

sideEffects is absent when nothing changed. If you see thread_marked_read, tell the creator that the chat may look read in OnlyFans.

Presence

Online status is a best guess. A fan missing from Online fans is not known to be offline, and a fan's presence of unknown does not mean offline. Do not tell anyone a fan is offline unless presence is offline.

Calling the platform directly

Call OnlyFans, Call Fansly and Call Fanvue always read live, so their responses have meta.source set to live. Each works only for accounts on its own platform. Prefer the routes above; use them only for data they do not cover.

A newly linked account

An account in syncing status was just linked: in the last 30 minutes on OnlyFans, or before its first full sync finished on Fansly. Its history is still filling in, so totals and lists can be short. See account status.

On this page