The Only API docs
Misc

List content report reasons

Returns the list of available reasons for reporting content or users. OnlyFans only — Fansly accounts are rejected on /api2/v2/.

GET
/api2/v2/reports/reasons

Returns the list of available reasons for reporting content or users. 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

X-API-Key<token>

Your CRM panel API key

In: header

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/reports/reasons" \  -H "user-id: 509955039"
{  "success": true,  "status_code": 0,  "data": [    {      "id": 0,      "name": "string",      "code": "string",      "requiresIssue": true,      "subReasons": [        {}      ],      "involves": [],      "issues": {        "revenge_porn": "string",        "expose": "string",        "impersonation": "string",        "underage": "string",        "tm": "string",        "spam": "string",        "prostitution": "string",        "weapons": "string",        "drugs": "string",        "other": "string"      }    }  ]}