Start Fixer Run — POST /api/v1/projects/{project_id}/fixer/run
Start Fixer Run
Trigger a manual fixer run (project QA_ENGINEER+).
Endpoint: POST /api/v1/projects/{project_id}/fixer/run
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
- Your role in the project must be QA engineer or higher. If you are not a member of the project, your account role counts instead.
- You must be a member of the project. Admins always have access.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
project_id | path | yes | string (uuid) | ||
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
202 | Successful Response | object (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Errors this endpoint returns, read from its source code:
403409, with the message “A fixer run is already in flight for this project”422, with the message “Suggest mode requires a runner (docker or workflow_dispatch). Configure fixer.runner.type before running in suggest mode”503, with the message “The fixer run could not be queued (task broker unavailable). Try again shortly”
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: Fixer
- Operation ID:
start_fixer_run_api_v1_projects__project_id__fixer_run_post - Source code:
backend/app/routers/fixer.py, line 190 - Specification: OpenAPI JSON