# Prolong request lock


```
PUT 
https://api.apify.com/v2/request-queues/:queueId/requests/:requestId/lock
```


Prolongs request lock. The request lock can be prolonged only by the client that has locked it using .

## Request

### Path Parameters

* **queueId** string required

  Queue ID or `username~queue-name`.

  **Example:** `WkzbQMuFYuamGv3YF`

  **requestId** string required

  Request ID.

  **Example:** `xpsmkDlspokDSmklS`

### Query Parameters

* **lockSecs** double required

  For how long second request will be locked.

  **Example:** `60`

  **clientKey** string

  A unique identifier of the client accessing the request queue. It must be a string between 1 and 32 characters long. This identifier is used to for locking and unlocking requests. You can delete or prolong lock only for requests that were locked by by same client key or from the same Actor run.

  **Example:** `client-abc`

  **forefront** string

  Determines if request should be added to the head of the queue or to the end after lock expires.

  **Example:** `false`

<!-- -->

### Status 200

**Response Headers**




```
{
  "data": {
    "lockExpiresAt": "2022-01-01T00:00:00.000Z"
  }
}
```


**Schema**

* **data** object required

  Information about a request lock.

  * **lockExpiresAt** string\<date-time> required

    The timestamp when the lock expires.

    **Example:** `2022-01-01T00:00:00.000Z`

### Status 400

Bad request - invalid input parameters or request body.


```
{
  "error": {
    "type": "invalid-input",
    "message": "Invalid input: The request body contains invalid data."
  }
}
```


**Schema**

* **error** object required

  * **type** string required\
    **Example:** `run-failed`
  * **message** string required\
    **Example:** `Actor run did not succeed (run ID: 55uatRrZib4xbZs, status: FAILED)`