> 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/developer-guides/api-intro/integrations-api.md).

# Integrations API

Connect your data platform to Immuta using the integrations API

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

## [Getting started guide](/saas/developer-guides/api-intro/integrations-api/getting-started.md)

This task-based guide includes end-to-end instructions for implementing your integration - from configuring your integration to mapping your users into Immuta so that they can access policy-enforced data. A basic request and payload example is provided for configuring each integration.

## [How-to guides](/saas/developer-guides/api-intro/integrations-api/how-to-guides.md)

These guides provide step-by-step instructions for creating and managing your integration and include configuration setting examples that vary in complexity.

* [Amazon Redshift Spectrum integration guide](/saas/developer-guides/api-intro/integrations-api/how-to-guides/configure-an-amazon-redshift-spectrum-integration.md)
* [Amazon S3 integration guide](/saas/developer-guides/api-intro/integrations-api/how-to-guides/s3-api.md)
* [Azure Synapse Analytics integration guide](/saas/developer-guides/api-intro/integrations-api/how-to-guides/synapse-api.md)
* [Google BigQuery integration guide](/saas/developer-guides/api-intro/integrations-api/how-to-guides/bigquery-api.md)

## [Reference guides](/saas/developer-guides/api-intro/integrations-api/reference-guides.md)

These guides define request and body parameters, response schema, and common error messages.

* [Integrations API endpoints](/saas/developer-guides/api-intro/integrations-api/reference-guides/integrations-api.md)
* [Integrations API payload](/saas/developer-guides/api-intro/integrations-api/reference-guides/integration-configuration-payload.md)
* [Response schema](/saas/developer-guides/api-intro/integrations-api/reference-guides/response-schema.md)
* [HTTP status codes and error messages](/saas/developer-guides/api-intro/integrations-api/reference-guides/status-codes.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 by asking a question.

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

```
GET https://documentation.immuta.com/saas/developer-guides/api-intro/integrations-api.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.