Overview
Twilio provides certain headers in REST API responses to help you monitor your API usage. This is especially beneficial for Twilio TaskRouter, as its APIs have strict limits.
By understanding these headers, you gain insights into your account's performance, helping you optimize API usage and plan for future growth effectively.
What You Need To Know
REST API Headers
Along with the REST API Headers for monitoring account-level concurrency, TaskRouter offers additional measures to monitor TaskRouter-specific endpoints.
| Header | Description |
|---|---|
| X-Rate-Limit-Limit | Defines the maximum number of requests permitted for a specific TaskRouter method. |
| X-Rate-Limit-Remaining | Shows the remaining number of requests before hitting your rate limit. |
| X-Rate-Limit-Config | Offers configuration details associated with rate limits. |
Real-Time Monitoring
Monitor the X-Rate-Limit-Remaining header to track your TaskRouter API consumption in real-time. Setting up alerts based on this value helps proactively manage your API usage to prevent reaching rate limits.
Event Streams
In addition to headers, you can also leverage Event Streams for TaskRouter data.
The event type com.twilio.apiusage.taskrouter.ratelimits provides information about your TaskRouter API consumption, enabling you to stream this information one of your services.
Conclusion
By understanding and utilizing this data, you can better manage your Twilio account's API usage and ensure optimal performance.