Skip to content

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs(changelog): note that signing secrets foreclose endpoint sharing

Anshu Gargaa21559176bf
diff --git a/docs/content/changelog/04-18-26-webhook-triggers-v2.mdx b/docs/content/changelog/04-18-26-webhook-triggers-v2.mdx
index 0c6a45a94..53a45f622 100644
--- a/docs/content/changelog/04-18-26-webhook-triggers-v2.mdx
+++ b/docs/content/changelog/04-18-26-webhook-triggers-v2.mdx
@@ -134,6 +134,8 @@ curl -X POST "https://backend.composio.dev/api/v3/trigger_instances/SLACK_CHANNE
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.
+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.
+
Project-scoped endpoints give each project:
- A dedicated ingress rate-limit and backpressure budget