Get legal inquiry update
Retrieves a specific update of a legal inquiry identified by inquiry_id, addressed by an update hash. OnlyFans only — Fansly accounts are rejected on /api2/v2/.
Retrieves a specific update of a legal inquiry identified by inquiry_id, addressed by an update hash. 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 legal inquiry
Hash identifying the specific inquiry update
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/legal-inquiry/string/update/string" \ -H "user-id: 509955039"{ "success": true, "status_code": 0, "data": null, "relogin": true}Get legal inquiry history GET
Returns the history/audit trail for a legal inquiry by id (from the legal/law module). OnlyFans only — Fansly accounts are rejected on /api2/v2/.
Update a legal inquiry POST
Submits an update to a legal inquiry identified by its ID and hash. Part of the legal-inquiry module (search, history, change-status). OnlyFans only — Fansly accounts are…