Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 03:37 UTC
| 1 | --- |
| 2 | title: 'Python SDK 0.23.0 and TypeScript SDK 0.20.0 add a faster API client' |
| 3 | description: 'Both SDKs now use a faster handrolled client, expose more v3.1 APIs, and tighten authentication and session updates.' |
| 4 | date: '2026-09-22' |
| 5 | --- |
| 6 | |
| 7 | Python SDK `0.23.0` and TypeScript SDK `0.20.0` replace the old autogenerated client with a new handrolled one. Its lightweight HTTP transport is substantially faster while preserving the SDK APIs you already use. The client also covers more of Composio's v3.1 API. |
| 8 | |
| 9 | ### Release versions |
| 10 | |
| 11 | | SDK | Version | |
| 12 | | --------------------------- | -------- | |
| 13 | | Python `composio` | `0.23.0` | |
| 14 | | TypeScript `@composio/core` | `0.20.0` | |
| 15 | | TypeScript `@composio/slim` | `0.20.0` | |
| 16 | |
| 17 | ### Faster API requests |
| 18 | |
| 19 | The new client reduces request overhead without changing existing imports, types, retries, timeouts, error classes, raw responses, streaming responses, or `AbortSignal` support. TypeScript users also get configurable SDK logging through `logger` and `logLevel`; Python routes client deprecations through `ComposioDeprecationWarning`. |
| 20 | |
| 21 | ### More of the Composio API |
| 22 | |
| 23 | - Project webhooks (`webhooks.subscriptions` and `webhooks.endpoints`), tool execution logs, customer-managed keyring transfer keys, experimental usage metering, and experimental project-owned custom toolkits. |
| 24 | - Connected account revocation and deferred OAuth completion. |
| 25 | - Toolkit bulk retrieval, changelogs, OAuth scope recommendations, and grant contexts. Toolkit auth details now include each field's end-user visibility and the scopes an auth method always requests. |
| 26 | - Tool Router session configuration history through `session.listConfigHistory()` in TypeScript and `session.list_config_history()` in Python. |
| 27 | - `userApiKey` and `orgApiKey` in TypeScript, and `user_api_key` and `org_api_key` in Python, for user- and organization-scoped operations. |
| 28 | |
| 29 | ### Safer authentication and session updates |
| 30 | |
| 31 | You can now authenticate without a project key by setting `apiKey: null` in TypeScript or `disable_api_key=True` in Python, then supplying a user or organization API key. Consumer requests can be scoped with `orgId` and `projectId` in TypeScript or `org_id` and `project_id` in Python. |
| 32 | |
| 33 | Session MCP configuration exports only the credential and project scope used for the session request, and only when the MCP URL has the same origin as the configured Composio API. `session.update()` now uses the session's last observed config version by default. Concurrent writes raise a typed conflict instead of silently overwriting a newer configuration, and nullable policy fields can remove stored overrides. |
| 34 | |
| 35 | <Callout type="warn"> |
| 36 | **Migration note** |
| 37 | |
| 38 | In TypeScript, `apiKey: null` now explicitly disables project-key fallbacks. If you want the SDK |
| 39 | to fall back to `COMPOSIO_API_KEY` or the CLI config when an environment variable is missing, pass |
| 40 | `undefined` or omit `apiKey` instead: |
| 41 | |
| 42 | ```typescript |
| 43 | import { Composio } from '@composio/core'; |
| 44 | |
| 45 | const composio = new Composio({ |
| 46 | apiKey: process.env.COMPOSIO_API_KEY, |
| 47 | }); |
| 48 | ``` |
| 49 | |
| 50 | Session updates now reject stale writes with `ComposioSessionConfigConflictError` in TypeScript |
| 51 | or `SessionConfigConflictError` in Python. Re-fetch the session and retry, or pass |
| 52 | `expectedConfigVersion: false` (`expected_config_version=False` in Python) when you explicitly |
| 53 | need last-writer-wins behavior. |
| 54 | </Callout> |
| 55 | |
| 56 | <Callout> |
| 57 | `connectedAccounts.refresh()` is deprecated because the API deprecated its endpoint. The API also |
| 58 | removed credential validation from refresh, so TypeScript now ignores `validateCredentials` and |
| 59 | logs a warning when you set it. |
| 60 | </Callout> |