Skip to main content
Hand each customer a dedicated ingest URL instead of one shared endpoint you demultiplex by hand. Each tenant gets its own endpoint — its own signing secret, its own dedup policy, and its own destination — so verification and routing never cross tenants.
1

One endpoint per tenant

Create an endpoint as you onboard each tenant and hand them its ingest URL. The URL is permanent, so it’s safe to store against the tenant record.
2

Per-tenant secret and dedup

Each tenant’s secret verifies only their traffic; each endpoint’s dedup policy is independent, so a noisy tenant’s window doesn’t affect a quiet one.
3

Route each tenant to the right destination

Subscribe each endpoint to the destination that serves that tenant — a shared receiver that reads the endpoint id, or a per-tenant URL.
Filter and audit per tenant with the endpoint id — wbhk events list <endpoint-id> and wbhk deliveries list --subscription <id> never bleed one tenant’s traffic into another’s view.