Change in GraphQL responses of bulk requests with invalid mutations

We will change the behavior of the GraphQL API for mutations sent in bulk to improve the clarity in the response when at least one of the mutations is invalid.

Currently, none are executed when one or more mutations of a large request are invalid (e.g., because it tries to modify a non-existent field). However, the API response can be mistaken for a successful execution because valid mutations are listed in the data attribute of the response.

From July 14, 2025, at 9 am CEST, the data attribute will return null in the API response in the above cases. The errors attribute will include an entry for each failed mutation, an error description, and a single entry "Error in Request." A "Transaction is rolled back" message in the response will indicate that other valid mutations did not cause an error but weren't applied.

Although there is no urgent need for action, we recommend adjusting your API calls and integrations that use the GraphQL API to process the changed responses and react to the provided errors to create a request in which all mutations are valid for successful processing.