Yandex.Cloud services support idempotency. An idempotent operation returns the same result for multiple calls.

By default, some operations in the API are not idempotent (for example, operations that change the state of resources). To make them work in an idempotent manner, specify the Idempotency-Key header in requests. The header must contain the UUID. Generate the UUIDs for each operation separately.

Idempotency-Key: <UUID>

We recommended using a v4 UUID.

When the service receives your request with the Idempotency-Key header, it checks whether an operation with this UUID has already been created. If it has, the server returns the Operation object with this operation's current status. If no operation with this UUID is found, the service starts performing it.


The examples below show how to use the idempotency mechanism when working with the Yandex API.Clouds.

Example 1

Let's say you send a start VM request:

POST /compute/v1/instances/e0m97h0gbq0foeuis03:start
Idempotency-Key: c1700de3-b8cb-4d8a-9990-e4ebf052e9aa

If you send this request again with the same Idempotency-Key, the server will not restart the VM. Instead, the server returns the Operation object with the status of the operation that was called as a result of the first request.

Example 2

This example illustrates a situation in which a race condition occurs.

Assume that a request was sent from a client to stop a running VM. No Idempotency-Key header is specified.

The connection failed when sending the request and the client did not receive a response from the server. The VM was stopped, but because no response was received, the client does not know the operation status.

At the same time, another client restarts this VM (for example, through the UI console).

But when the first client gets access to the internet, it re-sends its stop VM request. Since there is no Idempotency-Key header, the VM that the second client needs will be stopped.

If the first client had passed the Idempotency-Key in its stop VM requests, the VM would not have been stopped when the request was resent.