PR Campaign 429s at low thread count

Trying to understand why Predictive Routing API hits rate limits so early. Running a basic JMeter test in ap-southeast-1 with just 10 threads against /api/v2/predictiverouting/campaigns. Instant 429s.

“Rate limits are applied per tenant, not per user.”

Docs say it’s tenant-wide, but 10 threads feels too low for a hard cap. Is there a specific limit for campaign creation endpoints? Using standard OAuth token.

I think the limit is not thread count but transaction volume. The system enforces a strict cap on campaign modifications to prevent flow architecture conflicts.

This restriction applies to the tenant, not the user. High-frequency updates during peak CET hours trigger throttling. Reduce the request rate to align with standard API quotas.