Each webhook request sent by Bridge is signed with an HMAC-SHA256 signature to verify that the request is authentic and has not been tampered with.Documentation Index
Fetch the complete documentation index at: https://docs.bridge.new/llms.txt
Use this file to discover all available pages before exploring further.
Your server should validate this signature before processing the payload.
Signature Overview
Bridge includes three headers for authentication and validation:| Header | Description | Purpose |
|---|---|---|
X-Bridge-API-Key | Your assigned API key | Identifies your workspace |
X-Bridge-Signature | sha256={signature} | HMAC-SHA256 signature of the request body |
X-Bridge-Timestamp | Unix timestamp | Used to prevent replay attacks |
Step-by-Step Verification (Python Example)
Below is an example of how to verify a webhook’s signature in Python.Timestamp Validation
To prevent replay attacks, Bridge includes the headerX-Bridge-Timestamp.
Your system should reject webhook requests older than 5 minutes.
Security Recommendations
- Always verify both the HMAC signature and timestamp.
- Enforce HTTPS for all webhook endpoints.
- Implement rate limiting to protect against abuse.
- Only process events that pass signature verification.
- Never share your client secret publicly or store it in frontend code.