> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/consume/activate/apis/collection.md).

# Collection

Gives you ready-to-run requests so you can pull governed data into your app without building calls from scratch.

Because the collection already covers GraphQL, semantic queries, metadata, activity, quality, and other operational APIs, you can confirm a request works in Postman before committing it to your code.

## Before you start

Before importing the collection:

1. Generate a [DataOS API token](/consume/get-started/readme-1.md#get-a-dataos-api-token).
2. Open the target Data Product.
3. Make sure Postman is installed.

## Import the collection

{% stepper %}
{% step %}
Open the Data Product, then select **Activate → APIs** to open the **Build on the APIs** page.

Under **Postman collection**, select **Download**.

![Build on the APIs page with the Postman collection download](/files/m3xAKGtw7QJVHHQuBxjZ)
{% endstep %}

{% step %}
Import the collection into Postman.

{% file src="/files/Z6SHQVeECgEK0NWUtmQy" %}
Example Postman collection
{% endfile %}

After import, Postman shows the collection named **Vulcan API — \[your data product name]** with six top-level folders: **Discover**, **Query**, **GraphQL**, **Perspectives**, **Engagement**, and **Quality & Activity**.
{% endstep %}

{% step %}
Set the required values in Postman before sending a request.

<table><thead><tr><th width="131.5750732421875">Value</th><th>What to use</th></tr></thead><tbody><tr><td><code>baseUrl</code></td><td>The Data Product base URL from <strong>Connect → APIs</strong></td></tr><tr><td><code>token</code></td><td>Your <a href="/pages/7rh6mFCr0rhl6vO76XjW#get-a-dataos-api-token">DataOS API token</a></td></tr></tbody></table>

Set `baseUrl` in the collection Variables tab.

Set the token as a Bearer token in the collection Authorization tab.
{% endstep %}

{% step %}
Open the request you need, then send it from Postman.

Start with **Quality & Activity → Health → Liveness Probe** to confirm the base URL works.

Then run the API request you need from the relevant folder.
{% endstep %}
{% endstepper %}

## What the collection includes

So you can jump straight to the request you need, the collection groups requests into six top-level folders:

* **Discover** — metadata, semantic schema, and BI export downloads (Power BI, Tableau)
* **Query** — Semantic REST, Semantic SQL, Semantic Metrics, Data Model Query, query result polling, and usage analytics
* **GraphQL** — Semantic GraphQL queries
* **Perspectives** — create, list, fetch, update, and delete saved query views
* **Engagement** — followers and notifications
* **Quality & Activity** — data quality rules, deployment plans, run history, and health probes

## Next step

Use [SDK](/consume/activate/apis/sdk.md) when you want typed clients instead of Postman.

***

## Reference

For full setup details, collection variable descriptions, async query workflow, environment management, and all API groups included in the collection, see [Postman collection in Concepts](/concepts/foundations/activation/apis/getting-started/postman-collection.md).


---

# 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 dynamically by asking a question.

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

```
GET https://v2.dataos.info/consume/activate/apis/collection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.