Call OnlyFans

Prefer the dedicated routes, which read synced data and return documented objects. This one calls OnlyFans live and returns its response, with tokens, passwords, emails and phone numbers removed. Every route can also return the authentication errors, rate_limited and internal_error.

Call OnlyFans

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

Runs a read-only OnlyFans API GET for an account, with the account's session. Use it for data the other routes do not cover.

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

data is the JSON OnlyFans returned. OnlyFans returns many more fields than this example shows.

Query parameters you add are passed on to OnlyFans, so .../onlyfans/chats?limit=10 reads chats?limit=10.

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

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

Path parameters

Returns

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

Example request

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

Example response

{
  "data": {
    "id": 412345678,
    "username": "jessrivers",
    "name": "Jess Rivers"
  },
  "meta": {
    "source": "live",
    "asOf": null,
    "requestId": "req_7Hq2LmX9pRt4VbN8cKe3WzYa",
    "platform": "onlyfans"
  }
}

Errors