What is the correct way to handle 403 on BYOC trunk provisioning API?

What is the standard approach to handle 403 Forbidden errors when provisioning BYOC trunks via API under high concurrency?

Running JMeter tests to validate API throughput for initial setup. The UI works fine, but the API blocks requests after 50 concurrent threads.

  • Endpoint: /api/v2/architect/byoc/trunks
  • SDK: Genesys Cloud Java SDK 2.1.0
  • Error: 403 Forbidden (Rate limit exceeded)

The standard rate limit docs do not mention specific caps for this endpoint. Is there a hidden throttle for BYOC configuration?