For the complete documentation index, see llms.txt. This page is also available as Markdown.

Integrating with Our Platform API

indigo.ai's platform exposes a GraphQL API for full programmatic access to your AI Agents and a small set of REST endpoints for operational integrations. Whether you're looking to automate workflows, extract data for analysis, or enhance integrations across your tech stack, our APIs provide all the tools you need to extend your virtual assistant's capabilities.

The two surfaces complement each other:

  • GraphQL API β€” flexible, schema-driven access to conversations, messages, users, and configuration. Best for custom integrations, data extraction, and bulk operations.

  • REST endpoints β€” purpose-built for specific operational use cases:

For a primer on how indigo.ai groups messages into chats and conversations, see Sessions.

πŸ”§ What You Can Do with the API

Our APIs support a wide range of use cases, including:

  • Data Extraction: Retrieve detailed records of conversations, agent responses, and user feedback to integrate with internal systems.

  • Bulk Updates: Automate large-scale updates to your AI Agents data sources, like knowledge base articles and user profiles.

  • Custom Analytics: Build personalized dashboards using real-time chat, agent, and user data.

πŸ“˜ API Documentation & Endpoint

πŸ”— Documentation

You can find the latest technical details and schema definitions here: Indigo.ai API docs.

The core API is GraphQL. You can access it via a dedicated GraphQL client or any standard HTTP client by following the appropriate format. Specific REST endpoints are documented in their own pages β€” see Non-Conversational Triggers and the Analytics REST API.

🌐 API Endpoint

All API requests should be directed to: https://platform.indigo.ai/graphql

Use the POST HTTP method for all calls.

πŸ” Authentication

Authentication is handled via personal access tokens. All requests must include an Authorization header in the following format:

Pagination Model

The API implements the Relay-style cursor-based pagination model. Each query response includes endCursor and hasNextPage fields within the pageInfo object, enabling efficient traversal of large datasets through sequential requests.

Example Use Cases

Here are practical examples of how you can leverage our APIs.

πŸ“€ Get All Chats from a Workspace

Use the conversations query to retrieve all chat sessions:

Output structure

Once the query is executed with the required parameters, the API returns a response structured as follows:

πŸ’¬ Get All Messages from a Chat

Once you have a conversationId, use the messages query to extract every message:

Output structure

Messages are returned in reverse chronological order (newest first). To navigate through paginated results, use the before argument in the same way you would use after.

Within each message object:

  • The sender field indicates the origin of the message. If the value is null, the message was sent by the virtual assistant; otherwise, it contains an object representing the user (bot_user.id).

  • The actual message content is located in the content field.

πŸ‘₯ Get All Users in a Workspace

Use the userRoles query to retrieve users and their roles:

Output structure

Last updated

Was this helpful?