Update team
PUT /api/v1/teams/:teamId — change a team's settings or members.
Changes the fields you send and keeps the rest. The same rules as Create team are checked against the result, so changing lead_type to managed needs a lead_llm_config_id already set or sent along.
PUT /api/v1/teams/{teamId}Request body
Any of the fields of Create team, at least one. members, when sent, replaces the whole roster; leave it out to keep the current members.
project_id moves the team. An org-scoped key can move it to another project of the organization; a project-scoped key cannot move it out of its own project. A team always belongs to a project, so null is refused with 400.
Response
200 OK — the team, in the shape of Get team. currentVersion goes up by one: every update saves a version.
Errors
| Status | error | When |
|---|---|---|
400 | validation error | An empty body, a field that fails validation, project_id: null, or a rule broken by the resulting team. |
403 | forbidden | The team is in a different project than your project-scoped key, or the update would move it out of it. |
404 | team_not_found | No team with that ID exists in your organization. |
422 | validation_error | An agent or LLM configuration is not in your organization, or the team would have fewer than two agents that can receive work. |
422 | project_not_found | project_id is not a project of your organization. |
Example
curl -X PUT https://api.elizon.ai/api/v1/teams/3f9c... \
-H "X-API-Key: elz_your_key_here" \
-H "Content-Type: application/json" \
-d '{ "add_datetime_to_context": true, "status": "active" }'Teams cannot be deleted through the API; delete one in Studio.