Update a legal inquiry
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…
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 rejected on /api2/v2/*.
Guide: The two surfaces
Authorization
apiKey Your CRM panel API key
In: header
Path Parameters
ID of the legal inquiry
Update hash/token authorizing the 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.
Request Body
application/json
opaque object (caller 'data'); fields not statically visible
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X POST "https://example.com/api2/v2/legal-inquiry/string/update/string" \ -H "user-id: 509955039" \ -H "Content-Type: application/json" \ -d '{}'{ "success": true, "status_code": 0, "data": null, "relogin": true}Get legal inquiry update GET
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/.
Submit client-side log entry POST
Sends a client log message with optional context data, logger name and level to the server-side logging endpoint. The context is wrapped with an onlyfans.<logger> logger name…