/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: Plivohttps://api.plivo.com/v1, Vobiz https://api.vobiz.ai/api/v1. SDK columns use Python names (Node is the camelCase equivalent: make_call → makeCall).
Before / after: make an outbound call
The change is the client constructor and method name (create → make_call), plus passing auth_id explicitly. Call parameters carry over unchanged.
Plivo (Python):
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-IDandX-Auth-Tokenrequest 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/apibefore/v1). answer_methodis required on Vobizmake_call. Plivo defaults it toPOST; always pass it on Vobiz.- In-call actions are separate resources.
client.calls.play/speak/send_digits/recordbecomeclient.play_audio,client.speak_text,client.dtmf,client.record_calls.
Call-resource scope (conferences, CDRs, numbers, applications, webhooks/signatures, PlivoXML → VobizXML), see the full migration guide and the Vobiz vs Plivo comparison.