TWILIO ERROR
TRANSLATOR

This account has been disabled and may not be used until it is reactivated.

Premium features are limited to full accounts, so you must upgrade your account if you wish to use them. For guidance on updating your account, please see How to Work with your Free Twilio Trial Account.

An incoming call was made to your application, but was not answered because your account was not active at the time.

The request attempted to initiate an outbound phone call or send a message, but the To phone number you supplied was not a valid phone number or was incorrectly formatted.

your account tried to send a message to a destination that is disabled in Messaging Geo Permissions, or to a destination that Twilio does not support for the channel you are using.

You can send SMS messages only from a sender that your account can use for messaging.

The person you are trying to message has opted out of receiving messages from your Twilio phone number, Channels sender, or Messaging Service.

Message cannot be sent with the current combination of "To" and/or "From" parameters.

The request attempted to send a SMS with a 'To' number that is not a valid mobile number. It is likely that the number that you have specified is a landline number or is an invalid number.

The body of the message is too long.

Twilio queues messages based on the sending rate of a sender or an account. For example a US long code number can send one message segment per second, and a short code may send over 100 message segments per second.

Twilio accepted the message for queueing, but your account was suspended before Twilio could send it.

the destination handset is unavailable on the carrier network. This usually happens when the device is powered off, has no service, cannot receive SMS, or is otherwise temporarily unreachable.

Error 30004 indicates the destination number is blocked from receiving the message.

This delivery error indicates that the destination number is unknown and may no longer exist. Twilio receives this status from carrier partners and returns it to you.

This delivery error means the destination number cannot receive your message. Twilio returns 30006 when the destination is a landline or when a short code cannot reach the destination carrier.

Your message was filtered (blocked) by Twilio or by the carrier. This may be done by Twilio for violating Twilio's Messaging Policy or Acceptable Use Policy, or by a wireless carrier for violating carrier rules or regulations.

we received a generic delivery failure from a carrier or downstream provider and did not receive enough detail to classify the failure more specifically.

not every segment of a multi-part inbound message is received. Long SMS messages are sent as multiple segments, and inbound Message records expose the total segment count in num_segments.

The error code is obsolete. Find more information in the changelog. You provided the MaxPrice parameter in your API request. MaxPrice will prevent a message from sending if it exceeds the price you specified.

Twilio blocks messages to U. S. numbers when you send from a +1 10DLC number that is not associated with an approved A2P 10DLC Campaign. To send application-to-person traffic over a U. S.

We try to provide specific webhook errors whenever possible, however in this instance we are unable to identify the exact cause of the webhook delivery/response issue.

Network outages between Twilio and your web server. URLs that reference private IP addresses or localhost. Twilio's TCP timeout is 10 seconds.

a valid HTTP exchange can't be completed with the webhook URL configured for your messaging workflow. For incoming messages, Twilio makes an HTTP request to your webhook and expects a valid response.

The method attribute of Number must be GET or POST. See the Dial Verb API Reference for more information.

The sendDigits attribute may contain numbers, the # and * characters, the letters A, B, C, D, as well as lowercase w to "wait" for half a second or uppercase W to "wait" for a full second.

Phone Numbers must be in E.164 format. E.164 numbers are formatted \[+] \[country code] \[subscriber number including area code] and can have a maximum of 15 digits.

Twilio does not support calling this number or the number is invalid

Twilio blocked the outbound call before connecting it to the destination number.

The request attempted to initiate an outbound phone call to a phone number that is not enabled on your account.

muted must be either "true" or false".

waitUrl must be either a well formed URL or the empty string ""

This error usually means the credentials on your request are incorrect, expired, deleted, scoped to the wrong account, or not valid for the resource you are trying to access.

you request a resource that Twilio cannot find.

Twilio returns this error when your account exceeds allowed concurrency to Twilio's REST API (HTTP 429 Too Many Requests). Requests that receive 429 responses aren't processed and are safe to retry after backing off.

The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol.

This error indicates that authentication with the provided JWT failed when Twilio attempted to validate the token for an API/SDK request.

The request contained malformed or semantically incorrect parameters. Common occurrences: Lacking a specified Content-Type header field Invalid or missing XML data Invalid parameter type or value

If you received this error code on an inbound message, there was a failure attempting to receive an incoming MMS, as your Twilio phone number was sent an MMS in a region where Twilio does not support incoming MMS.

