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

# Delete request lock

`DELETE /v2/request-queues/{queueId}/requests/{requestId}/lock`

Deletes a request lock. The request lock can be deleted only by the client
that has locked it using [Get and lock head
operation](#/request-queue-head-lock-post).

The clientKey identifier is used for locking and unlocking requests.
You can delete or prolong the lock only for requests that were locked by the same client key or from the same Actor run.

## Path parameters

- `queueId` string, required
- `requestId` string, required

## Query parameters

- `clientKey` string
- `forefront` string

## Response `204`

No content

## 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.
- `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)