Skip to main content

Endpoint

Update the team’s configuration overrides. Uses PATCH semantics - provided values are deep-merged with existing config.

Authentication

Requires Team Token with write permissions.

Request

Headers

Body

Partial configuration object. Only include fields you want to change.

Request Example

Response

Success Response (200)

Approval Required Response (202)

When approval workflows are enabled:

Error Responses

400 Bad Request - Invalid Field
400 Bad Request - Validation Error
403 Forbidden

Immutable Fields

These fields cannot be changed via API:
  • team_name - Set by admin only
  • org_id - Fixed at team creation
  • team_node_id - Fixed at team creation

Common Updates

Add MCP Server

Update Agent Prompt

Enable Additional Tools

Disable Dangerous Tools

Update Slack Settings

Enable Feature Flags

Code Examples

Python

JavaScript

Validation

Before saving, the API validates:
  1. Schema compliance - Fields match expected types
  2. Immutable fields - Cannot change protected fields
  3. Tool existence - Enabled tools must exist
  4. MCP server validity - MCP servers must be configured

Approval Workflows

If your organization has approval workflows enabled:
  1. Updates create a pending change request
  2. Admins are notified
  3. Once approved, config is applied
  4. Requester is notified
Check pending changes:

Next Steps

Get Config

View current configuration

Configuration Guide

Configuration documentation