Alberto Schiabel 17a20be892 feat(core): add userApiKey and orgApiKey to ComposioConfig (#4532) ...

This PR:

- adds `userApiKey` and `orgApiKey` to `ComposioConfig` and forwards
them to the underlying `@composio/client`, which sends each one only on
operations whose security scheme requires it and never beside the
project key
- keeps both on `getConfig()` / `createSession()`; env fallbacks
(`COMPOSIO_USER_API_KEY`, `COMPOSIO_ORG_API_KEY`) stay in the client
- adds `user_api_key` / `org_api_key` to the Python `Composio`
constructor for parity
- adds a minor changeset for `@composio/core`
- a project `apiKey` is still required; widening that is out of scope

## Context

Org, consumer and user-scoped endpoints were only reachable from core
through `getClient()` plus hand-placed headers. This lands on `main`
(beta) only because `next` still pins the Stainless client, which has no
user/org credential support. Hackathon feedback (area 8).

2026-09-18 18:28:20 +02:00

13 KiB

Raw Permalink Blame History

View Raw