Undelivered messages generally return a 30XXX error code. Check your message’s status and look for an error code in your Twilio project's Programmable Messaging logs via either Console, or the REST API. The "Undelivered" message status indicates that Twilio has received a delivery receipt indicating that the message was not delivered. For example, a mismatch between the actual file type and the Content-Type header returned by the server would cause an MMS message to fail with error 12300. (Specific to Twilio MMS media messaging) Error 11200, 11751, or 12300: These errors correspond to specific problems that can happen when Twilio attempts to retrieve media from the MediaUrl you provided to send an MMS media message.Check the email associated with your Twilio account for details. When your account is suspended, Twilio will send you an email with the suspension reason. Error 30002 "Account suspended:" your Twilio account is currently suspended, for example due to running out of account funds and not having auto-recharge configured.Error 30001 "Queue overflow:" you have exceeding the maximum queue length of your Twilio number or sender, or the message queued for longer than the ValidityPeriod you specified in your API request.The most common reasons for "Failed" messages are: This status is different from the "Undelivered" status, described below. Twilio does not bill for "Failed" messages, because these never left Twilio's platform. The "Failed" message status indicates that Twilio was unable to send the message. If your error is not listed here, you can find the list of 2XXXX REST API errors along with instructions for resolving these issues in our API Errors and Warnings Dictionary. We suggest all "To" numbers should use E.164 formatting to help ensure proper routing.
The "To" phone number is not properly formatted.To determine if Twilio supports a particular carrier, please search for the country on the SMS Pricing page and scroll to the section labeled "All SMS Pricing for." If the carrier does not appear on that list, Twilio cannot send SMS messages to that carrier at this time. Twilio supports most carriers worldwide, but there are still carriers which we do not yet support. The carrier you are sending to is not a supported carrier.Įrror 21610 : You are attempting to send a message to a number that has opted out of receiving messages using a STOP keyword.Įrror 21612. Twilio will only allow you to do this with phone calls, not SMS. You might be trying to send SMS from a number you have verified with Twilio.All other Twilio phone numbers are not capable of sending SMS messages. This list shows which Twilio phone numbers are SMS enabled. You might be trying to send SMS from a phone number which is only enabled for voice.Įrror 21606 : You are attempting to use a "From" number which is not capable of sending SMS messages to your "To" number. Please note that using the Test Credentials will produce a response indicating that the message has been sent, but the message will not actually be sent.Įrror 21408 : You need to enable SMS permissions for this country on the Global SMS Permissions page. Here are the most common problems we see:Įrror 20003 : Be sure that you are using the correct Account SID and Auth Token. This type of REST API error generally returns a 2XXXX error code. For an invalid request, Twilio returns a 400 Bad Request response, with an error code and message explaining what the issue is. You can send your message via a REST API request, or through the API Explorer in Console. Next, try sending your message again, and check for similar results. If you aren't seeing a record of your message, then there was likely an issue with with your API request, or possibly a Twilio incident.įirst, check the Twilio Status Page to see if an active incident could be causing your issues. To validate that we successfully received and processed your request, check your Twilio project’s Programmable Messaging logs for the outbound message record via either Console, or the REST API. When Twilio receives a valid API request to send an outbound message, we return a 201 Created response, and create a record of the message in your logs. A note about error handling with Messaging Services.Fear not! This article is designed to help you walk through troubleshooting steps to diagnose, and hopefully fix, the problem. You've tried sending an SMS or MMS message, but it didn't arrive.
0 kommentar(er)