a downstream carrier rejects your US A2P 10DLC message because your traffic exceeded the rate allowed for your registered campaign.

You have sent the maximum allowable daily messages for your Brand to the carrier. Daily limits are based on your Brand Trust Score. You can check both your Trust Score and your daily Limit in the console here.

the destination carrier requires a pre-registered numeric sender and the sender you used isn't provisioned on that carrier.

Please note that this daily limit is based on the sum of SMS segments and MMS messages you send to T-Mobile subscribers on a 24-hour basis, and is reset daily at midnight PT.

This error is returned when you send a message from a Toll-Free number to a mobile subscriber in the United States or Canada before Toll-Free Verification is approved.

In your response to Twilio's request, the response body is larger than 64 kB.

the combined size of your outbound message and media exceeds the maximum allowed for the channel. The maximum size limit depends on the messaging channel. For an MMS message, the size limit is 5MB.

Twilio could not parse the provided XML Document. Your TwiML document must be a valid XML Document, or Twilio will not be able to read your document.

Misspelled verbs Incorrect case for verbs; TwiML is case-sensitive, so <Say> works, but <say> will not Misspelled or unknown attributes Unknown or unexpected nested elements.

The request attempted to initiate an outbound phone call to a phone number that is not enabled on your account.

Trial accounts and newly upgraded accounts without an approved Primary Customer Profile have limited concurrent calls. Your account has reached other Twilio defined concurrency limits.

Voice calling has been disabled for this account.

The website URL must be in a valid format, starting with https:// and followed by a valid domain name (e.g., https://example.com).

the Authorized Representative phone number in the linked Business Profile is not a valid United States phone number.

the Business Profile linked to your voice registration does not contain a valid US business address.

the Business Registration Number in your linked profile or registration does not meet validation requirements.

Your Voice Integrity Bundle can't be approved when the linked Business Profile is not in twilio-approved status.

you configure or submit a URL that isn't in a valid absolute format.

Twilio cannot establish a TCP connection to your web server. The two attempts to connect to your web server were timed out. Each connection attempt has a 5 second timeout.

Twilio cannot establish a TCP connection to your web server. Your web server rejected our two connection attempts.

All attempts to communicate with your web server were timed out. You set the total timeout using the tt parameter in the URL fragment identifier.

The DNS entry for the URL's host cannot be resolved.

this request has been redirected too many times and may be in a loop.

Twilio sent a webhook to your server and your server responded with a 3xx status code that was not a valid redirect.

Twilio sent a webhook to your server and your server responded with a 4xx or 5xx status code.

During SSL/TLS negotiation, Twilio experienced a connection reset.

Twilio tried to validate your SSL certificate but your certificate has a domain name that does not match the domain we requested.

Twilio tried to validate your SSL certificate but your certificate has expired.

Twilio tried to validate your SSL certificate but was unable to find it in our certificate store.

There was an error connecting to the URL due to an invalid edge location parameter.

There was an error connecting to the URL due to an unsupported edge location parameter.

Your account has not been enabled for HTTP connections over Twilio Interconnect.

One or more retry policies specified in the 'rp' parameter of your connection settings are invalid.

The provided URL template has an invalid format. Please check to see if you have unclosed brackets.

The provided URL template references a nonexistent token.

The version attribute of the Response root element is not valid.

The root element of a Twilio Markup XML document *must* be Response

Twilio is unable to process the Content-Type of the provided URL. Please see Twilio's documentation on accepted content types for more information on valid Content-Types. You must return a Content-Type for all requests.

An internal error has occurred that prevented Twilio from processing your response.

The Conference noun can only be used once inside a Dial verb

Annotate must contain one valid nested element

TwiML documents that execute on the called party's end (via the Dial->Number URL attribute, before the parties are bridged) cannot issue a new Dial.

You have provided an invalid value for the "method" attribute. Valid values are GET or POST. See the Dial Verb API Reference for more information.

Carriers may send invalid Caller IDs on Incoming calls to Twilio. If a specific Caller ID is not explicitly defined on the <Dial> verb, the invalid Caller ID will be passed to the destination.

The only valid nested element for Dial is Number. See the Dial Verb API Reference for more information.

timeLimit must be a positive integer, in seconds.

The country code of the provided phone number is unknown

