Skip to main content
Bavlio does not yet ship a customer-facing outbound webhook system. You cannot register a URL and have Bavlio POST events to it. Until that ships, poll the endpoints below.

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

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 with timestamp.body canonical), 5-minute replay window, retry policy with dead-letter queue, and a verification snippet you can drop into any framework.

← Back to Quickstart