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, 23:30 UTC
docs(changelog): note that signing secrets foreclose endpoint sharing
Add a short paired sentence to the project-scoping section: just as one OAuth app can't fan out to multiple projects on V2, two OAuth apps can't share a single V2 endpoint either, because the signing secret lives on the endpoint and only one app's signatures would verify. Closes a likely "can I work around this?" question without adding a new bullet. _(sent via Claude Code)_ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Anshu Garg committed
Apr 18, 2026 at 21:55 UTC
aa21559176bf62817fca58e05791c6e7f629420e
1 file changed
+2
docs/content/changelog/04-18-26-webhook-triggers-v2.mdx
+2
@@ -134,6 +134,8 @@ curl -X POST "https://backend.composio.dev/api/v3/trigger_instances/SLACK_CHANNE
134
135
The provider dashboard accepts only one callback URL per OAuth app, and each V2 URL resolves to exactly one project — so a single OAuth app cannot feed multiple projects on V2.
136
137
+The signing secret also lives on the endpoint, so the reverse holds too: two different OAuth apps cannot share one V2 endpoint — Composio would only verify signatures from the app whose secret is on file.
138
+
139
Project-scoped endpoints give each project:
140
141
- A dedicated ingress rate-limit and backpressure budget