endConferenceOnExit must be either "true" or false".

waitMethod must be either GET or POST

beep must be either "true" or false".

One or more parameters you sent the REST API were not recognized and were ignored. No harm done, but make sure that you didn't mis-type the parameter you really wanted to send.

Many Twilio resources take descriptive names to help you remember what they are. However, such "FriendlyNames" must be between 1 and 64 characters long.

The resource you accessed is valid, but the HTTP method you attempted to use is not supported for the resource. For example, you cannot DELETE your own account.

Your Twilio account is not active, potentially because you ran out of funds, or you have not yet activated your free trial.

You don't have sufficient privileges to access the requested resource. The user on whose behalf you are attempting to access the API may have revoked your privileges, or you may need to request greater privileges from the user.

You've requested a page size that is too large. The maximum page size is 1000.

Currently only a handful of API resources can be tested with your test credentials. Trying to authenticate with your test credentials to other resources will return a Forbidden error message.

The request attempted to delete a call or message resource before it was completed. If you are attempting to delete a call, wait until the call is completed and try your request again.

The Access Token provided to the Twilio API was invalid.

The issuer or subject of the Access Token provided to the Twilio API was invalid. **Issuer:** The API Key used to sign the the token. **Subject:** The Twilio Account SID from your Live Credentials.

This warning occurs when the Access Token sent to a Twilio API is no longer valid because its exp claim is in the past, the expiration time in the token is invalid, or the expiration was set beyond the maximum allowed lifetime.

The signature for the Access Token provided was invalid. Check that your code is correctly generating signatures using the algorithm and format expected by the Twilio API.

Twilio returns this error when the account lacks permission to access the Twilio API. This commonly occurs when an account is suspended or closed. For assistance, contact Twilio Support via the Console or Help Center.

The request could not be completed due to a conflict with the current state of the target resource.

The Twilio API encountered an error when processing your request. This generally indicates an error in the server handling logic or a timeout in the API. We apologize for the inconvenience.

Twilio returned "Service unavailable", so the request could not be completed as submitted.

Errors related to the Accounts resource

The request attempted to initiate an outbound phone call, but you did not specify what number to call in the 'To' POST parameter

The request attempted to initiate an outbound phone call to a "premium" phone number, such as a toll 976 line.

The request attempted to initiate an outbound phone call to an international phone number, which is not currently supported.

The request attempted to initiate an outbound phone call, but the URL you specified to handle the call was not a valid URL.

The request attempted to initiate an outbound phone call, and you included a SendDigits parameter that wasn't valid. SendDigits is optional, and specifies that Twilio should simulate sending keypad digits when the party answers.

The request attempted to initiate an outbound phone call, but you sent an invalid IfMachine parameter. Twilio can determine if an answering machine or voicemail has answered the call, and behave differently if it has.

The request attempted to initiate an outbound phone call, but the 'From' number you specified is not a verified number for your account.

