Notify REST API
We are no longer allowing customers to onboard to Notify. We intend to deprecate the Notify product on April 25, 2024. Learn more in our Notify API End of Life Notice. We prepared this Transition Guide to assist in supporting your push notification use cases.
The Notify REST API allows you to control your notifications workflow from your server. You can create bindings, credentials, and services, as well as send notifications using the endpoints in this REST API.
API Base URL
All URLs in the reference documentation use the following base URL:
All requests to the Notify REST API are served over HTTPS. Unencrypted HTTP is not supported.
You can control your connectivity into Twilio’s platform by including your specific edge location in the subdomain. This will allow you to bring Twilio’s public or private network connectivity closer to your applications for improved performance.
For instance customers with infrastructure in Germany can make use of the
frankfurt edge location by using the base url of:
Notify is supported by all our server-side helper libraries.
HTTP requests to the REST API are protected with HTTP Basic authentication like other REST APIs provided by Twilio. To learn more about how Twilio handles authentication, please refer to our security documentation. In short, you will use your Twilio account SID as the username and your auth token as the password for HTTP Basic authentication.
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.