> For the complete documentation index, see [llms.txt](https://api.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api.dataloy.com/api-release-8.25/dataloy-rest-api/master-data-objects.md).

# Master data Objects

It is possible to activate and deactivate any Master Data object. A new property has been added for this purpose, **isObjectActive.**

To deactivate an object the following JSON has to be used in the PUT method:

<table data-header-hidden><thead><tr><th></th></tr></thead><tbody><tr><td><pre><code>{
	"isObjectActive": false
}
</code></pre></td></tr></tbody></table>

\
To activate an object the following JSON has to be used in the PUT method:

<table data-header-hidden><thead><tr><th></th></tr></thead><tbody><tr><td><pre><code>{
	"isObjectActive": true
}
</code></pre></td></tr></tbody></table>

Master Data objects has to be deactivated before they can be deleted.

{% hint style="info" %}
Deactivated objects are not included in standard Master Data list query results. To work with these objects:

#### Retrieving Deactivated Objects

* **Via List Query**: To retrieve deactivated objects in a list query, add the filter parameter `isObjectActive(EQ)false` to your request.
* **Via Direct Access**: Individual deactivated objects remain accessible by their unique key, regardless of activation status.

#### Example using BusinessPartner master data object

```
// Standard query - returns only active business partners
GET /BusinessPartner

// Query deactivated business partners
GET /BusinessPartner?filter=isObjectActive(EQ)false

// Retrieving specific deactivated business partner by key
GET /BusinessPartner/{objectKey}
```

{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://api.dataloy.com/api-release-8.25/dataloy-rest-api/master-data-objects.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.