Quickstart
Make your first call, then put your newest reel to work. A few minutes, start to finish.
Authentication
API keys, scopes, expiry, and how to keep a key safe.
Instagram's rules
The platform rules every automation runs inside, stated once and plainly.
API reference
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, and the automation is live before the first comment lands. See the recipe.
- Report where you already look. Pull automation stats into your own dashboard, sheet or Slack digest. See the recipe.
- 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 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 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
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.