Webhook Delivery
Configure per-App webhook URLs and understand dual delivery for BYON messages.
BYON Apps support dual delivery — messages are delivered to both your webhook URL and any connected WebSocket clients in parallel. This ensures maximum reliability.
Configuring a webhook
In your App's settings, set a Webhook URL — an HTTPS endpoint that Pipes.bot will POST messages to.
https://your-app.example.com/webhook/pipesMessages from any sender on any of your App's BYON numbers will be delivered to this URL.
Delivery behavior
When a message arrives on a BYON number:
- Webhook: Pipes.bot sends an HTTP POST to your App's webhook URL
- WebSocket: Simultaneously delivered to any connected WebSocket clients authenticated with your
ak_key
Both deliveries happen in parallel. If one fails, the other still succeeds.
| Delivery method | Reliability | Latency | Best for |
|---|---|---|---|
| Webhook | High (with retries) | Slightly higher | Stateless services, automation platforms |
| WebSocket | Real-time | Lowest | AI agents, interactive apps |
Retry policy
Failed webhook deliveries are retried with exponential backoff:
| Attempt | Delay |
|---|---|
| 1st retry | 10 seconds |
| 2nd retry | 60 seconds |
| 3rd retry | 5 minutes |
After 3 failed attempts, the delivery is marked as failed. You can view delivery logs in the App's dashboard.
Testing your webhook
Use the Test Webhook button in your App's settings to send a sample payload to your configured URL. This helps verify your endpoint is reachable and processing messages correctly before going live.
Webhook payload
BYON webhook payloads follow the same format as pool number webhooks. See the Webhooks documentation for full payload details, signature verification, and error handling.
Next steps
- Webhooks — Full webhook payload reference
- Number Management — Monitor your BYON numbers