Preview native message recipients

Read-only native composer recipient preview. For the unexcluded Fans audience use filter[list_id]=fans, total=1, offset=0, limit=1, skip_users=all, field=recent and sort=desc.…

Read-only native composer recipient preview. For the unexcluded Fans audience use filter[list_id]=fans, total=1, offset=0, limit=1, skip_users=all, field=recent and sort=desc. Check success then data.total. limit controls the returned sample, not the total or a subsequent send. Does not validate media, reserve recipients or guarantee delivery; counts can change. Other inclusion/exclusion combinations require a matching preview. Verified with authenticated account reads on 27 October 2026; no mass message sent. See Messaging & mass DM. OnlyFans only.

Authorization

apiKey

X-API-Key<token>

Your CRM panel API key

In: header

Query Parameters

filter[list_id]?string

Default"fans"

total?integer

Default1

limit?integer

Default1

offset?integer

Default0

skip_users?string

Default"all"

field?string

Default"recent"

sort?string

Default"desc"

Header Parameters

user-id*string

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.

X-Proxy?string

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/chats/users?filter%5Blist_id%5D=fans&total=1&limit=1&offset=0&skip_users=all&field=recent&sort=desc" \  -H "user-id: 509955039"

{  "total": 0,  "list": [    {}  ],  "hasMore": true,  "nextOffset": 0}