# Unlock Coverage Set

Once you are finished working in a coverage set, you should release the lock so that other users can access it if desired.  The call is very similar to ‘lock coverage set’, except that the command in the header is ‘unlock’ instead of ‘lock’.

&#x20;

<figure><img src="https://2948796384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LmzGprckLqwd5v6bs6m%2Fuploads%2Fp6BlVrxSinU6PD6zMI36%2Fimage.png?alt=media&#x26;token=753da27f-5a76-4391-8b0b-ee36a70db7c2" alt=""><figcaption><p>Unlock coverage set API call</p></figcaption></figure>

&#x20;

&#x20;The body of the call is the same as in the ‘lock’ call.

&#x20;

```
{
    "context": {
        "user": "mbj_test",
        "password": "xxxx",
        "project": {
            "name": "imp_payments_demo",
            "version": "1.0"
        }
    }
}
```

&#x20;

The return message will show the lock attributes removed from the coverage set (highlighted below).

&#x20;

<figure><img src="https://2948796384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LmzGprckLqwd5v6bs6m%2Fuploads%2FWjDTQ7WLdzPBvTPamOuH%2Fimage.png?alt=media&#x26;token=9605ee38-4c45-4799-b698-7d863b8d424c" alt=""><figcaption><p>Return message showing lock removed</p></figcaption></figure>

&#x20;

When viewed in TDO, the ‘locked by’ column is now blank for this coverage set (api\_demo\_coverage 1.0), showing that the lock has been removed.

&#x20;

<figure><img src="https://2948796384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LmzGprckLqwd5v6bs6m%2Fuploads%2Fi3HWN2F3LHbRuWEr3gNa%2Fimage.png?alt=media&#x26;token=9507d9a6-9585-473a-a089-20036b40371b" alt=""><figcaption><p>TDO screen showing lock removed</p></figcaption></figure>
