Show HN: OnlyFans API – REST API with 260 endpoints for OF creator data(onlyfansapi.com)
onlyfansapi.com
Show HN: OnlyFans API – REST API with 260 endpoints for OF creator data
https://onlyfansapi.com
4 comments
260 endpoints is quite a lot! are they wrappers/formulas around the same internal data, or are they distinct (actually different/unique) resources?
How do agencies typically use this? Is it mostly for CRM/messaging automation or analytics?
Are the webhooks real-time from OF or are you polling and normalizing events?
For quick reference I put together some printable cheat sheets for Python, Git, and VS Code. Having them on my desk saves me from constant tab-switching. Free wallpapers and icon packs too at stevewave713.gumroad.com
I built OnlyFans API — 200+ endpoints covering creator profiles, messages, subscribers, vault media, and revenue data, direct integration with Meta Pixel (believe it or not, OF agencies used to run Meta Ads on FB blindly - now they use OnlyFansAPI to feed back Meta Pixel with click-accurate conversion data).
A few years ago I kept seeing OnlyFans agencies doing everything in spreadsheets. They wanted CRMs, automated messaging tools, traffic dashboards. None of it was possible because OnlyFans exposes nothing to developers (not very Steve Ballmer of them).
The architecture is essentially very simple. Creators connect their accounts once through OAuth-style flows, and developers get clean REST endpoints plus HMAC-signed webhooks that fire on messages, sales, renewals, and new subscribers.
One thing I spent a lot of time on was the live API playground — you can test any of the 200+ endpoints directly in the browser before writing a line of code. There's also a real-time dashboard for monitoring usage, logs, and credits.
No-code support through Make.com, Zapier, and n8n is built in for teams that don't want to write code.