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.
Bridge Webhooks Overview
Bridge uses webhooks to notify your system when key events occur in your workspace.Each webhook contains authentication headers and a structured JSON payload sent via HTTPS
POST.
How Webhooks Work
- An event occurs in Bridge (for example, a contact is updated or a conversation summary is created).
- Bridge sends an HTTP
POSTrequest to your configured webhook endpoint. - Your server verifies the request signature and timestamp to confirm authenticity.
- Your endpoint responds with a
2xxHTTP status code to acknowledge receipt.
HTTP Method
- Method:
POST - Content-Type:
application/json
Authentication Headers
Every webhook request sent from Bridge includes authentication headers to ensure secure delivery.| Header | Description | Purpose |
|---|---|---|
X-Bridge-API-Key | Your custom API key | Basic client authentication |
X-Bridge-Signature | HMAC-SHA256 signature of the request body | Validates integrity and authenticity |
X-Bridge-Timestamp | Unix timestamp of the request | Protects against replay attacks |
Example Webhook Request
HTTP Request
JSON Payload
Best Practices
- Always validate the HMAC signature before processing the payload.
- Reject requests where the timestamp (
X-Bridge-Timestamp) is older than 5 minutes. - Use HTTPS for all webhook endpoints.
- Return a
2xxresponse within 30 seconds to confirm successful delivery.