Stuck on a 500 Internal Server Error when executing a bulk update via the POST /api/v2/integrations/data-actions endpoint. Our AppFoundry integration handles high-volume payloads, but this specific batch of 500 records fails immediately without a detailed error body. Running v2.0 SDK in a multi-tenant environment with integration:write scope.
You need to inspect the payload structure closely because the 500 error often masks a schema validation failure that the API gateway rejects before it even reaches the business logic layer. When managing high-volume updates across multiple BYOC trunks, the system expects specific nested object structures for routing profiles and trunk associations. If you are sending flat arrays or omitting required carrier-specific metadata, the backend throws a generic 500 instead of a helpful 400.
Check if your JSON includes the trunk_id and region fields explicitly for each record. The documentation suggests that bulk operations require explicit carrier identifiers to prevent cross-region routing conflicts. Also, verify that the integration scope includes routing:write alongside integration:write, as some bulk operations require elevated permissions. Try reducing the batch size to 50 records to isolate whether it is a payload size limit or a data integrity issue. If the smaller batch succeeds, the problem is likely a hidden malformed entry in the larger set.