@devries-cameron20 / composio Mirror · read-only / commits / 5279fa225
Fork 0

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, 11:00 UTC

docs: changelog for scoped API keys tools read fix (#4557)

## Summary - Adds a changelog entry documenting the fix where tools read operations (fetch/list) were incorrectly gated behind the write API key scope instead of read. ## Context Palash requested this changelog entry to document the scoped API keys bug fix shipped today. ## Test plan - [ ] Verify the changelog renders correctly on the docs site --------- Co-authored-by: Palash Kala [zen] <palash@composio.dev> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

composio-zen[bot] committed Sep 24, 2026 at 13:40 UTC 5279fa2256c3a41c6aa2de67b5f819808cf6ab7f
1 file changed +15
docs/content/changelog/09-21-26-scoped-api-keys-tools-read.mdx new
+15
@@ -0,0 +1,15 @@
1 +---
2 +title: "Scoped API Keys: Tools Read Now Accepts Read-Scoped Keys"
3 +description: "Fixed a bug where reading multiple toolkits required a write-scoped API key instead of a read-scoped one"
4 +date: "2026-09-21"
5 +---
6 +
7 +When creating a scoped API key through the API key creation flow, you can assign either read or write scope. Reading multiple toolkits at once was incorrectly requiring a write-scoped API key. This has been fixed to accept read-scoped keys as intended.
8 +
9 +### Bug Fixes
10 +
11 +- Fetching and listing tools across multiple toolkits previously required a write-scoped API key. The scope check was corrected so that read-scoped API keys are now accepted for these read operations.
12 +
13 +### Backward Compatibility
14 +
15 +This is a backward-compatible fix. Existing API keys with write scope continue to work exactly as before. Read-scoped keys can now be used for tools read operations without needing to upgrade to write scope.