ApivomApivom
Get Demo

Instagram Graph API (Reels Publishing) Connector

The Instagram surface of Meta's Graph API on graph.facebook.com for business and creator accounts linked to a Facebook Page — Page-token lookup and the Reels publishing flow (upload to an IG container, poll container status, publish) — registered in Apivom Atlas with your own Meta token.

What you can do

  • Page tokens: list the Pages you manage with their access tokens, or fetch one Page's token to reach its linked Instagram account
  • Reels publishing: upload a Reel to an Instagram media container, poll the container status until finished, publish
  • Five routes (three read-only) on graph.facebook.com, documented in the AI integration guide (llms.txt)
  • For Instagram DMs use the separate Instagram Messaging connector on graph.instagram.com

Use cases

  • Schedule Reels from your own pipeline — Create the container with a hosted video URL, wait for the status to be finished and publish at the planned time, with Meta's responses logged per tenant.
  • One token path for Page and Instagram — Resolve the Page token once and use it for both Facebook Page actions and the linked Instagram account.

Instagram business and creator accounts that are linked to a Facebook Page are managed through Meta's main Graph host, graph.facebook.com, using the Page's access token. This connector catalogues the slice needed for publishing Reels there: list the Pages the authorised user manages with their tokens, or fetch one Page's token; create an Instagram media container for the Reel by giving Meta the video URL; poll the container's status code until processing finishes; and publish it to the account. Apivom Atlas registers these five routes with the Meta credential contract, per-tenant logging and the AI integration guide (llms.txt). Apivom Mars, the marketing product, publishes Instagram carousels, single images and stories through Meta's content-publishing flow directly, but this specific Reels route set is not part of a product workflow today — the connector is available to tenants that automate Instagram video from their own tooling, and a product workflow is scoped per customer.

Authentication

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.

Why does Instagram publishing go through graph.facebook.com?

Because business and creator accounts linked to a Facebook Page are addressed through the Page's token on Meta's main Graph host. Messaging for those accounts lives on graph.instagram.com, which Atlas registers as the Instagram Messaging connector.

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.