If you run into any issues or errors when attempting to send Twilio Notify messages, please run through these troubleshooting steps.
Notifications Resource API Request Errors
Successful HTTP POST requests to the Notifications API Resource will result in an HTTP 201 Response. This indicates that Twilio successfully received the request, and will attempt to send the notification.
Any other HTTP response to an API request will be caused by an error. Please check the response for the Error number and Message for details on what went wrong.
Check Notify Service Logs in Console
- Login to your account at www.twilio.com.
- From the left side navigation bar, click Notify .
- Click Services, and then select the desired Notify service.
- Click Logs.
- Click a notification to view the details for each delivery attempt.
Some communication channel bindings may be automatically deleted when certain unrecoverable errors occur, such as an SMS to an invalid phone number, or a push message with an invalid token. If the number of delivery attempts in your service’s logs does not correspond to your expectations, check your users’ Bindings.
SMS Notifications are Not Arriving at Handset
Twilio Notify SMS messages could fail to arrive at the handset due to a number of reasons. If the API request was successful, and there’s no error in the Notify Service Logs, please troubleshoot like a standard SMS message. For more information, please see our Troubleshooting undelivered Twilio SMS messages article.
Push Notifications are Not Arriving at Handset
If attempting to send Apple (APN) or Google (FCM or GCM) Push messages, check that the application is handling the notification in-app when necessary -
- For iOS, this is required when the app is in the foreground.
Note: iOS also allows message delivery logging - more information can be found in Apple’s Push Notifications Troubleshooting developer documentation.
- For Android, this is at all times.