What is the standard approach to structure the payload for a custom Data Action in Genesys Cloud Architect when pushing high volumes of concurrent requests via JMeter? We are running a stress test to validate our integration pipeline and hitting a wall with HTTP 400 Bad Request errors specifically on the /api/v2/integrations/dataactions endpoint. The setup involves a simple flow that triggers a Data Action to push call metadata to an external webhook. At low concurrency (10 threads), everything works fine and we see 200 OK responses. As soon as we ramp up to 50 concurrent threads using a JMeter HTTP Request sampler with a CSV Data Set Config, the error rate spikes to nearly 100%. The error message returned is generic: “Invalid Request: Body is missing required fields.” This is confusing because the JSON body in the JMeter request is static and validated against the schema before the test runs. We are using the latest version of the Genesys Cloud REST API docs for the payload structure. The body includes the standard actionId, input parameters for the callId, queueId, and agentEmail. We have verified that the OAuth token is valid and has the necessary scopes for integrations:dataactions. The issue seems to be related to how the platform handles the burst of requests rather than the payload content itself, given that it works at low volume. We have tried adding a constant throughput timer in JMeter to space out the requests, but the 400 errors persist even at 1 request per second per thread. Is there a specific rate limit or payload size restriction for Data Actions that is not documented? Or is there a better way to batch these requests to avoid hitting the platform’s internal validation limits? We need to simulate a realistic load of 100 calls per minute to ensure our data integration holds up during peak hours. Any insights on how to structure the JMeter config or the API call to bypass this validation error would be appreciated. We are currently stuck and cannot proceed with our capacity planning for the new site launch next month.