> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/saas/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/saas/~/changes/l3NnvynMHxi6VvqRtJhK/developer-guides/api-intro.md).

# The Immuta API

{% hint style="warning" %}
Any endpoints or attributes that are not documented are for internal purposes and should not be used.
{% endhint %}

## [Integrations API](/saas/~/changes/l3NnvynMHxi6VvqRtJhK/developer-guides/api-intro/integrations-api.md)

The integrations API allows you to integrate your remote data platform with Immuta so that Immuta can manage and enforce access controls on your data.

## [Enhanced Onboarding API](/saas/~/changes/l3NnvynMHxi6VvqRtJhK/developer-guides/api-intro/enhanced-onboarding-api.md)

The data API is used for enhanced onboarding and allows you to integrate both your remote data platform and its tables with Immuta in one action with one set of credentials. Then Immuta can manage and enforce access controls on your data.

## [Version 2 Immuta API](/saas/~/changes/l3NnvynMHxi6VvqRtJhK/developer-guides/api-intro/immuta-v2-api.md)

Version 2 of the Immuta API allows data engineers to manage their data sources, projects, and policies as code, providing a way to track, approve, and easily update data sources and their associated policies.

The benefits of the V2 API are outlined below:

* **Reduces complexity**: The data source API has been simplified to only require the connection information in most instances and one endpoint for all database technologies.
* **Maintains less state**: Whether updating or creating, the same endpoint is used, and the same data is passed. No IDs are required, so no additional state is required.
* **Requires fewer steps**: Only an API key is required; no additional authentication step is required before using the API.
* **Integrates with Git**: Define data sources and policies in files that can be tracked in Git and easily pushed to Immuta. Both JSON and YAML are supported for more flexibility. (For example, use YAML to add comments in files.)

## [Version 1 Immuta API](/saas/~/changes/l3NnvynMHxi6VvqRtJhK/developer-guides/api-intro/immuta-v1-api.md)

Version 1 of the Immuta API is still supported and can be accessed through the Immuta CLI. However, users are encouraged to use Version 2 of Immuta's API because of all the benefits outlined above.


---

# 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://documentation.immuta.com/saas/~/changes/l3NnvynMHxi6VvqRtJhK/developer-guides/api-intro.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.