Pagination Limits on GET /api/v2/telephony/providers/edges/trunks for Bulk BYOC Audits

How should I properly to retrieve a complete list of all active BYOC trunks across multiple regions without hitting the undocumented pagination ceiling in the Telephony Providers API?

I am currently executing a script to audit the registration status and failover logic for our fifteen BYOC trunks distributed across AP-SG, EU-FR, and US-VA. The goal is to correlate trunk health metrics with the analytics reporting data I previously discussed regarding conversation duration mismatches. When calling GET /api/v2/telephony/providers/edges/trunks with a page size of 250, the response consistently truncates after returning only forty-two records, despite the total count indicating significantly more entries. The API documentation suggests a maximum page size of 250, yet increasing this value results in a 400 Bad Request error stating ‘pageSize exceeds maximum allowed value’.

The environment is running the latest stable release of the Genesys Cloud platform in the Asia/Singapore region. I have verified that the OAuth token has the necessary ‘telephony:edge:trunk:read’ scope. The issue persists even when filtering by specific trunk groups or carrier IDs. This limitation creates a significant bottleneck for automated health checks, as we need to iterate through all trunks to detect registration flapping or 408 Request Timeout errors before they impact outbound routing. The current workaround involves manual pagination, which is inefficient given the volume of data and the strict rate limits on the /telephony/providers/edges endpoint. Has anyone found a reliable method to bypass this limitation or a different endpoint that provides a comprehensive view of all BYOC trunk configurations without requiring extensive pagination loops? I suspect this might be related to how the API handles multi-region data aggregation, but I need confirmation on the best practice for bulk retrieval in this context.