Documentation Index
Fetch the complete documentation index at: https://docs.bavlio.com/llms.txt
Use this file to discover all available pages before exploring further.
Why “not yet”?
A safe outbound webhook system requires SSRF defense at both registration and dispatch, retry semantics, dead-letter handling, and signing. Shipping it half-built is worse than shipping it later. The full design is parked in the backend roadmap.Use these polling endpoints instead
| Method | Path | Purpose |
|---|---|---|
GET | /api/v1/campaigns/{campaign_id}/stats | Comprehensive campaign stats (sends, opens, clicks, replies). |
GET | /api/v1/campaigns/{campaign_id}/leads/{id}/events | Per-lead email event timeline. |
GET | /api/v1/bavimail/emails | List sent emails with status (delivered, opened, bounced). |
GET | /api/v1/bavimail/inbound-emails | List inbound replies. |
GET | /api/v1/bavimail/conversations | Threaded inbound + outbound view. |
Poll inbound replies
Track which message ids you’ve seen and process new ones. Persist seen ids across restarts in production.Python
Poll campaign completion
Python
Internal webhook receivers (context only)
For visibility: Bavlio operates three inbound webhook receivers — one each for BaviMail, Unipile (LinkedIn), and Stripe. These are server-to-server endpoints between Bavlio and our infrastructure providers, not points you can register against. They are documented internally and surfaced here only so agents understand the data flow.Roadmap
Once the customer webhook system ships, this page will document: registration endpoint, signing scheme (HMAC-SHA256 withtimestamp.body canonical), 5-minute replay window, retry policy with dead-letter queue, and a verification snippet you can drop into any framework.