Submit a toll-free RespOrg change request
Bring a toll-free number onto the platform (direction: 'in') or release it (direction: 'out') by requesting a Responsible Organization (RespOrg) change via Somos — the SMS/800 analogue of geographic LNP porting (toll-free numbers are never ported carrier-to-carrier). newRespOrgId is required for direction: 'out'. The request is captured and tracked here and fulfilled by operations through Somos out-of-band (no live Somos API integration). Invariant #45 unaffected — inbound toll-free number administration only.
Authorizations
Dashboard JWT token from Clerk
Headers
Stripe-style idempotency token. Pass a stable, client-generated value (1-255 chars) to dedupe retries on transient timeouts. The same key+credential+path replays the original response for 24h on 2xx (5min on 4xx, 30s on 5xx). Returns 409 if a concurrent request with the same key is already in flight; replayed responses include the Idempotency-Replay: true response header.
1 - 255Sandbox 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 Body
in, out North-American toll-free numbers in E.164 (800/833/844/855/866/877/888…).
1 - 50 elements5-character alphanumeric RespOrg code.
5-character alphanumeric RespOrg code. Required when direction is 'out'.
200A Devotel-issued GCS signed URL from POST /files/upload.