- Page tokens: list the Pages your user manages with their access tokens, or fetch one Page's token
- Reels publishing: create the Reel container, check the upload-session status, publish — upload itself runs through the Resumable Upload connector
- Five routes (three read-only) on graph.facebook.com, documented in the AI integration guide (llms.txt)
- Pairs with the Facebook Resumable Upload connector for local or hosted video files
Facebook Graph API (Pages & Reels) Connector
The Facebook Graph API surface for Pages you manage — list Page access tokens, fetch a specific Page token, and publish Reels in Meta's three-step flow (create, upload, publish) — registered in Apivom Atlas with your own Meta token for marketing teams that automate Page video publishing.
What you can do
Use cases
- Automate Reels for a Page — Create the container, hand the file to the upload connector, confirm the session status and publish — all from your scheduler, with Meta's responses logged per tenant.
- Resolve Page tokens once — List the Pages a user manages and store the right Page access token for the connection instead of copying tokens by hand.
This connector covers the slice of Meta's Graph API that a marketing team needs to publish Reels to a Facebook Page: first the token routes — list the Pages the authorised user manages, each with its Page access token, or fetch the token of one Page — then Meta's three-step Reels flow. Publishing a Reel means creating a video container on the Page (step 1), uploading the file to Meta's upload host (step 2, catalogued separately as the Facebook Resumable Upload connector), optionally polling the upload-session status (step 3) and finally publishing with title and description (step 4). 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 photo and text posts to Facebook Pages and reads their insights through Meta's Graph API directly — but the Reels routes catalogued here are not part of that workflow; they are available to tenants automating Page video from their own tooling, and a product workflow 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.
Why is the upload step a separate connector?
Meta serves Reels uploads from a different host (rupload.facebook.com) with its own headers for local and hosted files. Atlas registers one connector per host, so the create/status/publish steps live here and the upload steps in Facebook Resumable Upload.
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.