The request attempted to initiate an outbound phone call or message, but the From parameter you supplied was not a valid phone number, Alphanumeric Sender ID or approved WhatsApp Sender. Twilio accepts phone numbers in E. 164 format (i.

The request attempted to initiate an outbound phone call, but you forgot to include a 'From' parameter. The 'From' parameter is required, and tells Twilio what Caller ID to use for the phone call.

The request attempted to initiate an outbound phone call to a phone number that cannot be reached. Please check the number and try again.

The request attempted to initiate an outbound phone call to a phone number that is not enabled on your account.

Twilio blocked the outbound call before connecting it to the destination.

The request attempted to initiate an outbound phone call to an invalid phone number.\ Please check the phone number and try again.

The request attempted to initiate an outbound phone call from a trial account, but the 'To' number you specified is not a verified number for your account.

You attempted a realtime operation on a Call that was not in-progress. Calls that have completed cannot be recorded or redirected.

TTL specified in the request is too small

TTL specified in the request is too big

The To attribute list is invalid or empty

The To or From attributes have an unsupported prefix for channel

The To or From attributes have channel prefixes what are incompatible

This error indicates that the downstream carrier is experiencing high MMS traffic and isn't accepting the message request.

You sent a message (message SID: SMXXXXX) to a mobile number in a country that requires Alphanumeric Sender ID pre-registration. Our records indicate that you do not have a registered Alphanumeric Sender ID for this country.

Message failed because the size of the content associated with the message exceeded carrier limit

An internal error has occurred with Message Scheduling that prevented Twilio from processing your request.

This error indicates that an internal failure occurred in the messaging service orchestrator while Twilio was processing your response.

Please note that this daily limit is based on the sum of SMS segments and MMS messages you send to T-Mobile subscribers on a 24-hour basis, and is reset daily at midnight PT.

Please note that this daily limit is based on the sum of SMS segments and MMS messages you send to T-Mobile subscribers on a 24-hour basis, and is reset daily at midnight PT.

API version used in the request is invalid

Twilio returns this error when the ContentRetention value in a Message create request is not valid for the request, or when the request depends on Message Privacy settings that are not enabled and configured for your account.

the AddressRetention value in your message request is invalid. Use this parameter only to control whether Twilio stores or obfuscates the address for a message. Supported values are retain and obfuscate.

MaxRate must be a valid float. Twilio returns this error when the value you provide is not a valid floating-point number.

Your message could not be sent because the sending campaign is suspended. A campaign can be suspended on its own or because the associated Brand is suspended.

Twilio could not send your message because the sending number is still being configured for US A2P 10DLC.

your outbound message stays in Twilio's queue longer than the configured ValidityPeriod. When the time elapsed since the message was submitted exceeds ValidityPeriod, Twilio does not send the message.

You receive this error when the account that submitted the message request is not allowed to send outbound messages. Review the account or subaccount that owns the request before you retry.

Twilio detected an OTP in the inbound message body. Twilio redacts the passcode and marks the message failed to help prevent abuse of Twilio numbers.

This warning means an inbound message appears to be machine generated.

You sent a message (message SID: SMXXXXX) to a mobile number in a country that requires Alphanumeric Sender ID pre-registration, and the Sender ID you used is not registered to your account.

you send a message to a destination that requires Alphanumeric Sender ID registration and the sender you provided is not registered or authorized for your account in that country.

you send a message with an Alphanumeric Sender ID that is blocked for the destination because it is generic, suspicious, or not approved for use on your account.

the destination mobile operator flagged the SMS as international traffic that was sent through a domestic gateway. The message was misrouted as domestic.

You see this error when you send a message from a Trial account and the message exceeds the segment limit enforced for Trial accounts.

Set the Validity Period to a supported value before you send the message. This warning appears when the value provided in your API request or inherited from a Messaging Service is outside the allowed range.

the Domain SID in your request does not identify a valid domain in your Twilio Organization.

you try to use a Link Shortening domain that has not been verified in your Twilio Organization.

the TLS certificate for your Twilio Link Shortening domain has expired.

Twilio couldn't shorten the links in your message because the Link Shortening service encountered an application failure.

This warning occurs when a request is received for a Click Tracking domain you registered, but no record is found for the shortened URL. When this happens, the request is redirected to your domain's FallbackUrl.

This warning occurs when a request is received for a Link Shortening domain on your account, but the shortened path can't be matched to a stored shortened link and no FallbackUrl is configured for the domain.

you tried to use Link Shortening click tracking before the domain was set up for the account.

Twilio returns this error when your Link Shortening domain is configured to serve shortened HTTPS links, but the certificate management step is not complete for that domain.

you try to use Click Tracking with an account that is not attached to a Twilio Organization.

the CallbackUrl in your Link Shortening domain configuration isn't a valid URL. Click event data is sent to this callback URL after a recipient clicks a shortened link.

Twilio returns this error when the URL used to resolve a link is on a blocked domain. This error is listed under Programmable SMS and is reported as an error.

Twilio returns this Messaging error when the URL you provide is blocked because it appears on a deny list.

Wrong account is given

Twilio returns this error when you request a Deactivations report for a date earlier than 2020-08-27. Deactivations data is only available from August 27, 2020 onward for the Deactivations resource.

you request a Deactivations report for a date that is not available yet.

the Date field in your Messaging request does not use the required YYYY-MM-DD format. Twilio expects a calendar date only for this field.

you upload a TLS certificate for a Link Shortening domain and the upload doesn't include the certificate, the private key, or both. Upload the certificate and key in PEM format.

Twilio returns this error when it can't parse the certificate you uploaded for a Link Shortening domain. Upload the certificate in PEM format and make sure the certificate content uses the expected PEM block structure.

Twilio returns this error when the private key uploaded for Link Shortening cannot be parsed.

the private key and certificate you upload are individually valid, but they do not match as a pair for your Link Shortening domain.

Twilio returns this when a Link Shortening domain has not had its TLS certificate and private key uploaded yet. Upload the certificate material before you use the domain for link shortening.

Twilio returns this error when the Link Shortening domain configuration does not include a FallbackUrl. Link Shortening domain defaults are set on the domain, and Twilio applies them to any Messaging Service that uses that domain.

the fallback URL configured for a Messaging Service or incoming phone number is not a valid URL.

a Messaging configuration or request does not include the required callbackUrl value.

Cannot create application: application limit exceeded

The phone number is not supported in North America.

The request attempted to update the URL handler associated with a phone number, but the URL you specified was not valid.

The request attempted to update the HTTP method that Twilio uses when somebody calls your phone number, but the Method you supplied was not valid. Valid Method values are GET or POST.

Purchasing phone numbers is a feature that is only available for upgraded accounts. Please upgrade to a Full Twilio Account in order to purchase numbers. You can upgrade from the billing section of your account portal.

This phone number type does not support SMS. You cannot set SmsUrl, SmsMethod, SmsFallbackUrl, or SmsFallbackMethod

You tried to purchase or lookup a phone number that is invalid or add a phone number to a Messaging Service with an invalid Phone Number SID.

You tried to purchase a phone number that is not available for purchase. This error can be triggered in a few ways: Twilio does not own the phone number in question. Twilio owns the number, but it is reserved for another account.

The request attempted to verify a phone number for your account, but that number is already verified for your account.

The request attempted to get a phone number for your account, but the AreaCode parameter you specified was not a valid North American area code.

The request attempted to get a phone number for your account, but Twilio couldn't find any numbers in the area you specified. You may try again with a different AreaCode or contact us to request a number in a certain area.

The request attempted to verify your phone number to activate your Twilio Free Trial Account, but that phone number is already associated with another Free Trial Account. You can only open one Free Trial Account per phone number.

Call delay specified must be an integer between 0 and 60, specifying the number of seconds to delay before initiating the validation call.

The URL given to play during validation isn't a valid URL.

The callback URL given to callback after validation isn't a valid URL.

The AreaCode parameter for provisioning numbers is not supported on the IncomingPhoneNumbers/Local & IncomingPhoneNumbers/TollFree sub-resources.

The resource was not found. Here are some examples of cases that may trigger a 404 error.

This Messaging error indicates that the provider used may be experiencing disruptions that result in errors or request timeouts. The message fails and is not retried to avoid duplicate delivery.

Error 31000 is a generic Programmable Voice error in the 310xx series. More details are often available in the Twilio Debugger or, for the JavaScript SDK, in the twilioError field.

Twilio returns this error when a call flow tries to use a TwiML App resource that Twilio can't find. In the Voice SDK error list, error 31001 appears as TwiML application not found.

Error 31002 is a Voice error that means Twilio declined the connection. Use the Debugger to view details about the underlying cause.

Error 31003 (Connection timeout) occurs in the Voice SDK when a call can't establish or maintain connectivity. You see this error when a Voice SDK call can't establish or maintain connectivity within the expected interval.

The WebSocket connection to the Twilio signaling servers closed unexpectedly during the call. If this issue occurs consistently, verify that the provided hostname resolves correctly.

This error indicates that the incoming call was cancelled because it was not answered in time or it was accepted/rejected by another application instance registered with the same identity.

Twilio returns this error when the Programmable Voice SDK cannot establish a transport to send or receive messages.

31100 indicates a generic malformed request in the Twilio Programmable Voice context.

This error is emitted by the Voice JavaScript SDK, formerly Twilio Client, when the browser has granted permission but getUserMedia fails to acquire the microphone during actions such as device. connect or connection. accept.

Twilio rejected the provided Access Token because its JWT signature couldn't be validated against the API Key secret associated with the token's issuer.

Twilio could not understand the request because the syntax was malformed. 31400 is a Voice error with the message Bad Request.

The server understood the request, but is refusing to fulfill it.

The server has not found anything matching the request.

This indicates a Voice request timed out. Twilio returns this code during Voice SDK registration, unregistration, connect, and CallInvite. accept flows.

This means the callee is currently unavailable. In the Voice JavaScript SDK changelog, Twilio maps this to ClientErrors.TemporarilyUnavilable, and the error dictionary lists it as a Voice ERROR.

Twilio returns this when it receives a busy response while trying to connect a Voice call. In Programmable Voice, <Dial> ends the new call when Twilio receives a busy signal, and the resulting DialCallStatus is busy.

The request has terminated as a result of a bye or cancel.

The server could not fulfill the request due to some unexpected condition.

The server is under maintenance. The Application SID provided in the access token points to an inaccessible URL.

The value of the finishOnKey attribute must be one of the following characters "0123456789#\*". See the Gather Verb API Reference for more information.

The method attribute of Number must be GET or POST. See the Gather Verb API Reference for more information.

The only valid nested elements of the Gather Verb are Say and Play. See the Gather Verb API Reference for more information.

Play requires an audio Content-Type

The value of the loop attribute must be an integer greater or equal to zero. See the Play Verb API Reference for more information.

Play requires an audio Content-Type

The digit attribute may contain numbers, the # and * characters, the letters A, B, C, D, as well as lowercase w to "wait" for half a second or uppercase W to "wait" for a full second.

The method attribute of Record must be GET or POST. See the Record Verb API Reference for more information.

timeout must be a positive integer, in seconds. See the Record Verb API Reference for more information.

The maxLength attribute must be a positive integer in seconds. See the Record Verb API Reference for more information.

The To attribute does not appear to be a phone number that you can SMS

The From phone number does not appear to be a phone number that you can message from

An Invalid Verb has been passed back in a Message reply. Valid Verbs are Message, Sms and Redirect

The method is invalid. You must specify one of GET or POST.

The waitUrl for the Enqueue verb is invalid.

The queue name must be less than 64 characters in length.

The Refer verb is only allowed on SIP call legs, e. g. you can refer an incoming SIP call that originate from SIP infrastructure or an outbound call to a SIP destination.

In order to send a SIP REFER message to an established <Dial> call, the referUrl attribute must be specified in the TwiML. In this case, a REFER was received on a <Dial> call without a referUrl attribute present.

you use the <Message> TwiML verb in a Twilio Region that does not support it. <Message> is currently supported only in the default US1 region. It is not available in IE1 or AU1.

Calls Per Second placed against a SIP trunk exceeded its set limit.

There is a typo in the name of the SIP Domain. When a SIP Domain is created you must press SAVE on Console.

Voice calling has been disabled for this account.

The AOR refers to: username@yoursipdomain.com There is a limit on the number of SIP Endpoints/bindings per AOR

There was a failure attempting to Dial the specified SIP Endpoint. The User specified is not registered.

The conference you tried to access is not currently active. Twilio creates a conference when the first participant connects, but the conference does not start until it is bridged.

Twilio cannot validate one or more <Conference> attributes on a Voice conference. Check the attribute values, URL formats, and limits against the supported <Conference> options.

Twilio could not recognize the provided conference sid or friendly name. Please see https://www.twilio.com/docs/voice/twiml/conference for more documentation.

Downstream Authentication Failed

End User Identification Timeout

The request was received and processed successfully but data is not available for the requested end user.

The request was received but failed due to an invalid configuration.

The request was received but failed during processing due to an error while communicating with the carrier.

The request was received and failed during processing because a downstream provider indicated that the phone number is invalid, although the phone number formatting was valid.

Security Token validation failed

The request was received and failed due to the phone number's carrier not supporting this endpoint.

Request does not contain required Account SID parameter.

The resource your request relates to is currently being deleted.

Specified friendly name is too long

Specified unique name is too long

Specified Service Instance does not exist.

Specified Role does not exist.

A callback request timed out in the callback queue.

Got an HTTP warning in response to the callback URL.

The method attribute of Number must be GET or POST. See the Redirect Verb API Reference for more information.

The phone number you provided as the FROM field to initiate an outbound message is not an incoming phone number assigned to your account. Only phone numbers that you buy from Twilio can be used for outgoing messages.

The Body OR MediaURL parameter is required to send a Message with Twilio.

The 'From' parameter in your API request to send an outbound message did not include a valid Twilio Number, Alphanumeric Sender ID, or Messaging Service SID. You can provide any of the above sender types in your From parameter.

'To' phone number is not specified Your request is not formatted as application/x-www-form-urlencoded