Skip to contentSkip to navigationSkip to topbar
Page toolsOn this page
Looking for more inspiration?Visit the

Notify API


(error)

Twilio Notify deprecated

Twilio stopped supporting Notify in October 2022.

To control your notifications workflow from your server, use the Notify API. You can create bindings, credentials, and services, as well as send notifications using these API resources.


API Base URL

api-base-url page anchor

All URLs in the reference documentation use the following base URL:

https://notify.twilio.com/v1

Twilio serves all requests to the Notify API over Secure HTTP (HTTPS) only.

Edge locations

edge-locations page anchor

To control your connectivity to Twilio's platform, include your specific edge location in the subdomain. By bringing Twilio's public or private network connectivity closer to your apps, your app performance improves.

For example: To use the frankfurt edge location, customers with infrastructure in Germany can change the base URL to the following:

https://notify.frankfurt.us1.twilio.com/v1

All Twilio server-side SDKs support the Notify API.


To authenticate requests to the Twilio APIs, Twilio supports HTTP Basic authentication(link takes you to an external page). Use your API key as the username and your API key secret as the password. You can create an API key either in the Twilio Console or using the API.

Note: Twilio recommends using API keys for authentication in production apps. For local testing, you can use your Account SID as the username and your Auth token as the password. You can find your Account SID and Auth Token in the Twilio Console(link takes you to an external page).

Learn more about Twilio API authentication.