GET returns a read-only survey of who has what. POST performs the backfill by calling the same provisioning function used at signup, so encryption and status handling are inherited rather than reimplemented. Agency-owned accounts (the agency itself and the demo account) are exempt rather than listed as unfinished.
Also called: retrofit subaccounts · who's still on the shared account · isolation report
- 1GET surveys active accounts against their Twilio bindings and compares each stored SID to the parent's.
- 2Agency-owned accounts are filtered out as exempt.
- 3POST runs provisionTwilioSubaccount per account needing one.
- 4Existing live accounts keep their current binding status so their texting is not interrupted.
The route explains both why it is an endpoint and why it was needed. Endpoint, not script: 'A subaccount's auth token is encrypted at rest with the app's own key. A standalone maintenance script would either have to reimplement that encryption or write the credential in plaintext.' Needed because 'seedBindings creates one at signup, but only for orgs created after it shipped and deliberately non-fatally — so 7 of 8 orgs had none and silently fell back to the agency account, and org_default had the PARENT sid stored as its own, reporting an isolation it did not have.' The exemption is reasoned too: the demo account 'is part of the CYA entity, sends from an agency number under the agency's real A2P brand, and could not register its own even if we wanted it to.'
- Accounts created before subaccount provisioning shipped silently shared the agency account.
- A maintenance script could not safely handle the encrypted credential.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →