How to Send Web API Batch Requests in Dynamics 365

Erick McCollum | 02 Nov 2019

DISCLAIMER: The opinions expressed on this website are solely my own, and they are not associated with my employer, another person, or another organization in any way. All information on this website is provided "as is", without guarantee or warranty of any kind. Read the full disclaimer here.

There are times when developing in Dynamics 365 where you may need to perform multiple operations at one time. For example, you may want to create three new account records on the click of a button. In order to do so, it is possible to send three separate HTTP requests to create these three account records using the Dynamics 365 Web API. However this is not ideal, as it becomes far less efficient as the number of records to create increases. In the future if you ever need to increase the record count to create twenty records, then you are having to send twenty different HTTP requests to complete this.

The more efficient, and more performant, option would be to send a Web API batch request to create these twenty account records in one HTTP request.

What are some benefits to using a Web API batch request?

There are many benefits to performing Web API operations using a batch request. I have outlined a few below:

  • Better Performance: Sending multiple operations in one batch request reduces the number of HTTP requests that need to be sent from the client. This means better application performance.
  • More Efficient: Similar to the above point, reducing the number of HTTP requests that are sent means that there are more resources available for the client to use. This increase in efficiency will have a positive effect.
  • Transactional Nature: Web API batch requests can be configured to act as a single transaction by using change sets. This means that if one request fails, they all will fail. This can be useful in certain situations. I won’t go into detail regarding change sets in this article. However, you can find more information at the official Microsoft documentation: Change sets

Okay, I am interested, but how do I do it?

When creating a Dynamics 365 Web API batch request, there are very specific steps and guidelines to follow in order to for it to be successful. This is because the Web API batch request body is essentially a body of text that is parsed and executed on the server side. It is not inherently structured like a JSON request body is, for example. Therefore, this request body must meet certain requirements in order for it to be successful. More information on these requirements may be found at the official Microsoft documentation page: Execute batch operations using the Web API.

In this article, I will walk through an example for sending a Dynamics 365 Web API batch request using JavaScript to create three account records. It is possible to combine POST, PATCH, DELETE, and even GET operations in one batch request. However, for the purposes of keeping this example simple, I will only focus on sending POST requests.

First, I will create a constructor function to make it easier to create and send the Web API batch request:

    function BatchPostAccounts() { 
        this.apiUrl = Xrm.Utility.getGlobalContext().getClientUrl() + 
        this.uniqueId = "batch_" + (new Date().getTime()); 
        this.batchItemHeader = "--" +  
            this.uniqueId +  
            "\nContent-Type: application/http\nContent-Transfer-Encoding:binary"; 
        this.content = []; 
    BatchPostAccounts.prototype.addRequestItem = function(entity) { 
        this.content.push("POST " + this.apiUrl + "accounts" + " HTTP/1.1"); 
        this.content.push("Content-Type: application/json;type=entry"); 
    BatchPostAccounts.prototype.sendRequest = function() { 
        this.content.push("--" + this.uniqueId + "--"); 
        this.content.push(" "); 
        var xhr = new XMLHttpRequest();"POST", encodeURI(this.apiUrl + "$batch")); 
        xhr.setRequestHeader("Content-Type", "multipart/mixed;boundary=" + this.uniqueId); 
        xhr.setRequestHeader("Accept", "application/json"); 
        xhr.setRequestHeader("OData-MaxVersion", "4.0"); 
        xhr.setRequestHeader("OData-Version", "4.0"); 
            function() {  
                console.log("Batch request response code: " + xhr.status);  

Please note, from my experience the additional empty space after the batch closing tag (line #21 above) is important for formatting issues. The server may return an “invalid JSON” error response if a trailing space is not included in the batch request body.

Next, I will create three account entity objects in JSON:

    var firstAccount = { 
        name: "Test Account 1" 
    var secondAccount = { 
        name: "Test Account 2" 
    var thirdAccount = { 
        name: "Test Account 3" 

Finally, I will feed these account entity objects into the constructor function, and send the Web API batch request:

    var batchRequest = new BatchPostAccounts(); 

The full code used in this example may be found in my GitHub repository at the following link: WebApiBatch Sample Code


For additional information and guidance, please see the following resources: