Skip to main content
Refactoring a Plivo app to Vobiz is mostly a tab-swap: same call flow, a few renamed methods, and an explicit auth_id. Each task below shows the Plivo code and the equivalent Vobiz code in Python and Node - copy the Vobiz tab.
Set your credentials once: AUTH_ID is your Vobiz Auth ID (MA_…), AUTH_TOKEN is your Auth Token. In the Vobiz SDK, api_key is the Auth ID, and every account-scoped method takes that auth_id explicitly.

Set up the client

Make an outbound call

The classic “change a few lines” migration: calls.createcalls.make_call, add auth_id, and to_to.

Answer a call with XML (TTS + menu)

The XML builder mirrors plivoxml - ResponseElement with add_* methods. GetDigits/GetInput become Gather (and add_get_digits is kept as an alias).

Serve the answer URL (Flask / FastAPI / Express)

When Vobiz rings your number it fetches your answer_url over HTTP - return the VobizXML from any web framework, exactly as you did with Plivo. Just build the response with vobizxml and send it as application/xml.

Control a live call

Plivo’s in-call actions live on calls.*; in Vobiz they’re dedicated resources keyed by (auth_id, call_uuid).

Look up a live call

Retrieving a live call needs status="live" on Vobiz.

Search and buy a phone number

List call records

Completed-call history is a first-class cdr resource on Vobiz.

Handle errors

Catch the Vobiz error types (all subclasses of ApiError) the same way you caught Plivo’s.
Need a method that isn’t here? The full per-resource map is in Voice Call API, Call-control XML, and the rest of the Plivo migration section.