Keys / Composio

COMPOSIO_API_KEY

The Composio project API key your app runs tools and connects user accounts with. Each key belongs to one project.

Starts with
ak_
Expires
the docs don't say
API
regenerate, with an organization API key; no create

Get it

Create one on dashboard.composio.dev/~/project/settings/api-keys. The steps aren't recorded yet.

Set it

COMPOSIO_API_KEY=ak_...

The Python and TypeScript SDKs read it from this variable when you don't pass a key. Or keep it out of .env with keypin: keypin run -- npm run dev

Replace it

  1. In Project Settings, an organization admin creates a new API key. For a scoped key, give it the same permissions.
  2. Deploy it everywhere that reads COMPOSIO_API_KEY.
  3. Check that tool calls succeed with the new key, then revoke the old one.
  4. Removing a member from the organization revokes the keys they own, so create the new key as a member who will stay.
  5. Don't use the API's regenerate endpoint for this: it stops every key in the project at once.

Set rotate_every on the key in keypin.toml and a rotated date on its vault item, and keypin status shows when it's due.

Sources, checked 2026-11-16