One clean, always-current JSON API for messages, fans, transactions and attribution. No signing to maintain. No rules treadmill. Just the data — the moment it happens.
$ curl https://api-only.fans/v1/creators/128/messages \ -H "Authorization: Bearer sk_live_••••••" { "creator_id": 128, "count": 2, "data": [ { "id": "msg_5f3a91", "fan_id": 585977745, "from": "fan", "text": "still doing customs?", "price": 0, "is_tip": false }, { "from": "creator", "text": "yes — $40 for 3 min", "price": 40, "created_at": "2026-08-14T12:43Z" } ] }
Stop stitching together scrapers and brittle endpoints. Pull the whole picture of a creator's account through a single, consistent API.
Complete conversation history — text, price, tips, PPV, sender and timestamps. Backfill or stream new messages as they arrive.
The full roster with subscribe dates, lifetime spend and where each fan came from — down to the ad click.
Every payout event — subscriptions, tips, PPV and customs — deduplicated and reconciled, ready for your ledger.
Tie subscribers back to visits, campaigns and geography. The join that ad platforms and your CAPI actually need.
Subscribe to new messages, subscribers and payments. Push events to your stack the moment they happen.
The account signs its own calls — we read the results. Nothing to patch when OnlyFans rotates its rules. It just keeps working.
Predictable resources, cursor pagination, bearer auth. JSON in, JSON out.
Most APIs replicate OnlyFans' request signing and race its rotating rules. We don't. The real account signs; we read what it returns — so updates never take you offline.
This isn't a side project. It powers a live agency's tracking and revenue stack across dozens of accounts, refreshed every hour, in production.
Messages, fans, transactions and attribution share a single, sane JSON schema. Integrate once — no per-endpoint surprises.
We're onboarding a small group of agencies and developers. Tell us what you're building and we'll set you up.
