---
title: "Delete requests"
method: DELETE
path: "/v2/request-queues/{queueId}/requests/batch"
tags: ["Storage/Request queues"]
---

# Delete requests

`DELETE /v2/request-queues/{queueId}/requests/batch`

Batch-deletes given requests from the queue. The number of requests in a
batch is limited to 25. The response contains an array of unprocessed and
processed requests.
If any delete operation fails because the request queue rate limit is
exceeded or an internal failure occurs,
the failed request is returned in the `unprocessedRequests` response
parameter.
You can re-send these delete requests. It is recommended to use an
exponential backoff algorithm for these retries.
Each request is identified by its ID or uniqueKey parameter. You can use
either of them to identify the request.

## Path parameters

- `queueId` string, required

## Query parameters

- `clientKey` string

## Headers

- `Content-Type` 'application/json', required

## Request body

- RequestDraftDelete[]
  - union — A request that should be deleted.
    - RequestDraftDeleteById — A request that should be deleted, identified by its ID.
      - `id` string, required — A unique identifier assigned to the request.
      - `uniqueKey` string — A unique key used for request de-duplication. Requests with the same unique key are considered identical.
    - RequestDraftDeleteByUniqueKey — A request that should be deleted, identified by its unique key.
      - `id` string — A unique identifier assigned to the request.
      - `uniqueKey` string, required — A unique key used for request de-duplication. Requests with the same unique key are considered identical.

## Response `200`

- BatchDeleteResponse — Response containing the result of a batch delete operation.
  - `data` BatchDeleteResult, required — Result of a batch delete operation containing successfully deleted and failed requests.
    - `processedRequests` DeletedRequest[], required — Requests that were successfully deleted from the request queue.
      - union — Confirmation of a request that was successfully deleted from a request queue.
        - DeletedRequestById — Confirmation of a request that was successfully deleted, identified by its ID.
          - `uniqueKey` string — A unique key used for request de-duplication. Requests with the same unique key are considered identical.
          - `id` string, required — A unique identifier assigned to the request.
        - DeletedRequestByUniqueKey — Confirmation of a request that was successfully deleted, identified by its unique key.
          - `uniqueKey` string, required — A unique key used for request de-duplication. Requests with the same unique key are considered identical.
          - `id` string — A unique identifier assigned to the request.
    - `unprocessedRequests` RequestDraft[], required — Requests that failed to be deleted and can be retried.
      - `id` string — A unique identifier assigned to the request.
      - `uniqueKey` string, required — A unique key used for request de-duplication. Requests with the same unique key are considered identical.
      - `url` string, required — The URL of the request.
      - `method` 'GET' | 'HEAD' | 'POST' | 'PUT' | 'DELETE' | 'CONNECT' | 'OPTIONS' | 'TRACE' | 'PATCH'

## Other responses

- `400` — Bad request - invalid input parameters or request body.
- `401` — Unauthorized - authentication required or invalid token.
- `403` — Forbidden - insufficient permissions to perform this action.
- `404` — Not found - the requested resource does not exist.
- `405` — Method not allowed.
- `413` — Payload too large - the request body exceeds the size limit.
- `415` — Unsupported media type - the Content-Encoding of the request is not supported.
- `429` — Too many requests - rate limit exceeded.

---

[API](https://skmtc.net/apify/apis/apify-api.md) · [All operations](https://skmtc.net/apify/apis/apify-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/apify/apify-api/versions/01a71794279b/schema)