> ## Documentation Index
> Fetch the complete documentation index at: https://docs.indm.social/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Build, launch and read Instagram comment-to-DM automations from your own code.

Your posts already start conversations. The inDM API lets your own code turn them into DMs: find the reel you just published, build an automation on it, set it live, and read how it's doing. The same automations the app builds, run by a script, a content calendar or a dashboard of your own.

> [card] [Quickstart](https://docs.indm.social/quickstart.md)
>
> Make your first call, then put your newest reel to work. A few minutes, start to finish.

> [card] [Authentication](https://docs.indm.social/authentication.md)
>
> API keys, scopes, expiry, and how to keep a key safe.

> [card] [Instagram's rules](https://docs.indm.social/instagram-rules.md)
>
> The platform rules every automation runs inside, stated once and plainly.

> [card] [API reference](https://docs.indm.social/api-reference/introduction.md)
>
> Every endpoint, with a playground to try it against your workspace.

## What you can build

* **Launch with the post.** Your publishing tool posts a reel, calls [Refresh content](https://docs.indm.social/api-reference/accounts/refresh-account.md), and the automation is live before the first comment lands. See the [recipe](https://docs.indm.social/recipes/refresh-then-automate.md).
* **Report where you already look.** Pull [automation stats](https://docs.indm.social/api-reference/automations/get-automation-stats.md) into your own dashboard, sheet or Slack digest. See the [recipe](https://docs.indm.social/recipes/read-automation-results.md).
* **Run many accounts the same way.** Agencies keep one key per client workspace and roll the same setup across every account.
* **Check copy before it ships.** [Validate an automation](https://docs.indm.social/api-reference/automations/validate-automation.md) catches a label Instagram would cut off or a DM that promises a link it never delivers.

## What it never does

The API configures automations and reports on them. It doesn't send.

* **No DM, broadcast or public reply leaves by this path.** Your automations run on inDM's own engine, answering comments as they arrive, whether or not your code is running.
* **Every automation starts as a draft.** [Set automation status](https://docs.indm.social/api-reference/automations/set-automation-status.md) is the one call that changes what people on Instagram receive.
* **Nothing about the people who comment comes back.** You get counts and your own setup. No handles, no messages, no email addresses.

## The basics

| | |
| - | - |
| Base URL | `https://api.indm.social/v1` |
| Authentication | `Authorization: Bearer indm_...` with a key from **Settings → API keys** |
| Format | JSON in, JSON out, `snake_case` field names |
| Plans | Works on every inDM plan. The plan decides what a workspace can build, exactly as it does in the app. |

> [!NOTE]
>
> Keys are server-side secrets. The API sends no CORS headers, so a browser can't call it, and a key in front-end code or a mobile app is a key anyone can read. Call the API from your server.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.