- A warning is logged once per toolkit version when the API reports it as deprecated through the Composio-Deprecated-Toolkits response header, naming the version, sunset date and how to pin a newer version
- Requires @composio/client 2.0.0-rc.18, which passes the credential as the client's auth option and the organization and project as scope instead of default headers behavior changed · inferred, marked in the notes below
- With apiKey set to null and only an organization API key, every request now carries x-org-api-key, including trigger channel authorization and session.mcp.headers, where previously only organization-owner operations did
- Credential and scope headers in defaultHeaders or createSession headers are folded into the SDK's own options instead of being forwarded, and getConfig() reports the folded values behavior changed · inferred, marked in the notes below
- Setting more than one of x-api-key, x-user-api-key and x-org-api-key now throws a ComposioError
- On the client returned by getClient(), apiKey, userApiKey and orgApiKey are read-only and deprecated, and a per-call headers option can no longer name a credential or scope header behavior changed · inferred, marked in the notes belowdeprecated · inferred, marked in the notes below
- The API client no longer reads the environment itself; COMPOSIO_ALLOW_INSECURE_HTTP=1 is still honoured, but COMPOSIO_CUSTOM_HEADERS is no longer applied and defaultHeaders should be passed instead removed · inferred, marked in the notes below
- The deprecated customConnectionData now requires val.access_token for S2S_OAUTH2, as the API does behavior changed · inferred, marked in the notes below
- Requires @composio/client 2.0.0-rc.19, and the SDK forwards API client log lines through a Console-shaped object instead of the removed Logger interface, with logged content and SDK levels unchanged removed · inferred, marked in the notes below
- With rc.19, the client returned by getClient() no longer exposes apiKey, userApiKey, orgApiKey or logger, and its baseURL, maxRetries, timeout and logLevel are read-only
- A node with nullable true in strict tool schemas accepts null through its type or a null branch, and the rewrite is reported as a nullable-converted change
- nullable false is removed from strict tool schemas as an unsupported-keyword-stripped change
- Formats on number and integer schemas are kept in strict tool schemas, since the API does not check them
- Fields with format binary or other non-base64 encodings are described to the model as plain strings
- toStrictJsonSchema folds OpenAPI nullable into the type instead of passing it through, so Anthropic strict tool use no longer rejects the request with a 400 behavior changed · inferred, marked in the notes below
- omitNullToolArguments keeps a null for a property marked nullable true behavior changed · inferred, marked in the notes below
- toStrictJsonSchema strips string format values that OpenAI structured outputs rejects, so a single unsupported format no longer makes every strict request fail with a 400
- String tool parameters are checked as base64 only when contentEncoding is base64, so format binary and other encodings such as base16 no longer reject plain text or hex in the Vercel, LangChain, LlamaIndex and Claude Agent SDK providers
3 changes to check, marked in the notes below
From Composio
Minor Changes
-
e08c84f: Requires
@composio/client2.0.0-rc.18. The SDK now hands the API client its credential as the client'sauthoption and its organization and project asscope, instead of placing them in default headers. TheapiKey,userApiKey,orgApiKey,orgIdandprojectIdoptions, their environment fallbacks and the credentials sent on each request are unchanged, with one exception: withapiKey: nulland only an organization API key (theorgApiKeyoption,COMPOSIO_ORG_API_KEY, or anx-org-api-keydefault header), every request now carriesx-org-api-key, and so do trigger channel authorization andsession.mcp.headers. Before, only the organization-owner operations did, and every other request went out without a credential. behavior changed · inferred deprecated · inferred removed · inferredCredential and scope headers in
defaultHeadersorcreateSession({ headers })keep working, but the SDK folds them into its own options instead of forwarding them: anx-user-api-keyorx-org-api-keyentry becomes the credential every request carries, anx-api-keyentry becomes the project key, andx-org-id/x-project-identries becomeorgId/projectId.getConfig()reports the folded values (for exampleapiKey: nullanduserApiKeyfor anx-user-api-keyentry) and no longer lists those entries underdefaultHeaders. Setting more than one ofx-api-key,x-user-api-keyandx-org-api-keynow throws aComposioError; the API rejected every such request.On the client returned by
getClient(),apiKey,userApiKeyandorgApiKeyare read-only and deprecated (read the keys fromgetConfig(), orauthModeandscopefrom the client), and a per-callheadersoption can no longer name a credential or scope header. The API client no longer reads the environment itself: the SDK still honoursCOMPOSIO_ALLOW_INSECURE_HTTP=1, and no longer appliesCOMPOSIO_CUSTOM_HEADERS; passdefaultHeadersinstead.The deprecated
customConnectionDatanow requiresval.access_tokenforS2S_OAUTH2, as the API does. -
57de614: Requires
@composio/client2.0.0-rc.19. The SDK forwards the API client's log lines through aConsole-shaped object instead of the client's removedLoggerinterface; what is logged, and at which SDK level, is unchanged. With rc.19, the client returned bygetClient()no longer hasapiKey,userApiKey,orgApiKeyorlogger, and itsbaseURL,maxRetries,timeoutandlogLevelare read-only: read the keys fromgetConfig(), and derive a client withwithOptions()to change the others. removed · inferred
Patch Changes
-
9d26fb8: Fold OpenAPI
nullableinto the type in strict tool schemastoStrictJsonSchemano longer passes OpenAPInullablethrough. Anthropic strict tool use rejects it on an object schema with a 400 for the whole request. A node withnullable: truenow acceptsnullthrough itstype(["object", "null"]) or a null branch, matching how the tool's arguments are validated, and the rewrite is reported as anullable-convertedchange.nullable: falseis removed as anunsupported-keyword-strippedchange.omitNullToolArgumentsnow keeps anullfor a property markednullable: true, as it already does for one whosetypeincludesnull. behavior changed · inferred -
3dd9a2c: Strip string
formatvalues that OpenAI structured outputs rejects from strict tool schemastoStrictJsonSchemanow removes aformaton a string schema unless it is one ofdate-time,time,date,duration,email,hostname,ipv4,ipv6, oruuid. OpenAI rejects any other string format in strict mode with a 400 for the whole request, so a single tool withformat: "uri", a custom format such asrepo.nwo, or theformat: "path"that file uploads add made every strict request fail. The removal is reported as anunsupported-keyword-strippedchange. Formats on number and integer schemas are kept, since the API does not check them. -
04fdb41: Check a string tool parameter as base64 only when its
contentEncodingisbase64.format: "binary"(raw octets in OpenAPI) and other encodings such asbase16were validated as base64, so the Vercel, LangChain, LlamaIndex, and Claude Agent SDK providers rejected tool calls with plain text or hex in those fields, and the schema sent to the model described them ascontentEncoding: "base64". Those fields are now plain strings.contentEncoding: "base64"keeps its check, andformat: "byte"stays unchecked. -
be12ce1: Warn once per toolkit version when the API reports it as deprecated through the
Composio-Deprecated-Toolkitsresponse header. The warning names the version, the sunset date and how to pin a newer version. Silence it withlogLevel: 'error'orCOMPOSIO_LOG_LEVEL=error. -
Updated dependencies [f119f05]
-
Updated dependencies [04fdb41]
- @composio/json-schema-to-zod@0.4.0