Skip to main content
This page maps Plivo’s Voice Call API - outbound call creation and in-call control - to the Vobiz REST API and SDKs, method by method. Both share the /Account/{auth_id}/Call/ path shape and the from / to / answer_url model; the differences are the base host, auth headers, SDK method names, and an endpoint Vobiz handles through XML.

Plivo → Vobiz mapping table

REST paths are relative to each base URL: Plivo https://api.plivo.com/v1, Vobiz https://api.vobiz.ai/api/v1. SDK columns use Python names (Node is the camelCase equivalent: make_callmakeCall).

Before / after: make an outbound call

The change is the client constructor and method name (createmake_call), plus passing auth_id explicitly. Call parameters carry over unchanged. Plivo (Python):
Vobiz (Python):
Both return api_id, request_uuid, and message: "Call fired". To dial multiple destinations in one request, both accept up to 1000 numbers in to separated by <.

Key differences & gotchas

  • Auth headers, not Basic auth. Vobiz uses X-Auth-ID and X-Auth-Token request headers instead of Plivo’s HTTP Basic. Raw-HTTP and webhook-verification code must change.
  • Base URL keeps an extra segment: api.vobiz.ai/api/v1 (note the /api before /v1).
  • answer_method is required on Vobiz make_call. Plivo defaults it to POST; always pass it on Vobiz.
  • In-call actions are separate resources. client.calls.play/speak/send_digits/record become client.play_audio, client.speak_text, client.dtmf, client.record_calls.
For everything outside this Call-resource scope (conferences, CDRs, numbers, applications, webhooks/signatures, PlivoXML → VobizXML), see the full migration guide and the Vobiz vs Plivo comparison.