Consumer Messaging Platform — WhatsApp-Class System  ·  View 19 of 23

Integration and Interface Catalogue

Every way the platform touches another system, with the protocol and cadence on each interface and the direction of the call.

Editable source SVG draw.io All views
Inbound consumers
Inbound consumers
Mobile Client
iOS / Android
Mobile Client...
Desktop & Web Client
Desktop & Web Client
Business Platform Partner
Business Platform Partner
Trust & Safety Console
Trust & Safety Console
Operations Tooling
Operations Tooling
Platform
Platform
Consumer Messaging Platform
23 services, 2 active regions
Consumer Messaging Platform...
Outbound dependencies
Outbound dependencies
Apple APNs
Apple APNs
Google FCM
Google FCM
SMS & Voice OTP
SMS & Voice OTP
Global CDN
Global CDN
STUN / TURN Fleet
STUN / TURN Fleet
Cloud Backup Providers
Cloud Backup Providers
Device Attestation
Device Attestation
Abuse Intelligence Feeds
Abuse Intelligence Feeds
Noise / TCP 443
Noise / TCP 443
Noise / WSS
Noise / WSS
REST + webhook
REST + webhook
mTLS, internal
mTLS, internal
gRPC, audited
gRPC, audited
HTTP/2 push
HTTP/2 push
HTTP v1 push
HTTP v1 push
REST, per signup
REST, per signup
origin pull
origin pull
UDP relay
UDP relay
OAuth upload
OAuth upload
REST, per device
REST, per device
hourly batch
hourly batch
Integration and Interface Catalogue
Integration and Interface Catalogue
Application we own
Application we own
External / third party
External / third party
synchronous
synchronous
event / async
event / async
batch
batch
Every inbound interface terminates at the edge; no dependency reaches the data tier directly.
Every inbound interface terminates at the edge; no dependency reaches the data tier directly.
v 1.0 · owner Platform Architecture · date 2026-08
v 1.0 · owner Platform Architecture · date 2026-08Text is not SVG - cannot display

Inbound

  • Clients hold one persistent authenticated socket, not a REST session
  • Business partners use a separate REST plus webhook surface with its own quotas
  • Internal consoles reach the platform over mTLS only, with break-glass access audited

Outbound

  • Push, OTP and attestation are the three dependencies on the registration and delivery critical path
  • CDN, TURN and cloud backup are on feature paths and degrade gracefully
  • Every outbound dependency has a defined behaviour when it is unavailable

Boundary rule

  • All inbound traffic terminates at the edge tier
  • No external system reaches a core service or a data store directly
  • Outbound credentials are per-integration and rotated from the KMS
Solution Architecture v1.0 · Platform Architecture · 2026-0819-integration-architecture