Migrate from Twilio

Most Twilio Programmable Voice code ports with small changes. Edesy accepts Twilio-style Basic auth (Account SID and Auth Token), serves Twilio-shaped paths such as /v1/Accounts/{AccountSid}/Calls, and sends status callbacks with the same PascalCase fields. The one real difference is the instruction format: answer URLs return VoiceML (JSON), not TwiML (XML), and Edesy does not parse TwiML.

Endpoint mapping#

Authentication#

# Twilio
curl -u "$TWILIO_ACCOUNT_SID:$TWILIO_AUTH_TOKEN" https://api.twilio.com/2010-04-01/Accounts/$TWILIO_ACCOUNT_SID/Calls.json

# Edesy
curl -u "$ACCOUNT_SID:$AUTH_TOKEN" https://voice-api.edesy.in/v1/Accounts/$ACCOUNT_SID/Calls

Your Account SID is your workspace ID; the Auth Token is on the credentials card of the portal dashboard. For new code, a Bearer API key (Authorization: Bearer sk_...) is simpler. See Authentication.

Request parameters#

Edesy uses JSON with snake_case names.

Fields Edesy does not recognise are not errors: they are listed in meta.ignored_fields, which makes leftover Twilio parameters easy to spot.

Status callbacks#

The payload keeps Twilio's PascalCase names: CallSid, AccountSid, From, To, CallStatus, Direction, Duration. CallStatus uses the same values (initiated, ringing, in-progress, completed, busy, no-answer, failed, canceled).

Differences to plan for:

• With POST, the body is JSON, not form-encoded. Parse JSON.
• Edesy adds SipResponseCode, HangupReason and CallOutcome on the final event, so you can tell "phone switched off" from "invalid number". See Call Events and Outcomes.
• Your custom_parameters come back under Custom.
• The signature header is X-Webhook-Signature (HMAC-SHA256 over timestamp and body), not X-Twilio-Signature. See Status Callbacks.
• Call SIDs look like CA_ plus a UUID.

VoiceML instead of TwiML#

This is the main code change. Edesy does not parse TwiML; your answer URL must return VoiceML JSON with Content-Type: application/json.

TwiML:

<Response>
  <Say language="en-IN">Thanks for calling Acme.</Say>
  <Play>https://cdn.example.com/hold.mp3</Play>
  <Hangup/>
</Response>

VoiceML:

{
  "instructions": [
    { "verb": "say", "text": "Thanks for calling Acme.", "language": "en-IN" },
    { "verb": "play", "url": "https://cdn.example.com/hold.mp3" },
    { "verb": "hangup" }
  ]
}

Multi-step flows that chain <Gather action> callbacks do not translate one-to-one: Edesy runs the document your answer URL returns, and action callbacks are not covered by these docs yet. Rebuild multi-step keypad menus in IVR Studio, or move conversational flows to Conversation Relay. Full reference: VoiceML Reference.

If you have many TwiML handlers, one option is a small adapter in your own code that maps your TwiML builder's output to the VoiceML JSON above.

Media Streams#

Twilio Media Streams sends base64 mu-law audio inside JSON messages. Edesy Media Streams sends raw L16 PCM (16-bit, mono, 8 or 16 kHz) as binary WebSocket frames after one JSON metadata frame, and takes killAudio / disconnect control messages. A stock Twilio serializer will not work; swap it for an Edesy one. See Media Streams, which includes a Pipecat serializer.

ConversationRelay#

The Conversation Relay protocol is compatible with Twilio ConversationRelay: the same setup, prompt, interrupt, dtmf messages in, and text, play, sendDigits, language, end out. A bot written for Twilio usually works after pointing an Edesy number at its URL. See Conversation Relay.

Numbers and billing#

• Numbers: buy Indian mobile, landline, toll-free and 92-series virtual numbers self-serve after KYC. You can also bring a Twilio Elastic SIP trunk to Edesy as a carrier; see SIP trunking.
• Billing: prepaid INR wallet topped up with Razorpay, GST invoices with your GSTIN, Rs 0.50 per minute with a 60-second pulse, unanswered calls free, no minimum commitment. Prices exclude 18% GST.
• SDKs: Edesy does not publish server SDK packages. Call the REST API with your HTTP client; the endpoints are small.

Migration checklist#

1. Complete KYC and buy (or bring) your numbers.
2. Create an API key, or copy your Account SID and Auth Token.
3. Change the base URL to https://voice-api.edesy.in/v1 and send JSON bodies.
4. Convert answer-URL handlers from TwiML to VoiceML.
5. Update status-callback handlers to parse JSON and read HangupReason / CallOutcome.
6. Swap Media Streams serializers, if you use them.
7. Route inbound numbers with PUT/v1/phone-numbers/{id}/inbound.
8. Place test calls and read GET/v1/calls/{CallSid}/events for each path.

Questions about a larger migration: /contact or book a demo.