List story-blocked users
Returns users blocked from viewing the current user's stories. OnlyFans only — Fansly accounts are rejected on /api2/v2/.
Returns users blocked from viewing the current user's stories. OnlyFans only — Fansly accounts are rejected on /api2/v2/*.
✓ Verified live against a real OnlyFans account (2026-07-30); the data schema below is the real response shape.
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.
Response Body
application/json
curl -X GET "https://example.com/api2/v2/stories/users/blocked" \ -H "user-id: 509955039"{ "success": true, "status_code": 0, "data": []}Delete a story answer DELETE
Deletes a viewer's answer/reply to a story (e.g. story question sticker) identified by answer id. OnlyFans only — Fansly accounts are rejected on /api2/v2/.
Block user from stories POST
Blocks the specified user from viewing the creator's stories. OnlyFans only — Fansly accounts are rejected on /api2/v2/.