Invite user to dual stream
Invites a user to join a dual/co-stream. Called as inviteDualStream({streamId, userId}). OnlyFans only — Fansly accounts are rejected on /api2/v2/.
Invites a user to join a dual/co-stream. Called as inviteDualStream({streamId, userId}). OnlyFans only — Fansly accounts are rejected on /api2/v2/*.
Guide: The two surfaces
Authorization
apiKey Your CRM panel API key
In: header
Path Parameters
ID of the stream
ID of the user to invite
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.
Response Body
application/json
curl -X POST "https://example.com/api2/v2/streams/string/users/string/invite" \ -H "user-id: 509955039"{ "success": true, "status_code": 0, "data": null, "relogin": true}Add stream helper PUT
Grants a user helper (moderator) permissions on a live stream. Enclosing fn addStreamHelper. OnlyFans only — Fansly accounts are rejected on /api2/v2/.
Get stream viewers 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,…