- Send API: text, photo/GIF, audio, video, stickers, reactions, quick replies, generic and button templates, uploaded assets and published posts
- Private replies to comments and messages tagged for human agents beyond the standard window
- Welcome-message flows and ice breakers to start conversations; conversation and message retrieval routes
- 42 routes (13 read-only) on graph.instagram.com, documented in the AI integration guide (llms.txt)
Instagram Messaging API Connector
Meta's Instagram API on graph.instagram.com for professional accounts — the Send API for DMs (text, media, stickers, reactions, quick replies, templates, private replies), welcome-message flows, ice breakers and persistent menu — registered in Apivom Atlas with your own Instagram token for teams that automate Instagram conversations.
What you can do
Use cases
- Answer DMs with structure — Reply to Instagram messages with quick replies and button templates so customers pick an option instead of typing, and escalate to a person with the human-agent tag.
- Turn comments into conversations — Use private replies to move a question asked under a post into the customer's DMs, with the conversation logged per tenant.
The Instagram API with Instagram Login lets a professional account handle its direct messages programmatically on graph.instagram.com. The Send API covers everything a support or sales conversation needs — text, photos and GIFs, audio, video, stickers, reactions, quick replies, generic and button templates, sending an uploaded asset or an already published post, and private replies that answer a public comment in DM. The human-agent tag extends the reply window for a person taking over from automation. Around the conversation sit the welcome-message flows and ice breakers that open a chat with suggested questions, plus routes to read conversations and messages. Apivom Atlas catalogues 42 of these routes with the Meta credential contract, per-tenant logging and the AI integration guide (llms.txt). No Apivom product workflow handles Instagram DMs today; the connector is available for tenants automating Instagram conversations from their own tooling, and a product workflow — for example an assistant on Instagram alongside WhatsApp — is scoped per customer.
A Meta Graph API access token — a System User token from your Meta Business portfolio is the stable choice — with the permissions this API needs, sent as Bearer on every call. Tokens are encrypted in your Iris tenant when stored; Apivom Atlas forwards and logs the call and stores nothing.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
Is this the same as the Instagram Graph connector?
No. This connector is the messaging surface on graph.instagram.com (DMs, flows, menus). The separate Instagram Graph connector on graph.facebook.com covers Page-token lookup and Reels publishing for Instagram accounts linked to a Facebook Page.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.