Rate limit headers X-RateLimit-Count missing from API responses

The X-RateLimit-Count header is inconsistent across API endpoints.

I’ve been systematically documenting rate limit headers for our outbound contact list automation. The /api/v2/outbound/contactlists endpoint returns X-RateLimit-Count and X-RateLimit-Limit headers. But the /api/v2/analytics/conversations/details/query endpoint returns neither - it just silently returns a 429 without telling you how close you are to the limit.

We noticed the same inconsistency when building our Teams direct routing health monitor.

Our PowerShell script polls the GC API for trunk status every 30 seconds. Without rate limit headers, we have no way to dynamically adjust our polling interval. We had to hard-code a conservative 5-second delay between calls to avoid hitting the unknown threshold.