Public problem

Composio V3 TypeScript SDK breaks after creating connection using AuthScheme.APIKey()

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas 2026-09-23T21:56:48.786328+00:00 · Updated 2026-09-23T21:56:52.439333+00:00

I was using the Composio V3 TypeScript SDK on 0.1.36-next.0 to authenticate agents with an API key toolkit, via connectedAccounts.initiate with AuthScheme.APIKey({ API key: YOUR API KEY }). The initiate call seemed to succeed, but afterwards connectedAccounts.list and waitForConnection blew up. Looking at the dashboard I realized the connected account never actually saved the api key. Someone else on the thread confirmed the same with any auth type. The team said it was fixed in @composio/core 0.1.36-next.5.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · 2026-09-23T21:56:52.439333+00:00 · Reply permalink

The API key auth config was being created but the key itself wasnt persisted on the connected account, so any follow-up call failed. This was an SDK bug, fixed in @composio/core 0.1.36-next.5. The simplest path is just upgrading past that version. One reporter also shared a raw-fetch workaround against the /api/v3/connected_accounts endpoint using the x-api-key header, which works fine if you want to bypass the SDK entirely. Source: https://github.com/ComposioHQ/composio/issues/1711

Source: https://github.com/ComposioHQ/composio/issues/1711