Notifications
Notifications
OnlyFans notification endpoints (via proxy). **OnlyFans only** — Fansly accounts are rejected on this surface.
OnlyFans notification endpoints (via proxy). OnlyFans only — Fansly accounts are rejected on this surface.
| Method | Endpoint | Path |
|---|---|---|
GET | Get user alerts | /api2/v2/users/alert |
DELETE | Delete user alert | /api2/v2/users/alert/{alert_id} |
DELETE | Dismiss a mass alert | /api2/v2/users/mass-alert/{alert_id} |
GET | Get notifications | /api2/v2/users/notifications |
POST | Mark notification as read | /api2/v2/users/notifications/{notification_id}/read |
GET | Get unread notification count | /api2/v2/users/notifications/count |
POST | Mark all notifications as read | /api2/v2/users/notifications/read |
GET | Get notification tabs order | /api2/v2/users/notifications/settings/tabs-order |
POST | Save notification tabs order | /api2/v2/users/notifications/settings/tabs-order |
PUT | Register PWA push token | /api2/v2/users/push-token/pwa |
Get referral earnings balance GET
OnlyFans only. Requests made with a user-id belonging to a Fansly account are rejected — use the platform-neutral CRM data routes (/notifications, /balances,…
Get user alerts GET
Returns the current user's alert(s) banner data. OnlyFans only — Fansly accounts are rejected on /api2/v2/.