BetterFans Link: the OnlyFans APIBetterFans Link

Account status

The seven account statuses, which ones stop live calls, and what to do about each.

Product page: OnlyFans agency API

Every account has one status in plain words. Read it before a long task, and whenever a call fails with account_unavailable.

The statuses

StatusLabelLive callsWhat it meansWhat to do
healthyHealthyWorkThe session works and the account is syncing.Nothing.
syncingSyncingWorkLinked in the last 30 minutes. The first sync is still running.Read as usual. History fills in over the next minutes, so totals can be low until then.
needs_relinkNeeds relinkStopped with account_unavailableThe platform signed the session out, or a Fansly sign-in failed.Send the creator a new hosted link. The synced history stays in place.
awaiting_2faAwaiting 2FAStopped with account_unavailableThe platform asked for a two-factor code.Send the creator a hosted link so they can enter the code.
awaiting_selfieAwaiting selfieStopped with account_unavailableOnlyFans asked for face verification. Fansly accounts never use it.Send the creator a hosted link so they can finish the selfie check.
restrictedRestrictedStopped with account_unavailableOnlyFans limited the account. Fansly accounts never use it.The creator has to resolve it with OnlyFans. BetterFans Link cannot lift a restriction.
disconnectedDisconnectedStopped with account_unavailableThere is no usable session.Send the creator a hosted link to connect the account again.

statusReason holds one plain sentence about a status that is not healthy. Show it to people as it is.

Fansly accounts

A Fansly account uses five of the statuses: healthy, syncing, awaiting_2fa, needs_relink and disconnected. Fansly has no selfie step and no restriction, so a Fansly account is never awaiting_selfie or restricted.

  • healthy when the session works. A newly linked account is syncing until its first full sync finishes.
  • awaiting_2fa while the sign-in waits for the code Fansly sent.
  • needs_relink when the sign-in failed, or when it worked and the session has since ended.
  • disconnected in every other case.

When live calls stop

Five statuses stop every live call on the account: needs_relink, awaiting_2fa, awaiting_selfie, restricted and disconnected. While the account is in one of them:

  • Reads without fresh=true keep working and say how old they are in meta.asOf.
  • Live reads, such as fresh=true, Call OnlyFans and Call Fansly, fail with 409 account_unavailable. The error's accountStatus holds the status.
  • Writes need a working session too. Wait for the account to be healthy before you ask for one.
{
  "error": {
    "type": "account_unavailable",
    "code": "account_unavailable",
    "message": "The platform is not accepting calls for this account right now.",
    "hint": "See error.accountStatus. Reads without fresh=true still work.",
    "accountStatus": "needs_relink",
    "docsUrl": "https://betterfans.link/docs/errors#account-unavailable"
  },
  "requestId": "req_7Hq2LmX9pRt4VbN8cKe3WzYa"
}

Do not retry account_unavailable in a loop. The status changes only when the creator acts, or when OnlyFans lifts a restriction.

Fixing a status

Most statuses need the creator. Create a hosted link from the Linking page or with Create link and send it to them. The hosted page walks them through signing in again, entering a 2FA code or taking the selfie. The synced history stays in place, and when they finish the account goes back to healthy.

restricted is different. OnlyFans limited the account, and only the creator can resolve that with OnlyFans. It never happens on Fansly.

Watching for changes

Subscribe to account.status_changed to hear about a change as it happens, with the previous and the new status. List accounts and the MCP tool account_health return the current status at any time.

On this page