Skip to main content
Plivo splits number management across PhoneNumber (search the carrier catalog and buy) and Number (manage numbers you own); Vobiz folds both into a single phone_numbers resource backed by an inventory model - you buy by E.164 from Vobiz’s pre-provisioned stock. A 15-day DID cool-off applies on sub-account moves.

Plivo → Vobiz mapping

Before / after: buy a number

Plivo POSTs to the specific {number} path and can attach a Plivo Application at buy time. Vobiz POSTs the E.164 (with the leading +) to a single purchase-from-inventory endpoint, which debits setup_fee + monthly_fee from your balance (for an SA_ sub-account, the parent MA_ is charged). After purchase the number is owned - assign it to a trunk to take inbound calls.
Plivo
Vobiz

Key differences & gotchas

  • E.164 formatting varies by endpoint. purchase_from_inventory takes the number with the leading + in the body; unrent_number takes it without the + in the path; trunk/sub-account assignment endpoints take it URL-encoded (%2B14155551234).
  • Routing is by trunk. Vobiz routes inbound by an explicit assign/unassign to a trunk_group_id (a UUID); assign a freshly purchased number to a trunk to route it.
  • 15-day DID cool-off on sub-account moves. unassign_did_from_subaccount returns 409 did_cool_off_in_effect if the DID took a call in the last 15 days; never-used DIDs move immediately, and admins can bypass with force=true.
  • Sub-account assignment uses a lowercase account path (/api/v1/account/...), unlike the capital-Account of every other number endpoint - the SDK hides this, but raw HTTP callers must match the casing.