Per-day usage timeline
Daily message-volume timeline across channels (SMS, WhatsApp, email, voice, agents) as rendered by the home-overview usage chart. Select the window with ?days= (default 30, max 365) or an explicit start_date / end_date pair — the explicit pair takes precedence. Each row carries date plus one counter key per channel. An always-on read — transient database availability degrades to an empty timeline (200) rather than an error.
Authorizations
Dashboard JWT token from Clerk
Headers
Sandbox opt-in for Clerk-session-authenticated requests. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.
true, false Query Parameters
Trailing window in days (default 30, capped at 365). An explicit start_date / end_date pair takes precedence over days.
1 <= x <= 365Window start date in YYYY-MM-DD. Must be used together with end_date.
Window end date in YYYY-MM-DD. Must be used together with start_date.
Response
Usage timeline in data — one row per day with date plus per-channel counters (e.g. sms, whatsapp, email, voice) — within the standard { data, meta } envelope.
Usage timeline in data — one row per day with date plus per-channel counters (e.g. sms, whatsapp, email, voice) — within the standard { data, meta } envelope.