Get cross-channel fallback configuration
Returns the tenant’s cross-channel fallback routing map: for each primary channel (sms, rcs, whatsapp, viber, messenger, instagram, line, telegram, email), the ordered list of fallback channels to try when the primary fails, so an rcs->sms failover chain survives a downstream outage. Empty arrays (or a missing key) mean no fallback is configured for that primary — primary failure surfaces CHANNEL_UNAVAILABLE to the caller. The dashboard’s /settings/channels surface edits this; admin does not touch it (routing policy is the tenant’s call).
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