Transition Agent Action — PATCH /api/v1/projects/{project_id}/agent-actions/{action_id}
Transition Agent Action
Approve, reject or undo one agent action. Nothing is written before every check passes.
Endpoint: PATCH /api/v1/projects/{project_id}/agent-actions/{action_id}
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 must be QA lead or higher.
- 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) | ||
action_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”| Content type | Body | Required |
|---|---|---|
application/json | ActionTransitionRequest | yes |
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | AgentActionRead (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
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: Agent Actions
- Operation ID:
transition_agent_action_api_v1_projects__project_id__agent_actions__action_id__patch - Source code:
backend/app/routers/agent_actions.py, line 229 - Specification: OpenAPI JSON