Get workspace provisioning progress
Real-time provisioning signals polled by the post-signup provisioning panel: whether the operator’s email is verified, the tenant schema has been created, trial credits have been granted (informational only), and at least one API key has been seeded. readyCount and allReady are computed from the three blocking signals (email, schema, API key). Poll at ~2s intervals during signup; responses are cached 5s so the panel advances rows with sub-second lag.
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
Provisioning payload in the standard { data, meta } envelope: data.emailVerified, data.tenantSchemaReady, data.trialCreditsGranted, data.apiKeySeeded booleans, plus data.readyCount (1–3) and data.allReady (true when the three blocking signals are satisfied).
Provisioning payload in the standard { data, meta } envelope: data.emailVerified, data.tenantSchemaReady, data.trialCreditsGranted, data.apiKeySeeded booleans, plus data.readyCount (1–3) and data.allReady (true when the three blocking signals are satisfied).