Event-Driven Notification Platform · View 05 of 26 · 2 · Structure

Integration and Interface Catalogue

Every way something enters or leaves the platform, with protocol, cadence and owner.

Editable source SVG draw.io All views

Producer API surface

POST /v1/events — the main path, asynchronous, returns 202 with an event id
POST /v1/notifications — direct send for callers that already know the decision
GET /v1/notifications/{id} and /delivery-status — lifecycle inspection
Preference, template and admin APIs, all OpenAPI 3.1; the event contract is published as AsyncAPI 3

Provider policy

Two vendors per channel, ranked, with automatic failover — no provider is a platform dependency
Credentials are per tenant and leased from Vault for one hour; nothing is baked into an image
A new provider is a client implementation plus a config row, not a release

Risks

Native Kafka producers bypass the gateway, so schema and quota enforcement move to broker-side ACLs and the registry — weaker than the HTTP path
FCM and APNs have no second vendor; the only fallback for push is degrading to SMS or in-app

◀ Container and Component Architecture All views Channel Abstraction ▶