OnlyFans Notifications API
Read a creator's OnlyFans activity feed programmatically — new subscribers, tips, likes, comments and mentions — without driving a headless browser. The ofapis notifications endpoints return the same events the OnlyFans app surfaces, over authenticated HTTP, billed one credit per successful call. There are two access patterns: a lightweight count for badges and polling, and the full feed when you actually need to render or react to events.
What you can do
- List a creator's notifications (paginated), optionally filtered by type.
- Read the unread notifications count for a cheap badge or poll loop.
- List mentions of the creator separately from the main feed.
- Run any of the above globally (first active account) or scoped to a specific linked account for agencies.
Endpoints
GET /api/public/v1/notifications
GET /api/public/v1/notifications/count
GET /api/public/v1/mentions
# account-scoped (agencies)
GET /api/public/v1/accounts/{accountId}/notifications
GET /api/public/v1/accounts/{accountId}/notifications/count
GET /api/public/v1/accounts/{accountId}/mentions
Poll the count, then fetch the feed
curl "https://api.ofapis.com/api/public/v1/notifications/count" \
-H "Authorization: Bearer ofapis_sk_..."
The count call is the one you run on a timer. When the unread number moves, pull the feed:
curl "https://api.ofapis.com/api/public/v1/notifications?type=tip&limit=50" \
-H "Authorization: Bearer ofapis_sk_..."
The feed paginates — walk pages with the cursor the response returns rather than assuming everything fits in one page. Each call, count or feed, is one credit. A poll loop that hits /count every minute burns roughly 1,440 credits a day, so size your interval against your plan: Free gives 250 credits a month, Starter 30,000, Pro 120,000.
Polling vs webhooks
Polling is simple and stateless, but it costs a credit per check and adds latency equal to your interval. For anything that needs to react in near real time — a "new fan" welcome, a tip alert into Slack — signed webhooks push the event to you instead, so you spend credits on actions rather than checks. Many teams use both: webhooks for reactions, the count endpoint as a reconciliation backstop.
When to use it
Reach for notifications when you're building a unified inbox, a welcome automation, or an analytics dashboard that reacts to tips and comments. To act on who's subscribing, join this with the subscribers API; to reply, hand off to the messaging API.
FAQ
Should I poll notifications or use webhooks?
Use the count endpoint for cheap periodic polling and reconciliation, and webhooks for real-time reactions. Webhooks spend credits on actions instead of on checks, so they scale better for alerting.
Can I filter notifications by type?
Yes. Pass a type parameter to the feed endpoint to narrow to tips, subscribers, comments, or likes, instead of paging through the mixed feed.
How are notification calls billed?
One credit per successful call, whether it's the count, the feed, or mentions. Failed calls — expired session or upstream error — are not charged. Watch the count endpoint if you poll on a tight loop, since each check is a credit.
What's the rate limit?
Requests per minute are set by your plan (60 rpm on Free up to 500 rpm on Pro). See pricing for the full breakdown.