Log inStart Free Trial
easyCoexistence Official APIs

Facebook Reels API: publishing Reels to a Page

The Facebook Reels API publishes a Reel to a Page in three steps: POST /{page-id}/video_reels with upload_phase start returns a video_id, the video goes to rupload.facebook.com, and POST /{page-id}/video_reels with upload_phase finish and video_state PUBLISHED posts it. Meta's specification is a 9:16 video of 3 to 90 seconds, and a Page can publish 30 Reels through the API in 24 hours.

easyCoexistence posts videos to a Facebook Page as regular video posts with publish_facebook_post, from Claude, ChatGPT or your own code, beside text, links and photos.

30 a day

API-published Reels per Page within a 24-hour moving period, enforced on POST /{page_id}/video_reels.

3 to 90 s

Reel duration Meta accepts; a Reel published as a story on a Page cannot exceed 60 seconds.

540 x 960

Minimum Reel resolution; Meta recommends 1080 x 1920 pixels at a 9 x 16 aspect ratio.

29 days

Furthest ahead scheduled_publish_time can set a Reel, at least 10 minutes out, with video_state SCHEDULED.

1363128

Error code for a Reel whose duration Facebook does not support; Reels must run 3 to 90 seconds.

How does the Reels API publish a Reel?

In three steps across two hosts. The start and finish calls go to the Page's video_reels edge on graph.facebook.com, while the video itself goes to rupload.facebook.com, at the upload_url the start call returns. A status check on the video's ID between the upload and the finish shows whether Meta has the whole file and has processed it.

1StartPOST /{page-id}/video_reels, upload_phase start: returns video_id and upload_url
2UploadPOST to rupload.facebook.com with the bytes or a file_url header
3CheckGET /{video-id}?fields=status until processing completes
4FinishPOST /{page-id}/video_reels, upload_phase finish, video_state PUBLISHED

What video does a Reel need?

Meta publishes its Reels specifications in the Reels Publishing guide, and an upload that misses them on aspect ratio, resolution, duration or frame rate is refused with an error code of its own. A Reel meant for a Page story also has to stay within 60 seconds.

File.mp4 recommended
Aspect ratio9 x 16
Resolution1080 x 1920 recommended, 540 x 960 at least
Frame rate24 to 60 fps, fixed, progressive scan
Duration3 to 90 seconds
VideoH.264 or H.265 (VP9 and AV1 also supported), 4:2:0, closed GOP of 2 to 5 s
AudioAAC Low Complexity, 48 kHz, stereo, 128 kbps or more

How is the video uploaded?

With a POST to the upload_url on rupload.facebook.com, carrying the Page token in an Authorization: OAuth header. A file on your machine goes as the request body, with an offset header set to 0 and file_size set to its size in bytes. A file already online goes as a file_url header instead, and Meta fetches it; a successful upload returns success set to true.

  • file_url takes http or https addresses; URLs that need authentication are not supported.
  • The host has to let the facebookexternalhit/1.1 user agent fetch the file, since Meta rejects files on sites that block it in robots.txt.
  • Files on Meta's own CDN, such as fbcdn URLs, are rejected; Meta points to crossposting to reuse a video on another Page.
Uploading a hosted video
# <UPLOAD_URL> is the upload_url the start call returned
curl -X POST "<UPLOAD_URL>" \
  -H "Authorization: OAuth <PAGE_ACCESS_TOKEN>" \
  -H "file_url: https://example.com/reel.mp4"

How do you check a Reel's status?

With GET /{video-id}?fields=status on graph.facebook.com. The answer holds video_status, which reads uploading, upload_complete, processing, ready, upload_failed, expired or error, and one object per phase: uploading_phase with bytes_transfered, processing_phase with any error message, and publishing_phase with publish_status (draft, scheduled, published or error) and publish_time. Each phase's own status is not_started, in_progress, completed or error.

How is an interrupted upload resumed?

By sending the upload POST again with the offset header set to uploading_phase.bytes_transfered from a status check, the bytes Meta already has. An offset Meta does not accept returns OffsetInvalidError, a body that does not match the file's length returns PartialRequestError, and when uploading again does not work, Meta's advice is to start over from the first step.

