Message volume and delivery by channel
Aggregates the tenant’s messaging traffic over the selected date range into a per-channel breakdown — for each channel (sms, whatsapp, email, rcs, viber, telegram, voice) the total messages sent, delivered and failed plus the resulting delivery rate. Powers the Messages hub per-channel slice and the WhatsApp Analytics KPI cards; pass phone_number_id to scope the counts to a single WhatsApp sending number. Read-only, rate-limited, 60s cached; degrades to an empty channels array (still 200) during a transient database blip so the always-on widget never flashes a 5xx.
Authorizations
Dashboard JWT token from Clerk
Query Parameters
Inclusive start of the reporting window (ISO-8601 date, e.g. 2026-07-01). Defaults to the tenant's standard lookback when omitted; the range may not exceed the platform lookback cap.
Inclusive end of the reporting window (ISO-8601 date). A single-day range (start_date === end_date) is accepted.
Alternative rolling lookback in whole days (bounded by the lookback cap). Mutually exclusive with an explicit start/end range.
x >= 1Optional WhatsApp multi-WABA scope — narrows the breakdown to outbound rows stamped with this sending phone_number_id. Ignored by org-wide callers.