Asynchronous web endpoints

An asynchronous web endpoint intercepts messages to a Web API and writes them to the message queue. Each time the system accepts such an API request, it generates a UUID identifier. Magento includes this UUID when it adds the message to the queue. Then, a consumer reads the messages from the queue and executes them one-by-one.

Use the bin/magento queue:consumers:start async.operations.all command to start the consumer that handles asynchronous and bulk API messages.

Magento supports the following types of asynchronous requests:

• POST
• PUT
• PATCH

GET and DELETE requests are not supported. Although Magento does not currently implement any PATCH requests, they are supported in custom extensions.

The route to all asynchronous calls contains the prefix /async, added before /V1 of a standard synchronous endpoint. For example:

1
2
POST /async/V1/products
PUT /async/V1/products/:sku

Magento Open Source and Magento Commerce installations support asynchronous web endpoints.

The REST API documentation provides a list of all current synchronous Magento API routes.

The response of an asynchronous request contains the following fields:

Sample usage

The following call asynchronously changes the price of the product that has a sku of 24-MB01:

PUT /rest//async/V1/products/24-MB01

Payload

1
2
3
4
5
{
  "product": {
    "price": 29
  }
}

Response

Magento generates a bulk_uuid for each asynchronous request. Use the bulk_uuid to determine the operation status of your request.

1
2
3
4
5
6
7
8
9
10
11
{
    "bulk_uuid": "fbfca270-7a90-4c4e-9f32-d6cf3728cdc7",
    "request_items": [
        {
            "id": 0,
            "data_hash": null,
            "status": "accepted"
        }
    ],
    "errors": false
}