# Delete Coverage Set

This call will delete the coverage set from the project.  The header is the same as the ‘get coverage set details’ API, except that it is sent as a ‘DELETE’ command.  It is recommended that you confirm the ID of the set you are deleting before you run this API as it cannot be reversed.

&#x20;

<figure><img src="/files/8Ghk4JP40QqnQu67qEzv" alt=""><figcaption><p>Delete coverage set API </p></figcaption></figure>

&#x20;The body is the same as the simple body API calls; just credentials and project information.

&#x20;

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

&#x20;

This API will delete the ‘api\_demo\_coverage 1.0’ coverage set.  The return message is very simple, only showing a result of ‘true’.

&#x20;&#x20;

<figure><img src="/files/UcjkSyPZIFw6wadnVcSr" alt=""><figcaption><p>Delete coverage set return message</p></figcaption></figure>

&#x20;

In TDO, the coverage set main page now shows that ‘api\_demo\_coverage 1.0’ no longer exists.

&#x20;

<figure><img src="/files/l2jjSGiTBS89l15pt3Vg" alt=""><figcaption><p>TDO coverage set listing showing target set removed</p></figcaption></figure>

Remember only users with administrator credentials can delete objects in TDO.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/api-guide/coverage-set-apis/delete-coverage-set.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
