Back to browse
OnlyFans API – REST API with 260 endpoints for OF creator data

OnlyFans API – REST API with 260 endpoints for OF creator data

by martingalovic·Mar 16, 2026·5 points·4 comments

AI Analysis

●●SolidSolve My ProblemSlick

200+ endpoints with live playground when OnlyFans offers zero official API access.

Strengths
  • HMAC-signed webhooks for messages, sales, renewals enable real-time automations without polling.
  • Live API playground lets developers test all 200+ endpoints in-browser before writing code.
  • Meta Pixel integration solves actual pain point for agencies running paid traffic blindly.
Weaknesses
  • Unofficial API carries ToS and legal risk if OnlyFans decides to crack down.
  • Niche audience limits broader appeal beyond the creator economy ecosystem.
Target Audience

OnlyFans agencies, developers building creator management tools

Similar To

RapidAPI · Apify

Post Description

Hi HN,

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.

Similar Projects

Productivity●●Solid

Video Compressor – 10x Faster via Dual-Engine (WebCodecs/WASM)

This runs entirely in the browser and routes encoding through the WebCodecs path for GPU-accelerated speed, falling back to a WASM engine when needed — that dual-engine approach is the real hook. The UI gives sensible presets (Discord, WhatsApp, email) and clear privacy messaging, but the pitch leans heavily on speed claims without visible cross-browser compatibility or quality/bitrate tradeoff details.

WizardryCrowd Pleaser
charlesding2024
114mo ago