---
metadata:
  - name: generator
    content: Diplodoc Platform v5.44.0
alternate:
  - https://yandex.ru/dev/disk-api/doc/en/reference/operations.md
  - https://yandex.ru/dev/disk-api/doc/ru/reference/operations.md
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.ru/dev/disk-api/doc/en/llms.txt

# Operation status

[Copying](https://yandex.ru/dev/disk-api/doc/en/reference/copy.md), [moving](https://yandex.ru/dev/disk-api/doc/en/reference/move.md), and [deleting](https://yandex.ru/dev/disk-api/doc/en/reference/delete.md) non-empty folders can take some time. The response to each of these requests contains the URL of the operation status. Below is a description of the URL and status description formats.


## Request format {#format}

Use the GET method to send a request for operation status. The URL for this request (including the ID) is returned in the response if the operation may take time (for example, when [copying](https://yandex.ru/dev/disk-api/doc/en/reference/copy.md)).

```
https://cloud-api.yandex.net/v1/disk/operations/<operation ID>
```


## Response format {#response}

If the request is processed without errors, the API returns the `200 OK` code. The response body contains an operation status within the [Operation](https://yandex.ru/dev/disk-api/doc/en/reference/response-objects.md#operation) object.

Sample response:

```json
{
  "status":"success"
}
```
<!-- source: en/_includes/reference/response-objects/id-link/operation-table.md -->


#|
|| **Element** | **Description**||
|| `status` | Operation status. Possible values:

- `success` — Operation successfully completed.
- `failed` — Operation failed. Try repeating the original copy, move, or delete request.
- `in-progress` — Operation has started but not finished yet.||
   |#
<!-- endsource: en/_includes/reference/response-objects/id-link/operation-table.md -->