> 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/sdk.md).

# SDK

Use the SDKs when an application, notebook, or automation should call Data Product APIs without manually building every HTTP request.

Both SDKs wrap the main API groups into a single `VulcanClient`.

## Available SDKs

<table><thead><tr><th width="151.52197265625">SDK</th><th>Use when</th></tr></thead><tbody><tr><td><a href="/pages/h6YVl9Uc8CWxTQTgrwyR">Python SDK</a></td><td>Python applications, notebooks, and automations need typed API access.</td></tr><tr><td><a href="/pages/WA51HwaxgTZthsFdcNoj">TypeScript SDK</a></td><td>Node.js or TypeScript applications need typed API access.</td></tr></tbody></table>

## What the SDKs cover

Both SDKs support these API groups:

* Metadata
* Query
* Activity
* Data quality
* Perspectives
* Notifications and followers

## Base URL pattern

The SDKs build the Data Product API base URL from the same values used in raw HTTP requests:

```
https://{fqdn}/vulcan/tenants/{tenant}/data-products/{tenant}-{data-product-name}/api/v1
```

## Choose an SDK

Choose Python when your workload runs in notebooks, jobs, or backend automation.

Choose TypeScript when your workload runs in Node.js services, backend apps, or TypeScript tooling.

***

## Reference

For full installation instructions, available methods, code examples, error handling, and cancellation support, see [SDKs](/concepts/foundations/activation/apis/getting-started/sdks.md) in Concepts.


---

# 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/sdk.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.