Requests and logs
Request ids, the headers worth sending, and the request log in the dashboard.
Every request gets an id and a row in your workspace's request log. Use them to find out what happened to a call.
Request ids
Every response has an x-request-id header, and every error body repeats it as requestId. Ids look like req_7Hq2LmX9pRt4VbN8cKe3WzYa. Log it next to your own records, and include it when you ask for help.
You can choose the id yourself. Send an x-request-id header that starts with req_ followed by 16 to 32 letters and digits, and BetterFans Link uses it instead of making one. That lets you search your own logs and ours for the same id. A value in any other shape is ignored and a new id is made.
curl https://app.betterfans.link/v1/me \
-H "Authorization: Bearer $BFL_KEY" \
-H "x-request-id: req_nightlyreport20260929a"Naming your app
Send an x-bfl-client header with your app's name, such as Nightly report. The request log shows it as the client, which makes one app's traffic easy to find when several share a key. MCP clients are named for you.
The request log
In the dashboard, open Developers, then Logs. Each row is one request, kept for 30 days.
| Column | What it shows |
|---|---|
| Route | The route's name, such as List fans, with the path and query. |
| Status | The HTTP status and, for errors, the error code. |
| Duration | Total time, and how much of it was spent waiting on OnlyFans. |
| Source | synced, live or sandbox, as in meta.source. |
| Key | The key's name, or the MCP client's name. |
| Client | The app that called: your x-bfl-client value, an MCP client such as Claude Code, or Dashboard. |
| Tool | The MCP tool, when the call came from MCP. |
| Account | The account the request was about. |
Filter by status, key, account, client or route, or search by request id, path or error code. A key's page in the dashboard also shows its recent requests and request volume.
The audit log
Changes people make in the dashboard, such as creating a key, turning on writes or approving an action, go to the audit log under Workspace, then Audit log. It records who did what and when. Request logs cover API traffic; the audit log covers people.