Release

August 17, 2026

32 new endpoints across posts, post labels, bookmarks, chat and chatter analytics, and tracking and trial links. Nothing you already call was removed, and no existing response field changed meaning.

Current plan

Releases are dated rather than numbered — there is no v2 to migrate to, and nothing to pin a request to. They reach every organization at the same time and are additive by default: we add endpoints and fields rather than change the ones you already read. Read responses loosely, because new fields turn up without a release of their own, and a parser that rejects unknown keys will fail on a change meant to be invisible.

What's new

The largest release since the API opened up. In practice it unlocks three things: a posts surface complete enough to browse and act on, messaging analytics per account and per chatter, and revenue, cost and tags attached to individual tracking and trial links instead of stitched together on your side.

Posts — 10 endpoints. Browse the creator's feed, open a single post, read its stats and comments, and like, pin, archive or bookmark it.
Post Labels — 5 endpoints. Read the creator's own labels and move posts in and out of them.
Bookmarks — 2 endpoints. Read the Saved for later collection and the categories it is filed under.
Chat — 2 endpoints. Per-account messaging KPIs, as a headline card and as a chart.
Chatters — 3 endpoints. Organization-wide chatter performance: a ranked list, a side-by-side comparison, and a totals table.
Tracking and trial links — 10 endpoints. Per-link stats, per-link tags, and a FansMetric-backed list carrying revenue, cost and tags.

Posts, labels and bookmarks

Enough to build a posts tab end to end. List Posts returns the creator's own feed with filters for media type, label, caption text and pinned state; Get Post opens a single one; Get Post Statistics and List Post Comments fill in a detail panel.

The action endpoints write back to OnlyFans — Like Post, Pin Post, Archive Post, Unarchive Post, Bookmark Post and Remove Post Bookmark.

Labels are what OnlyFans calls collections: named buckets a creator drops posts into, which double as filter chips on their public profile. List Post Labels returns them with preview thumbnails, List Post Label Filters returns the same set shaped for a filter bar, and Get Post Label, Add Posts to Label and Remove Post from Label cover the rest.

List Bookmarks returns the Saved for later collection and List Bookmark Categories returns the buckets it is filed under.

Like and Pin are toggles. OnlyFans has no separate unlike or unpin for posts, so a second call reverses the first — drive your button state from what the response says, not from what you assume the call did.
The post feed pages by cursor, not by page number. Follow _pagination.next_page instead of building a numbered pager.
A label id is a number for the creator's own labels and a word for the two archive buckets, so check its type before treating it as a number.
Bookmarks mix saved posts and saved chat messages in one feed. Branch on responseType before rendering a row, or narrow to one kind with entity_type.

Chat and chatter analytics

Chat Overview returns an 11-stat headline for one connected account over a date window, each stat carrying the previous window's value and the percent change — so a comparison tile costs one call rather than two. Chat Chart returns the same measures bucketed over time for a trend line.

The chatter endpoints work organization-wide. List Chatters is the ranked list you would populate a selector from, Compare Chatters puts up to five of them side by side across the same 11 stats, and Chatter Report returns that data as a table with a totals row.

The 11 stats always come back in the same order, so a dashboard tile bound to a position stays put.
Compare puts every chatter on the same bucket axis, so their series overlay without you padding them first.
The totals row on Chatter Report spans every chatter matching your filter, not just the page you are looking at — don't rebuild it by summing pages.

Tracking and trial links

Both resources are now served two ways, and the URL picks which. The bare path relays OnlyFans live; the same path under /fm/ serves the FansMetric database with revenue, cost and tags attached. The pair sits together in the sidebar, badged OF for the live relay and FM for the FansMetric view.

Get Tracking Link Stats and Get Trial Link Stats return cumulative totals plus daily and monthly series for a single link — enough for a per-link detail page without pulling the whole list first.

Six endpoints manage tags on an individual link: list, add and remove for tracking links and the same three for trial links. Tags are addressed by name, and adding preserves the ones already there.

The FansMetric lists — tracking, trial — carry revenue, cost and tags, plus search, tag_ids and include_hidden filters the live relay does not have.
Freshness is the trade. The relay is live; the FansMetric view is refreshed by our scraper, roughly every 30 minutes for tracking links and every 2 hours for trial links.
limit on both link lists is capped at 25.
Get Earnings Chart gained five more by values — tips_profile, tips_post, tips_chat, tips_stream and tips_story — so tips can be split by where they came from.

Renamed in the docs

Naming only. Every path and permission stayed exactly where it was, and no request you send today behaves differently.

The Campaigns section folded into Tracking Links. GET /v1/{account_id}/campaigns still answers as before and is documented as an alias on List Tracking Links.
Get Campaigns Chart and Get Campaigns Overview are now Get Tracking Links Chart and Get Tracking Links Overview. Their paths still read /campaigns/... because that is what the API serves; the retired documentation URLs redirect.

Docs improvements

The reference passed 160 endpoints in this release, so most of the work went into finding things inside it.

A filter box under API Reference in the sidebar. Type part of a title or a path and the tree collapses to matches, each carrying its method and its section — titles repeat across sections, so both matter.
Search no longer matches the HTTP method. Typing get used to return every GET endpoint in the reference; it now returns the routes actually named Get ….
Cross-references and emphasis in the copy render as links and bold text instead of printing raw markdown.
Try it now sends a request body on DELETE endpoints. Five of them take one — per-link tag removal for tracking and trial links, unlike message, delete media, and remove media from list — and Send used to come back 400 on all five even though the sample beside it was correct.
Every navigation group and section has an icon, and the sidebar scrolls the active route into view when you land on a deep link.

Before you call the new endpoints

Each new endpoint ships with its own per-route permission, and keys you already issued do not pick those up on their own.

An organization admin needs to add the new permissions to the role your key uses, under Public API → Roles in the FansMetric app. Until that happens the new endpoints answer 403 even though the key itself is valid.
Every reference page names the permission slug it needs, so you can check a role against the pages you plan to call.
Nothing else is required. No field changed meaning and no endpoint was removed, so anything already in production keeps working untouched.
This page is the summary of what moved. The endpoint pages stay the source of truth for parameters, payloads and permissions.

Auth

List Accounts