Number Lifecycle
Once you own a number, Orbit gives you full lifecycle control: keep it billing automatically, schedule a future teardown, hand it to a sibling subaccount, recover from a failed carrier release, or reclaim a parked number during its grace window. All lifecycle mutations are gated by org ownership — a sibling subaccount sharing your tenant schema cannot touch a number it doesn’t own.Auto-Renew
Toggle automatic recurring renewal so a held number is re-billed each cycle instead of lapsing atnext_billing_at.
Scheduled Release
Pre-plan a teardown (seasonal campaign DIDs, trial overflow, contract end-of-term) without remembering to release on the day. A separate sweeper drives the existing release path when the date arrives.release_at is an ISO-8601 future timestamp. Sending release_at: null on the PATCH /:id/scheduled-release variant also clears the schedule.
Reassign to a Subaccount
Move a purchased number from your subaccount to a sibling subaccount under the same reseller parent — the DID parity to wallet transfer-to-subaccount.purchased state. Cross-tenant or unowned moves are rejected.
Retry a Failed Release
When a carrierDELETE fails (release_status = "failed" or stuck pending), re-issue it without re-purchasing.
Reclaim a Parked Number
Re-claim a parked number during its grace window without re-purchasing from upstream. Returns409 when the number isn’t reclaimable (not parked, wrong org, or window expired) — fall back to a fresh purchase in those cases.
Repair Provisioning
Re-attach the messaging profile and voice connection on a number whose original purchase left them partial.Attach a Compliance Profile
For a number that landed atpending_compliance, attach an approved compliance profile. Orbit re-submits the profile to the carrier and patches the pending order; a carrier webhook later flips the row to active.