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(webhook-verification): drop redundant "two signatures" callout
Once the Ingress signature verification section moved off this page, the top callout's only job was to tell readers that ingress is covered elsewhere — useful only when there was an in-page contrast to make. Now that the page covers delivery exclusively (and the title + opening sentence say so), the callout is just overhead. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Anshu Garg committed
May 7, 2026 at 20:55 UTC
03618512d17a829e19ac74e58bf1f6cd607c716c
1 file changed
-4
docs/content/docs/webhook-verification.mdx
-4
@@ -6,10 +6,6 @@ keywords: [webhook, verification, signature, HMAC, security]
6
7
Composio signs every webhook request. Always verify signatures in production to ensure payloads are authentic.
8
9
-<Callout>
10
-**Two signatures, two responsibilities.** Composio verifies provider signatures on the **ingress** hop automatically. You verify Composio's signature on the **delivery** hop — this page covers that.
11
-</Callout>
12
-
9
## SDK verification
10
11
The SDK handles signature verification, payload parsing, and version detection (V1, V2, V3).