Skip to main content
Plivo and Vobiz ship server SDKs for the same seven languages, and the Vobiz SDKs mirror Plivo’s resource layout and XML-builder shape. What changes when you migrate: you git-clone the Vobiz SDKs from github.com/vobiz-ai (no registry install), you construct the client with X-Auth-ID/X-Auth-Token headers instead of HTTP Basic, and a handful of method names differ (calls.createcalls.make_call, plus an explicit auth_id).

Client init & method-name mapping

CDRs live under client.cdr.* on Vobiz (Plivo folds completed-call lookups into calls.get). For the verb-by-verb XML mapping see Convert PlivoXML to VobizXML.

Before / after: client init + outbound call

The call parameters (from, to, answer_url, answer_method, etc.) carry over unchanged. What changes is the constructor, the method name, and the added auth_id.

Key differences & gotchas

  • Install is git-clone, not registry. Clone vobiz-ai/Vobiz-<Language>-SDK and install from the checkout (Go is the exception: go get github.com/vobiz-ai/Vobiz-Go-SDK). Pin to a tag/commit for reproducible builds.
  • Auth is headers, not Basic. Vobiz sends api_key as X-Auth-ID and auth_token as X-Auth-Token; the constructor keyword is api_key= (Python) / apiKey: (Node), not auth_id.
  • Every account-scoped method takes an explicit auth_id - Plivo infers it from the credential.
  • Purpose-built call resources. Vobiz uses live_calls for in-progress calls and cdr for completed-call records - each resource is dedicated to its job.
  • Gather uses executionTimeout, never timeout - the most common porting mistake. timeout in VobizXML belongs only to <Dial>/<Number> (ring timeout).

Endpoint & SDK mapping

The full REST resource and method mapping, with the make-call contract.

Convert PlivoXML to VobizXML

Verb-by-verb XML mapping and the GetDigits/GetInput to Gather rename.