Looking for advice on handling 403 Forbidden errors when scaling predictive routing campaigns via API. We are running JMeter 5.6 in the US1 region to simulate campaign updates for 200 concurrent users. The script hits /api/v2/routing/campaigns/{campaignId} to toggle the state. Initial requests succeed, but after 10 minutes, most threads return 403 with message ‘Insufficient permissions’. The OAuth token is valid and has routing:campaign:write scope. We checked the user role in Genesys Cloud and it seems correct for single requests.
Is there a hidden rate limit or IP-based block triggering these 403s under load? We are not seeing 429 Too Many Requests, which is confusing. The environment is a standard production instance. We need to know if this is a configuration issue on our side or a platform limitation for bulk updates. Please share any insights on predictive routing API throughput limits or workaround strategies for high-concurrency updates.