TaskRouter's REST API enables you to interact with TaskRouter resources from your server-side applications.
All TaskRouter URLs referenced in the documentation have the following base: https://taskrouter.twilio.com
.
All Twilio REST APIs are served over HTTPS. To ensure data privacy, unencrypted HTTP is not supported.
The TaskRouter REST API exposes the following subresources. You can read about these resources and some common TaskRouter development tasks below:
We encourage you to build your solution using REST API: Best Practices, such as retries with exponential backoff to properly handle the API response Error 429 "Too Many Requests", in case your application has to handle spikes in volumes or unexpected usage patterns.
When API rate limits are calculated, they are averaged over 10 seconds. This calculation method means that our REST APIs can handle rate spikes as long as the average number of requests over 10 seconds remains within the per-second rate limit.
We recommend using restricted API keys as a security best practice. Restricted API keys enable you to decide which TaskRouter API resources an API Key can access, as well as which actions the API key is allowed to take on those API resources. For more information, see Restricted API keys.