Jan 14, 2026
Latest updates and announcements
True PATCH Semantics for Auth Config Updates
Version Information
TypeScript/JavaScript
- Package:
@composio/coreand provider packages - Version:
0.5.1+
Python
- Package:
composio-coreand provider packages - Version:
0.10.7+
The PATCH /api/v3/auth_configs/{id} endpoint now implements proper partial update semantics. Previously, omitting fields would clear them (behaving like PUT). Now, omitted fields are preserved—only explicitly provided fields are modified.
Breaking Change: If you relied on omitting fields to clear them, you must now explicitly send null or []. See Migration Guide below.
What Changed
| Field | Before (Buggy) | After (Correct) |
|---|---|---|
credentials | Required on every update | Optional—merged with existing |
tool_access_config | Reset to {} if omitted | Preserved if omitted |
scopes (type: default) | Cleared if omitted | Preserved if omitted |
restrict_to_following_tools | Reset to [] if omitted | Preserved if omitted |
Merge Behavior: The credentials object is merged—send only the fields you want to change, and existing fields are preserved.
New Capabilities
Rotate a Single Credential Field
Update just client_secret without resending client_id or other fields:
from composio import Composio
composio = Composio()
# Only send the field you want to update - other credentials are preserved
composio.auth_configs.update(
"ac_yourAuthConfigId",
options={
"type": "custom",
"credentials": {
"client_secret": "new_rotated_secret",
},
},
)import { Composio } from "@composio/core";
const composio = new Composio();
// Only send the field you want to update - other credentials are preserved
await composio.authConfigs.update("ac_yourAuthConfigId", {
type: "custom",
credentials: {
client_secret: "new_rotated_secret",
},
});Update Tool Restrictions Without Touching Credentials
Previously, this would fail because credentials was required. Now it works:
from composio import Composio
composio = Composio()
# Update tool restrictions - credentials are automatically preserved
composio.auth_configs.update(
"ac_yourAuthConfigId",
options={
"type": "custom",
"tool_access_config": {
"tools_available_for_execution": ["GMAIL_SEND_EMAIL", "GMAIL_READ_EMAIL"],
},
},
)import { Composio } from "@composio/core";
const composio = new Composio();
// Note: TypeScript SDK currently requires credentials for custom type updates
await composio.authConfigs.update("ac_yourAuthConfigId", {
type: "custom",
credentials: {
// Include existing credentials when using TS SDK
},
toolAccessConfig: {
toolsAvailableForExecution: ["GMAIL_SEND_EMAIL", "GMAIL_READ_EMAIL"],
},
});Migration Guide
Am I Affected?
Yes, if your code relied on omitting fields to clear them.
No, if you always send complete payloads or only use PATCH to update specific fields.
How to Clear Fields Explicitly
| To Clear | Python SDK | TypeScript SDK |
|---|---|---|
tool_access_config | "tool_access_config": {"tools_available_for_execution": []} | toolAccessConfig: { toolsAvailableForExecution: [] } |
scopes (default) | "scopes": "" | scopes: "" (via HTTP API) |
from composio import Composio
composio = Composio()
# Explicitly clear tool restrictions with empty array
composio.auth_configs.update(
"ac_yourAuthConfigId",
options={
"type": "custom",
"tool_access_config": {
"tools_available_for_execution": [],
},
},
)import { Composio } from "@composio/core";
const composio = new Composio();
// Explicitly clear tool restrictions with empty array
await composio.authConfigs.update("ac_yourAuthConfigId", {
type: "custom",
credentials: {
// Include existing credentials when using TS SDK
},
toolAccessConfig: {
toolsAvailableForExecution: [],
},
});Raw HTTP API
For users calling the API directly:
# Rotate single credential
curl -X PATCH "https://backend.composio.dev/api/v3/auth_configs/{id}" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"type": "custom", "credentials": {"client_secret": "new_secret"}}'
# Clear tool restrictions
curl -X PATCH "https://backend.composio.dev/api/v3/auth_configs/{id}" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"type": "custom", "tool_access_config": {"tools_available_for_execution": []}}'