Skip to main content
Vobiz mirrors Plivo’s recording model closely - same Record XML verb, same Record/ and Recording/ REST endpoints, and webhook-delivered transcription. Migration is mostly a base-URL (https://api.vobiz.ai/api/v1), auth-header (X-Auth-ID + X-Auth-Token, not Basic auth), and SDK-namespace swap.

Plivo → Vobiz mapping

Before / after - record a voicemail in XML

Plivo (PlivoXML) and Vobiz (VobizXML) share the verb and attribute names verbatim:
Plivo
Vobiz
The action-URL callback params also match: RecordUrl, RecordingID, RecordingDuration, RecordingDurationMs, RecordingStartMs, RecordingEndMs. Vobiz adds RecordingEndReason (RecordingTimeout / maxLength / FinishedOnKey / HungUp).

Key differences & gotchas

  • Recording namespace split. Plivo puts in-call recording on client.calls; Vobiz splits it into client.record_calls (live call) and client.conference_recording (conference). Stored-asset list/get/delete lives on client.recordings on both sides.
  • recordChannelType location. On Vobiz, mono/stereo is set via record_channel_type on the REST Record/ call.
  • Transcription delivery. Both support auto and hybrid. Vobiz posts the result to transcriptionUrl (XML) or the recording callback_url (REST) - wire up the webhook to receive it.
  • timeout default differs. timeout is the trailing-silence cutoff (Vobiz default 60s, Plivo default 15s); re-check your Plivo values after migrating.