Put Agent Config — PUT /api/v1/projects/{project_id}/agent-configs/{agent_id}

Put Agent Config

Replace this project’s configuration of one agent (QA_LEAD+).

Endpoint: PUT /api/v1/projects/{project_id}/agent-configs/{agent_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 in the project must be QA lead 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

Name	In	Required	Type	Default	Description
project_id	path	yes	string (uuid)
agent_id	path	yes	string
If-Match	header	no	string or null
X-API-Key	header	no	string or null		API key, as an alternative to the access token (see Authentication).

Request body

Content type	Body	Required
application/json	AgentConfigV1	yes

Responses

Status	Meaning	Body
200	Successful Response	object (application/json)
422	Validation Error	HTTPValidationError (application/json)

Errors this endpoint returns, read from its source code:

• 409, with messages such as “The agent configuration changed after it was loaded. Reload it before saving”, “The agent configuration changed while it was being saved. Reload it before saving again”
• 422

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

• Group: Agent Configs
• Operation ID: put_agent_config_api_v1_projects__project_id__agent_configs__agent_id__put
• Source code: backend/app/routers/agent_configs.py, line 88
• Specification: OpenAPI JSON