> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/latest/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/latest/developer-guides/api-intro/integrations-api/reference-guides.md).

# Reference Guides

The reference guides in this section define the integrations API endpoints, request and body parameters, and response schema.

## [Integrations API endpoints](/latest/developer-guides/api-intro/integrations-api/reference-guides/integrations-api.md)

The integrations API endpoints allow you to create, update, get, and delete integrations and generate scripts to run in your data platform to manually set up or remove Immuta-managed resources.

Consult this guide for endpoint descriptions and examples.

## [Integrations API payloads and objects](/latest/developer-guides/api-intro/integrations-api/reference-guides/payload.md)

The integrations API request payloads accept JSON or YAML format, and each integration has parameters and objects specific to the data platform.

Consult this guide for parameter value types, requirements, definitions, and accepted values.

## [Response schema](/latest/developer-guides/api-intro/integrations-api/reference-guides/response-schema.md)

The response returns the status of the integration configuration in JSON format.

Consult this guide for response schema definitions and integration state definitions.

## [HTTP status codes and error messages](/latest/developer-guides/api-intro/integrations-api/reference-guides/status-codes.md)

The integrations API uses standard HTTP status codes. Status codes specific to the integrations API are described in this reference guide.

Consult this guide for a list of status codes, integration states, common error messages, and troubleshooting guidance.


---

# 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/latest/developer-guides/api-intro/integrations-api/reference-guides.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.