What counts as a credit?

One successful API call. If a request fails — expired session, upstream error — it isn't charged. Mass DMs are the exception: a mailing bills one credit per recipient, and you can preview the exact cost before sending.

How do I authenticate?

A Bearer token: Authorization: Bearer ofapis_sk_…. Create and revoke keys in the dashboard.

Can I manage multiple creators?

Yes. Link several accounts and address each by id under scoped routes. Account count scales with your plan.

Do you have an OpenAPI spec?

A complete OpenAPI 3.0 document and a live Swagger playground — point your generator at it for a typed client.

OnlyFans Tips API

Tips are read-only signal: fans tip creators, and the onlyfans tips api lets you pull those events back out and attribute each one to the fan who sent it. ofapis surfaces tips two ways — as a flag on individual messages and as typed events in the notifications feed — both over a single Bearer-authed call. There is no route to send a tip; the API reads what fans have already given.

Two ways to read tips

On messages — every message carries isTip; when true, price is the tip amount in cents and fromUser is the fan who tipped.
In notifications — the activity feed emits tip events; filter it with ?type=tips.

Endpoints

GET /api/public/v1/notifications?type=tips&limit=
GET /api/public/v1/chats/{chatId}/messages?limit=
# account-scoped (agencies)
GET /api/public/v1/accounts/{accountId}/notifications
GET /api/public/v1/accounts/{accountId}/chats/{chatId}/messages

Example

curl "https://api.ofapis.com/api/public/v1/notifications?type=tips&limit=50" \
  -H "Authorization: Bearer ofapis_sk_..."

The notifications payload is forwarded from OnlyFans as-is, newest first. Page through with the returned cursor to walk a longer history.

Attributing tips to fans

For a per-fan tip total, read a conversation's messages and keep the ones where isTip is true. Each carries fromUser.id (who tipped), price (how much, in cents — divide by 100 for dollars), and createdAt (when). Group by fromUser.id and sum. The notifications feed is the faster path to a chronological "who just tipped" stream; the message read is the path to a precise per-conversation ledger.

Use cases

Auto thank-you. Watch the tips feed and fire a personalized DM to fromUser right after a tip lands, using the messaging API.
Top-tipper leaderboard. Roll tips up per fan into a CRM to spotlight whales and tailor outreach.
Real-time alerts. Subscribe to webhooks so a tip pings Slack or Telegram the moment it happens instead of polling.

Gotchas

Read-only. The API reports tips; it can't send them. Tipping is a fan action.
Amounts are gross. price is the tip's face value in cents, before OnlyFans' platform fee — it isn't your net payout.
Billing. One successful call is one credit, whether a notifications page or a message page. Failed calls (expired session, upstream error) are free.
Pagination. The feed and message lists page with limit and a cursor (nextOffset / nextMessageId). A high-volume account is many credits, so store what you've read and pull deltas. Pace the loop to your plan's rate limits.

FAQ

Can I send a tip through the API?

No. Tips flow from fan to creator; the API only reads tips that have already been received. There is no send-tip endpoint.

How do I know which fan sent a tip?

Tip messages and tip notifications both carry the sending user. On a message, check isTip is true and read fromUser; key your per-fan totals on fromUser.id.

Is the tip amount my net earnings?

No — price is the gross tip amount in cents before OnlyFans' platform fee. Convert to dollars by dividing by 100, but don't treat it as your payout.

Does reading tips cost credits?

Yes, one credit per successful call. Whether you read the tips notification feed or a conversation's messages, only successful calls are billed.

Get a free token · Notifications API · API reference