What does the finish call take?

The video_id from the start call, upload_phase set to finish and video_state set to PUBLISHED, DRAFT or SCHEDULED. description carries the text and supports hashtags. title, place for a location Page and is_ai_generated, which discloses that the Reel was created or edited with AI, are optional. A scheduled Reel adds scheduled_publish_time, a UNIX timestamp more than 10 minutes and within 29 days ahead. Meta answers with success set to true.

How many Reels can a Page publish through the API?

30 within a 24-hour moving period. Meta enforces the cap on POST /{page_id}/video_reels when a Reel is published and recommends that apps enforce it themselves too, especially apps that let people schedule posts for later. Collaborator invitations have a cap of their own, 10 per Page per 24 hours, and the video_reels reference lists error 613, calls to this API have exceeded the rate limit.

Which permissions and Page task does it need?

A Page access token from someone who can perform the CREATE_CONTENT task on the Page, with pages_show_list, pages_read_engagement and pages_manage_posts granted through Facebook Login. Meta also asks apps to show the person a disclosure of how their Reels are used on Facebook, with options to control it, and to offer only the Public audience, since publishing to a Page has implicit public scope.

Which errors does the Reels API return?

Code 100 means a required parameter is missing, such as upload_phase, and Meta's message lists the missing ones. Four more codes refuse a video that falls outside the specifications:

  • 1363040: the aspect ratio is not supported; videos need to be between 16x9 and 9x16.
  • 1363127: the resolution is not supported; the minimum is 540 x 960 pixels.
  • 1363128: the duration is not supported; Reels run 3 to 90 seconds.
  • 1363129: the average frame rate is not supported; Reels need 24 to 60 frames per second.

How do you list a Page's Reels?

With GET /{page-id}/video_reels, which returns the Page's published Reels with their IDs, update times and descriptions. since and until narrow the list to dates given as today, yesterday, a UNIX timestamp or yyyy-mm-dd, with until later than since. Meta's feed reference points to this edge for the Reels published to a Page.

How do you publish a Reel through easyCoexistence?

Not as a Reel, today. publish_facebook_post sends videos to the Page's videos edge, as regular video posts, and easyCoexistence has no tool for the video_reels calls; Page tokens are not handed out, so the three steps cannot run from your own code on its connection either. Publish the Reel from Facebook or Meta Business Suite, or post the video as a regular video post.

Common mistakes

  • Sending the upload to graph.facebook.com. The video goes to rupload.facebook.com with an Authorization: OAuth header; only the start, finish and status calls use graph.facebook.com.
  • Hosting the file where Meta cannot fetch it. A file_url behind a login, on a site whose robots.txt blocks facebookexternalhit/1.1, or on fbcdn is rejected.
  • Starting over after an interrupted upload. Read the status first: uploading_phase.bytes_transfered is the offset to resume from, and a new session is the last resort.
  • Queueing more than 30 Reels for one Page in a day. Meta counts API-published Reels over a 24-hour moving period, so spread scheduled ones out.
Doing this with EasyCoexistence

It has no tool for the Reels API, so a Reel is published from Facebook or Meta Business Suite. US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.

easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.

Frequently asked questions

Can a Reel be published to a Facebook profile or group through the API?

No. Meta's Reels Publishing API publishes Reels to Facebook Pages, and crossposts them only to Pages.

Does publish_facebook_post publish Reels?

No. It posts text, links, photos and videos to the Page. A Reel takes the video_reels calls, which easyCoexistence's tools do not make.

How do I check a Reel for copyright matches?

Read GET /{video-id}?fields=copyright_check_information with pages_read_engagement. Meta runs the check at upload, it can take a couple of minutes, and only the owner sees the matches.

Can another Page publish my Reel too?

Yes, as a collaborator. POST /{video-id}/collaborators with target_id set to their Page's ID sends an invitation, and once they accept, the Reel appears on their Page as well.

Keep reading

Connect your first channel in two minutes.

No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.

  • 3 days free
  • Cancel any time
  • Official APIs only
  • Monitored 24/7

Verified on