Register PWA push token
Registers or updates the web-push (PWA) push notification token for the current user. OnlyFans only — Fansly accounts are rejected on /api2/v2/.
Registers or updates the web-push (PWA) push notification token for the current user. OnlyFans only — Fansly accounts are rejected on /api2/v2/*.
Guide: The two surfaces
Authorization
apiKey Your CRM panel API key
In: header
Header Parameters
Creator account ID of the account to act as (e.g. 509955039). Required — omitting it returns 400 user-id header is required. Use GET /accounts to list your connected accounts. On /api2/v2/* the account must be an OnlyFans account; Fansly accounts are rejected there.
Proxy URL — HTTP or SOCKS5 (e.g. http://user:pass@host:port or socks5://user:pass@host:port). Optional on post-connection routes, where it overrides the proxy saved at login time. Required on the connection routes (POST /accounts/login, POST /accounts/login/cookies, POST /accounts/login/verify-otp) for OnlyFans accounts; optional for Fansly.
Request Body
application/json
opaque object; push subscription/token payload
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X PUT "https://example.com/api2/v2/users/push-token/pwa" \ -H "user-id: 509955039" \ -H "Content-Type: application/json" \ -d '{}'{ "success": true, "status_code": 0, "data": null, "relogin": true}Mark notification as read POST
Marks a single notification as read by its id. OnlyFans only — Fansly accounts are rejected on /api2/v2/.
Get notifications 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,…