Sort pinned list users
Reorders the pinned users within a list identified by list_id, per the provided order. OnlyFans only — Fansly accounts are rejected on /api2/v2/.
Reorders the pinned users within a list identified by list_id, per the provided order. 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 list whose pinned users are sorted
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
Payload is {order: t}
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X POST "https://example.com/api2/v2/lists/string/users/pinned/sort" \ -H "user-id: 509955039" \ -H "Content-Type: application/json" \ -d '{}'{ "success": true, "status_code": 0, "data": null, "relogin": true}Add media buyers to list POST
Adds users who purchased a given media item to a list (bulk add by media). OnlyFans only — Fansly accounts are rejected on /api2/v2/.
Add queue buyers to list POST
Adds users who bought from a given queue to a list (bulk add by queue). OnlyFans only — Fansly accounts are rejected on /api2/v2/.