jambonz vs Plivo Voice API

jambonz

OpenAPI 3.1 and AsyncAPI documents, an llms.txt and Markdown pages cover the REST and WebSocket APIs, and session prices are public. No status page, security.txt or advisory was found, API keys carry no scopes, and the 2021 privacy policy says audio is never stored while the October 2026 release notes say support keeps call audio for a few days.

Plivo Voice API

US outbound at $0.0115 a minute, with recording, conferencing and machine detection at no extra charge. 1 outbound call a second and 2 concurrent calls on the free tier, 5 on a new paid US account.

jambonz

1. Send Authorization: Bearer <token> to https://api.jambonz.cloud/v1, the server in the OpenAPI files. The REST introduction page gives https://jambonz.cloud/api instead, so confirm the base URL with the operator
2. Create a call with from, to and either application_sid or call_hook. Do not retry a timed-out create without checking GET /Accounts/{AccountSid}/Calls first
3. Read ratelimit-remaining and ratelimit-reset on every response and stop when a 429 arrives
4. Append #rc=3&rp=5xx,ct to an application URL to turn on webhook retries. HTTP webhooks are not retried by default
5. Check the account has a carrier and speech credentials before dialling. jambonz does not supply numbers, minutes or speech services

Plivo Voice API

1. Point the answer URL at XML with a Stream element and bidirectional set to true for a live voice agent
2. Check concurrency before dialling out in bulk. Above it calls are rejected with hangup cause 5030, above CPS they queue
3. Don't rely on the status callback alone to learn a call ended. Poll the call if the webhook doesn't arrive
4. Validate webhook signatures before acting on call events