Maintenance Requests
UsePOST /maintenance/requests to create a maintenance process targeted at a specific account.
When To Use It
Use this endpoint when you need account maintenance work such as profile editing. This is the recommended public maintenance entrypoint.Current Supported Step
The current implementation supports one maintenance action:edit_profile
Request Example
Accepted Response
Request Fields
| Field | Type | Required | Notes |
|---|---|---|---|
request_id | string | yes | Caller-generated idempotency key component. |
account_id | string | yes | Target account id. Must resolve to an active account. |
inputs | object | yes | Contains steps and optional metadata. |
callback | object | yes | Callback destination and metadata. |
requested_by | object | yes | Caller identity. |
inputs.steps[]
| Field | Type | Required | Notes |
|---|---|---|---|
action | string | yes | Must currently be edit_profile. |
params | object | yes | At least one supported profile field is required. |
edit_profile.params fields:
display_namebiousernamemutation_kindrandomized
display_name, bio, or username must be present.
Idempotency
Idempotency key:Advanced Compatibility Note
The lower-level capability contract also knows about amaintenance capability. Public docs treat POST /maintenance/requests as the canonical maintenance route.
Failure Modes
| Status code | Meaning |
|---|---|
401 | Missing or invalid bearer token. |
404 | Account not found or inactive. |
422 | Invalid request structure or unsupported step payload. |
500 | Unexpected enqueue failure. |