Messaging API 429 errors during JMeter load test

Just noticed that the /api/v2/messaging/conversations endpoint returns HTTP 429 Too Many Requests when JMeter pushes 200 concurrent messages to Genesys Cloud US1. The rate limit headers show X-RateLimit-Remaining hitting zero quickly. Are there specific throttle settings for digital channels under load that differ from voice?