# Delete Business Rule

This call is sent as a DELETE call.  You can only delete one rule at a time using this call, as the rule ID is part of the header.

 

The body of this call is the same as the details calls, only containing the context.

 

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

 

For this call, we are sending the ID for the third rule in the ‘Get All Details’ call illustrated earlier.  The return message simply shows a successful call.

  

<figure><img src="/files/flhFpTBxxw4t2lvN5Y9i" alt=""><figcaption><p>Results of delete rule API</p></figcaption></figure>

&#x20; Viewing the business rules in TDO after this call is sent, you can see that the third business rule is no longer present.

&#x20;

<figure><img src="/files/ctG4xCptOShjIK8ROq0P" alt=""><figcaption><p>Rule deleted from TDO</p></figcaption></figure>


---

# 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/business-rule-apis/delete-business-rule.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.