Struggling to understand why the messaging API returns 429 Too Many Requests when simulating 100 concurrent users. The endpoint is v2/conversations/messaging. This happens even though we are well below the documented rate limits for our tier.
Using JMeter 5.4.1 with a ramp-up period of 10 seconds. The error starts appearing after just 20 threads are active. Each thread sends a simple text message to a bot.
The response headers show x-ratelimit-remaining hitting zero quickly. We are in the Asia/Singapore region. Is there a specific header we need to include to handle concurrent write operations better?
Looking for advice on how to structure the JMeter script to avoid hitting these limits prematurely. Any insights on WebSocket connection limits for digital channels would also be appreciated.