Developer platform
Getting Started
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.fansmetric.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 served both ways, and the URL picks which: the bare path relays OnlyFans live, while the same path under /fm/ serves FansMetric's own database with revenue, cost and tags attached.
FansMetric-native responses no longer use fm-prefixed field names. A FansMetric-backed endpoint is identified by its badge and, for the link lists, by the /fm/ path segment; its response is one canonical camelCase item with nested revenue, cost, tags and links objects. Relay endpoints return OnlyFans' payload 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 the
/fm/link lists and on single-item / create responses for tracking and trial links GET /v1/{account_id}/tracking-linksrelays OnlyFans;GET /v1/{account_id}/fm/tracking-linksreturns our data. Same split fortrial-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
- Photos and videos come back as FansMetric links that expire after 2 hours — see Media URLs