Cross-channel deliverability and sender-reputation cockpit
One composite deliverability/reputation score (0-100 with an excellent/good/fair/poor/critical tier) rolled up from per-channel cards: SMS route quality, email domain and IP authentication, WhatsApp quality rating, RCS sender status, and voice call quality — each card independently fail-safe (a channel outage degrades that one card to an ‘error’ status instead of blanking the cockpit). Below the healthy bar a per-channel issue joins the worst-first issues remediation list with its root cause and what to do about it. Optional query days (1-90, default 7) sizes the SMS route-quality slice. Read-only; owner/admin/developer/viewer; 60s cached.
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 Response
Successful response.