Guides
Subscriber Portal
Let each subscriber manage their own Endpoint, auth, and Subscriptions directly — without an account, a password, or any access to your dashboard or other subscribers' data.
No subscriber accounts — passes instead
There's no signup flow for subscribers. Access is a short-lived pass your own backend mints on demand, using the same API key you already use to publish events.
Your backend mints a pass (~60s)
→
subscriber opens the portal link
→
pass exchanged for a session (~1h)
→
scoped to that one Application
What subscribers can do
Endpoints, auth & signing secret
Create, edit, and delete their own Endpoint; configure inbound auth (API key or Basic Auth) on it; view, rotate, and sunset their own signing secret — the same reachability/SSRF checks your dashboard uses, just re-scoped to their Application.
Subscriptions from a read-only catalog
Pick which Event Types they receive — including a wildcard "all events" option — from a read-only view of your Event Type catalog. They can't create Event Types, filters, or transforms; those stay under your control.
Delivery logs, retry & test events
See their own delivery attempts and timelines, retry an exhausted delivery themselves, and send a test event to verify their endpoint is wired up correctly — before going live.
Session state is intentionally not persisted. The bearer session lives in memory only —
no cookie, no localStorage. A full page refresh loses it; the subscriber re-arrives via a
fresh link from you. This avoids third-party-cookie blocks when the portal is embedded in an iframe.
Embedding is opt-in per Application — you control which of your own domains are allowed to
iframe the portal. Anything not explicitly listed is denied by default.