Skip to main content

True PATCH Semantics for Auth Config Updates

Version Information

TypeScript/JavaScript

  • Package: @composio/core and provider packages
  • Version: 0.5.1+

Python

  • Package: composio-core and 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

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:

Update Tool Restrictions Without Touching Credentials

Previously, this would fail because credentials was required. Now it works:

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

Raw HTTP API

For users calling the API directly: