Get the SMS getting-started checklist
Channel-scoped fast-path for the SMS surface’s 5-item getting-started panel: whether the org has an active API key, a purchased number, an approved SMS sender ID, a sent SMS message, and an active webhook endpoint. Collapses six dashboard queries into one round-trip; results are cached 30s. Use it to render the SMS onboarding progress header (completedCount of 5) without hitting six endpoints.
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
SMS checklist payload in the standard { data, meta } envelope: data.hasApiKey, data.hasNumber, data.hasSenderId, data.hasSentMessage, data.hasWebhook booleans plus data.completedCount (count of true booleans).
SMS checklist payload in the standard { data, meta } envelope: data.hasApiKey, data.hasNumber, data.hasSenderId, data.hasSentMessage, data.hasWebhook booleans plus data.completedCount (count of true booleans).