- Upload a local Reel: stream the video bytes to the container created in the Graph API with offset and file-size headers
- Upload a hosted Reel: give Meta a public file URL and let it fetch the video server-side
- Two write routes on rupload.facebook.com, documented in the AI integration guide (llms.txt)
- Completes the create → upload → status → publish sequence with the Facebook Graph (Pages & Reels) connector
Facebook Resumable Upload API Connector
Meta's Resumable Upload host (rupload.facebook.com) for Reels — upload a local video file in chunks or hand Meta a hosted file URL to fetch — registered in Apivom Atlas as the step-2 companion of the Facebook Graph Reels publishing flow, with your own Meta token.
What you can do
Use cases
- Publish large Reels reliably — Upload multi-hundred-megabyte videos in resumable chunks from your pipeline, then publish the container once Meta reports the upload complete.
- Skip the download–upload round trip — If your videos already sit on a CDN, give Meta the URL and let it fetch the file instead of moving the bytes through your servers.
Meta separates the heavy lifting of video publishing onto a dedicated host: once a Reel container exists on a Facebook Page, the video itself is sent to rupload.facebook.com, not to the Graph API. Two methods exist. For a local file, the bytes are streamed to the container's upload URL with headers for the current offset and total size, so large videos can be resumed if the connection drops. For a file that is already online, you pass its public URL and Meta downloads it on its side. Apivom Atlas registers both routes with the Meta credential contract, per-tenant logging and the AI integration guide (llms.txt); because the upload is a write with no read-only counterpart, both routes are flagged as mutations. This connector is only useful together with the Facebook Graph (Pages & Reels) connector, which creates the container before and publishes after. No Apivom product workflow uploads Facebook Reels today; the pair is 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.
Do I need this connector on its own?
No — it only makes sense as step 2 of the Reels flow. Create the container with the Facebook Graph (Pages & Reels) connector, upload here, then check status and publish there again.
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.