Just noticed that our automated reporting pipeline is hitting rate limits when aggregating call detail records for our 15 BYOC trunks in AP-Southeast-1. The /api/v2/analytics/details/query endpoint returns a 429 status when processing high-volume intervals.
“Error 429: Too Many Requests. Please retry after 60 seconds.”
Is there a recommended batching strategy or specific filter optimization to avoid throttling while maintaining granular trunk-level visibility?