Get queued mass messages
Read native queued mass messages. The upstream body observed live is an array under data in the passthrough envelope, not data.list. This is not an exhaustive historical…
Read native queued mass messages. The upstream body observed live is an array under data in the passthrough envelope, not data.list. This is not an exhaustive historical delivery ledger. An empty queue does not prove that an ambiguous send failed; it may already have been processed. Do not automatically retry a send on that basis. OnlyFans only. See Messaging & mass DM.
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.
Response Body
application/json
curl -X GET "https://example.com/api2/v2/messages/queue" \ -H "user-id: 509955039"[ {}]Mark chat as read POST
OnlyFans only. Requests made with a user-id belonging to a Fansly account are rejected — use the platform-neutral CRM data routes (/notifications, /balances,…
Create a mass message POST
Create a native OnlyFans mass-message queue item. Select the native Fans audience explicitly with userLists: ["fans"]. Do not assume this includes expired subscribers or…