# Reference Guides

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

## [Integrations API endpoints](/saas/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](/saas/developer-guides/api-intro/integrations-api/reference-guides/integration-configuration-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](/saas/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](/saas/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: 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:

```
GET https://documentation.immuta.com/saas/developer-guides/api-intro/integrations-api/reference-guides.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.