Developer platform
Introduction
The FansMetric API gives you programmatic access to the OnlyFans surface — chats, messages, fans, subscribers, lists, notifications, mass messages — plus FansMetric resources like tracking links, trial links, and tags. Authenticate with an API key; each key carries a set of per-route permissions.
Current plan
Base URL: https://public-api.buffmetrics.com. All routes live under /v1/. See the API Reference for the response envelope and per-route details.
What the API does
Most endpoints expose your connected OnlyFans accounts in real time — the API keeps the session and authenticates requests on your behalf. Tags are FansMetric-native. Tracking links and trial links are hybrid: list endpoints are pure OF passthrough, while GET by id and POST (create) responses also carry FansMetric revenue enrichment from our database.
FansMetric-native response fields are prefixed with fm (for example fmRevenue, fmTags). They appear on tag responses and on the single-item / create responses for tracking and trial links. Everything else comes from OnlyFans as-is.
- Read endpoints: accounts, chats, messages, subscribers, fans, notifications, lists, GIFs
- Write endpoints: send/like/pin messages, mass messages, hide/mute/delete chats, block/report/restrict users, manage user lists
- FansMetric resources: tags (org-wide), plus revenue enrichment on single-item / create responses for tracking and trial links
Envelope and conventions
Successful responses are wrapped in { data, _pagination?, _meta }. The _meta block carries credit usage and rate-limit headroom on every authenticated response. Error responses use a flat { error: "..." } body and do not include the envelope.
- Auth:
Authorization: Bearer fm_api_...orX-API-Key: fm_api_... - Permissions are per-route and enforced by API key role
- Rate limits are per-organization (default 1000/min, 50000/day)
- Pagination is offset-based or cursor-based depending on the endpoint