Moving from Twilio
The Calls API follows Twilio's 2010-04-01 Calls and Recordings resources, and OneML is compatible with TwiML, so most Twilio voice integrations run on Signals after you change the base URL and credentials. This page names Twilio and TwiML directly. It lists what you change, what Signals serves, and where behaviour differs.
What you change
| Twilio | Signals | |
|---|---|---|
| Base URL | https://api.twilio.com | https://api.signals.pressone.africa |
| Path | /2010-04-01/Accounts/{AccountSid}/... | Same |
| Username | Account SID, or an API key SID (SK...) | Voice Account AccountSid only. It must equal the AccountSid in the path. |
| Password | Auth token, or API key secret | Voice Account auth token |
To on create-call | A phone number, a client, or a SIP address | An E.164 number with a leading +, or sip:user@domain for a SIP user registered on your own Signals SIP domain. |
| Webhook signature key | Auth token | Voice Account auth token. X-Twilio-Signature is computed as on Twilio. See Request signatures. |
| Inbound call setup | Phone number voice URL, or a TwiML App | A voice application, with a number routed to it. See Receiving calls. |
Configure your HTTP client, or your helper library's HTTP layer, to send requests to api.signals.pressone.africa. Find the AccountSid and auth token in the Signals console under Developers, Voice Account.
Resources Signals serves
| Resource | Methods | Notes |
|---|---|---|
Calls.json | GET, POST | List and create calls. |
Calls/{CallSid} (.json optional) | GET, POST, DELETE | Fetch, update and delete a call. PATCH is not accepted. |
Calls/{CallSid}/Recordings.json | GET | List a call's recordings. |
Calls/{CallSid}/Recordings/{RecordingSid} (.json optional) | GET, DELETE | Fetch and delete one of the call's recordings. A recording of another call returns 404. |
Calls/{CallSid}/Events.json | GET | The requests Signals made to your URLs during the call, with your responses. See Inspect requests with call events. |
Recordings.json | GET | List the account's recordings. |
Recordings/{RecordingSid} (.json optional) | GET, DELETE | Fetch and delete a recording. |
Recordings/{RecordingSid}.wav | GET, HEAD | Recording audio. .mp3 and other formats are not served. |
Every other Twilio resource, such as Messages, IncomingPhoneNumbers, Applications, Conferences or Queues, returns 404 with code 20404. A method that a served resource does not accept returns 405 with code 20004. Manage numbers and voice applications through the Signals API instead.
Supported verbs
Each OneML verb links to its reference page.
| OneML verb | TwiML verb | Notes |
|---|---|---|
| Say | <Say> | Voice and language handling differ. See Behaviour differences. |
| Play | <Play> | |
| Gather | <Gather> | |
| Record | <Record> | |
| Dial | <Dial> | Bare numbers and <Number> children only. |
| Redirect | <Redirect> | |
| Pause | <Pause> | |
| Hangup | <Hangup> | |
| Reject | <Reject> | |
| Stream | <Connect><Stream> | Two-way, blocking media session. |
| Stream | <Start><Stream>, <Stop><Stream> | One-way, non-blocking media session. |
| Disconnect | None | OneML extension. |
Not supported
The elements and attributes below are not implemented. They fail in different ways: some reject the document, others are skipped, and others are accepted with no effect. A rejected document is visible at once; a skipped element is not, so check your documents for these before you move.
Rejected with a validation error
| Verb | What happens |
|---|---|
<Pay> | Fails validation with <Pay> is not supported yet. Inline Twiml containing <Pay> is refused when you send it: create-call and update-call return 400 with code 12100, and no call is placed or redirected. A <Pay> in a document fetched from your URL or a <Redirect> target fails when Signals runs it, and the call ends as failed, as shown on the call resource or in a status callback. |
Accepted and skipped
These elements pass validation, but nothing runs them. Signals moves on to the next verb with no error, no action request and no signal to your server or the caller.
| Element | Context | Notes |
|---|---|---|
<Enqueue> | Child of <Response> | |
<Leave> | Child of <Response> | |
<Refer> | Child of <Response> | Its sendDigits format is checked, but the verb never runs. |
<Siprec> | Child of <Start> or <Stop> | |
<Transcription> | Child of <Start> or <Stop> | |
<ConversationRelay> | Child of <Connect> | Only <Connect><Stream> is implemented. |
<Room> | Child of <Connect> | |
<VirtualAgent> | Child of <Connect> |
<Start> and <Stop> still need at least one recognized child (<Siprec>, <Stream> or <Transcription>) to pass validation. An empty <Start> or <Stop> is rejected. Only the <Stream> child runs.
Dial targets that are dropped
<Dial> dials bare phone numbers and <Number> children. The following targets parse without error but are dropped when Signals builds the list of numbers to dial. If a <Dial> contains only these targets, Signals reports a failed dial to its action URL when one is set.
| Target | Notes |
|---|---|
<Conference> | |
<Client> | |
<Queue> | |
<Application> | |
<Sip> | Not available for Programmable Voice. To reach your own PBX, dial a Signals number that is routed to your SIP trunk; Signals connects it on net. |
Dial attributes that are ignored
These <Dial> attributes are validated but have no effect.
| Attribute | Notes |
|---|---|
trim | Recording trim is not configurable through <Dial>. |
referUrl | |
recordingTrack |
REST API differences
- The Basic username must be the path
AccountSid. Signals rejects any other username with401and code20003before the request goes further. Twilio API key SIDs (SK...) and parent-account credentials on a subaccount path are not accepted. - SIDs are lowercase.
AccountSid,CallSidandRecordingSidmust be two uppercase letters followed by 32 lowercase hexadecimal characters. Any other form returns404. FromandCallerIdmust be numbers your project holds. Both are E.164 numbers with a leading+, such as+2342013300100. Create-call refuses a number your project does not hold with error21210, and aFromthat is not E.164 with error21212.Toreaches your own SIP users. Besides an E.164 number,Toacceptssip:user@domainwhen the domain is your own Signals SIP domain and the user is registered on it. Another domain, or a user that is not registered, returns error21214. A SIP address with a port, parameters or headers, or asips:address, returns error21211.Byoctakes a Signals carrier connection. As on Twilio,Byocnames the connection the call leaves through, here abyo_ID such asbyo_01a19b7e-deee-779d-953d-a3f8be2d1617. It must be the connection of theFromnumber, which already decides the route, so you rarely need it. Another connection fails the call. A value that is not a connection ID ordefault, or aByocwith asip:To, returns error20001. See Bring your own carrier.- Recording is a create-call parameter; machine detection is not.
Record,RecordingChannels(monoordual),RecordingTrack(inbound,outboundorboth),RecordingStatusCallback,RecordingStatusCallbackMethod(GETorPOST) andRecordingStatusCallbackEvent(in-progress,completedorabsent, repeatable) are supported, and the recording appears withsourceOutboundAPI. Values are not case sensitive, andRecordingStatusCallbackEventaccepts several events separated by spaces, as Twilio documents. TheRecording*fields apply only whenRecordistrueand are ignored otherwise.Method,FallbackMethodandStatusCallbackMethodmust also beGETorPOST. A value outside these sets returns error20001, and aRecordingStatusCallbackthat is not an absolute http(s) URL returns21205.MachineDetection,MachineDetectionTimeoutandTrimare refused with error20001, naming the parameter. TheRecordingSidin the first recording callback already resolves onGET Recordings/{RecordingSid}: the recording readsin-progresswhile it is captured,processingwhile it is checked, and thencompletedorabsent. Recording callbacks carryRecordingStartTimeonce recording has started, and anabsentcallback carriesErrorCodewhen Signals knows why nothing was recorded (see Recording error codes). A recording cannot be paused, resumed or stopped while the call runs: there is noCalls/{CallSid}/Recordingscreate or update. ApplicationSidis rejected. Create-call fails with error21605whenApplicationSidis present. UseUrlorTwiml. A Signals voice application ID is not accepted there either; voice applications serve inbound numbers.- A project needs a billing account to place calls. Without one, create-call returns
403with code20005and the call is not placed. - Inbound numbers point at voice applications. A Signals number has no voice URL of its own. Create a voice application and route the number to it.
Timeoutdefaults to 60 seconds on create-call, the same as Twilio.- Empty and repeated fields. A form field with an empty value counts as absent, and when a field is repeated only its first value counts, except
StatusCallbackEventandRecordingStatusCallbackEvent. Fields an operation does not list are ignored, as on Twilio. - A new call can already be ringing. Create-call returns the call as Signals records it. That is usually
queued, but it can already beringingwhen the call's first progress event arrived first. - Call updates use form fields. Send
POSTwith the fields as a form.UrlorTwimlredirects anin-progresscall, and the voice platform refuses a redirect before answer with error21220.Status=completedends a queued, ringing or in-progress call.Status=canceledends only a queued or ringing call: on an answered call Signals refuses it with error21220, where Twilio ignores it, so sendStatus=completedinstead.Statuscannot be combined withUrl,MethodorTwiml. - Updates can change call parameters.
FallbackUrl,FallbackMethod,StatusCallback,StatusCallbackMethodandTimeLimitmay be sent alone or with a redirect or a status.TimeLimitcounts from answer, so it is not applied to a call that has not been answered; a limit the call has already passed returns error13216. A call that has ended accepts no update (21220), and a body with none of these fields is refused with21220too. - An update answers with the call as Signals records it. The
200response can still show the status from before the update until the voice platform reports the change. DELETEdeletes the call record. It does not hang up. A call that has not ended returns400with code20009. After the delete, fetching or updating the call returns404, it is no longer listed, and itsEvents.jsonreturns404. Its recordings are kept and can still be listed, fetched, downloaded and deleted.- Lists are paginated with
PageandPageSize.PageSizedefaults to 50 and accepts 1 to 1,000. Only the PascalCase names are recognized, and there is noPageToken: follownext_page_uri, which repeats your filters. - The Calls resource holds Programmable Voice calls only. A call an Automation placed is not listed, and fetching or deleting it returns
404with code20404. - Call list filters.
Calls.jsonfilters byStatus,To,From,ParentCallSid, andStartTimeorEndTimewith=,<or>. An unknownStatusreturns error20001.StartTimecomparesdate_created, the time Signals first recorded the call.EndTimecomparesend_time. A date value is a UTC day, as on Twilio:StartTime=2026-10-26matches calls created on 26 October,StartTime>2026-10-26matches calls created on or after 26 October, andStartTime<2026-10-26matches calls created before 26 October. With an instant,<matches times strictly before it,>matches times at or after it, and=matches the whole UTC day the instant falls on:StartTime=2026-10-26T09:00:00Zmatches every call created on 26 October. Twilio'sStartTime>=andStartTime<=spellings are the same>and<filters, because the=separates the name from the value. - Recording list filters.
Recordings.jsonandCalls/{CallSid}/Recordings.jsonfilter byDateCreatedwith=,<or>, with the same date and instant rules asStartTime. The account-wide list also filters byCallSid, and both acceptIncludeSoftDeleted. ACallSidyour account does not know lists no recordings. - Deleted recordings stay visible on request.
DELETE Recordings/{RecordingSid}andDELETE Calls/{CallSid}/Recordings/{RecordingSid}return204, and so does a repeat. The recording is then hidden unless you sendIncludeSoftDeleted=true, which shows it withstatusdeleted. A recording still being processed, or under a legal hold, returns400with code20009. - Recording audio needs authentication.
RecordingUrland the.wavresource require yourAccountSidand auth token. Recording metadata carries nomedia_url. Audio that is not ready yet returns404, as on Twilio. See Download recording audio. priceis the connectivity charge. A call'spriceis negative, as on Twilio, in the currency inprice_unit, and staysnulluntil every charge on the call has been rated.- Call resources link to their events. Call responses include
subresource_uris.events, pointing atCalls/{CallSid}/Events.json. - Request bodies are limited to 1 MiB. A larger body returns
413with code20001. - Timeouts return
504. Signals waits at most 10 seconds for the voice platform to confirm a new call and 15 seconds for it to apply an update. - Errors have one shape. Every error is Twilio-style JSON with
code,message,statusandmore_info, whether Signals raised it or the voice platform did. The voice platform's refusals of a create or an update are returned unchanged.
Recording error codes
An absent recording callback and the absent Recordings resource carry one of these codes in ErrorCode and error_code when the recording could not start or its audio could not be kept. They are Signals codes, not Twilio's. A recording that is absent without a code ended before any audio was captured, or its stored audio failed Signals' own verification.
| Code | Meaning |
|---|---|
61001 | The call leg was gone when recording was to start. |
61002 | The voice platform could not write the recording file. |
61003 | The voice platform did not confirm the recording start in time. |
61004 | The recorded audio was not a valid file, so it was not kept. |
The call itself continues whatever the recording's outcome.
Behaviour differences
<Dial>works only inside an active call. As with Twilio,<Dial>does not start an outbound call. Create the call through the Calls API, then use<Dial>in its OneML.<Dial>caller IDs depend on how the call started. On a call you created through the Calls API,callerIdmay be a number your project owns or any other E.164 number, written with a leading+, that is not another customer's number. On an inbound call,callerIdmust be a number your project owns. WithoutcallerId, Signals usesFromfor calls created through the Calls API andTofor inbound calls. It never presents an arbitrary incoming caller number as yours. Dialed numbers go through your project's outbound policy.<Dial record>dual-channel modes record one mixed channel. The from-answer and from-ringing start points are honoured, butrecord-from-answer-dualandrecord-from-ringing-dualdo not produce a channel per party.<Say>uses Google Cloud Text-to-Speech, not Amazon Polly, including for theman,womanandalicealiases.<Say voice>is not checked against a list.man(the default) and any unrecognized plain string select a Google male voice;womanandalice, in lowercase, select a Google female voice. See Voice selection.<Say voice>accepts a provider prefix.Google.<voice-name>andElevenlabs.<voice-id>select a specific Google Cloud Text-to-Speech or ElevenLabs voice.<Say language>must match the voice. A mismatch returns a clear error. The built-in aliases supportenanden-US. For another Google language, select a matchingGoogle.<voice-name>. The current ElevenLabs integration acceptsenanden-US.<Number sendDigits>is accepted but not applied. Signals checks its format but does not send the tones.<Connect>actionandmethodare never requested. When a<Connect><Stream>session ends, the next verb runs.<Start><Stream>metadata omitsaccount_sid.<Connect><Stream>includes it. See Stream.- Inbound status callbacks come from the voice application. An inbound call sends a
completedstatus callback only when its voice application has a status callback URL. API-created calls useStatusCallbackas on Twilio. See Status callbacks. StatusCallbackEventis not validated. Any string is accepted; onlyinitiated,ringing,answeredandcompletedever match an event.- The webhook user agent keeps its Twilio name. Requests carry
User-Agent: TwilioProxy/1.1.
Next steps
- Quickstart: place a call with your Signals credentials.
- Receiving calls: move an inbound number to a voice application.
- OneML overview: every OneML verb and attribute.
- Calls API reference: every Calls API endpoint.