Trying to understand the correct approach for handling rate limiting when performing bulk screen recording configuration updates across multiple Genesys Cloud organizations via the Platform API. Our AppFoundry integration synchronizes recording policies for enterprise clients, and we are hitting HTTP 429 Too Many Requests errors when executing concurrent POST requests to /api/v2/recording/recording-configs. The application uses multi-org OAuth tokens to provision settings, but the standard retry logic with exponential backoff is not sufficient to handle the volume of updates required during initial deployment phases. We have reviewed the API rate limit documentation, but it is unclear how the limits are calculated per tenant versus per API key in a multi-org context. Are there specific headers or request patterns that can help mitigate these limits, or is there a recommended batch processing strategy for large-scale configuration deployments? Any insights on optimizing the request flow to avoid throttling while maintaining data consistency across tenants would be greatly appreciated.