Log inStart Free Trial
easyCoexistence Official APIs

Posting videos to a Facebook Page through the API

A video reaches a Facebook Page through POST /{page-id}/videos, either with file_url, a URL Meta downloads itself, or with a file the app uploads to Meta first. title names the video, and description is the text Meta may show with the post. Meta then processes the file, and GET /{video-id}?fields=status reports video_status as processing until it reads ready.

easyCoexistence posts videos to Facebook Pages with publish_facebook_post from Claude, ChatGPT or your own code, now or scheduled up to 90 days ahead.

389

Error code when Meta cannot fetch the video file from the URL given in file_url.

382

Error code for a video file too small to upload; Meta asks for a larger file.

10 min to 6 months

Window for scheduled_publish_time on the videos edge, counted from when the video is published.

0 to 100

Range of processing_progress, the share of a video's processing done, reported beside video_status.

graph.facebook.com

Host for video uploads, per Meta's Video API overview, which marks graph-video.facebook.com deprecated for them.

h

The file handle an upload returns, passed to /{page-id}/videos as fbuploader_video_file_chunk to publish the video.

How is a video posted to a Page?

With POST /{page-id}/videos and a Page access token. The file reaches Meta one of two ways: file_url, an accessible URL of the video that Meta fetches itself, or an upload, where the app sends the bytes first. file_url cannot be combined with upload_phase, the parameter of the chunked upload, so a request uses one way or the other.

file_urlUploaded file
Where the video isAt a URL Meta can reachOn your own system
On /{page-id}/videosfile_urlfbuploader_video_file_chunk with the upload's handle
Before publishingNothing: Meta fetches the fileAn upload session, then the bytes
If it failsError 389 when Meta cannot fetch itResume from the offset Meta reports

How does the upload work for a file that is not online?

Meta's video publishing guide uses the Resumable Upload API. POST /{app-id}/uploads with file_name, file_length and file_type opens a session, and POST /upload:{session-id} with a file_offset header and the bytes returns a handle, h. The video is then published with POST /{page-id}/videos and fbuploader_video_file_chunk set to that handle, beside title and description. These upload calls carry a user access token.

  • An interrupted upload resumes from the file_offset that GET /upload:{session-id} returns.
  • The videos reference also documents a chunked upload on the same edge: upload_phase start, transfer and finish, with start_offset, file_size and video_file_chunk.

What do title and description do?

title is the title of the video. description is, in Meta's words, the text describing a post that may be shown in a story about it, so it is where the post's words go. Both are optional on the videos edge, and publish_facebook_post sends its message as the description and leaves the title unset.

How do you know when the video is ready?

Meta processes a video after it arrives. GET /{video-id}?fields=status returns video_status, which reads processing while Meta works, ready once the video is uploaded, encoded and has its thumbnails, or error if processing failed, with processing_progress giving the share done from 0 to 100. Meta can also report publishing status through Page webhooks on the videos field, which easyCoexistence does not subscribe to.

How large and how long can the video be?

The Page videos reference and Meta's video publishing guide state no maximum file size or length; the size rule they do name is error 382, for a file too small to upload. Meta's Reels and Stories guides set durations of their own: 3 to 90 seconds for a Reel and 60 at most for a video story. When easyCoexistence schedules a video, it copies the file at that moment and refuses one over 1 GB.

Which permissions and Page task does it need?

pages_manage_posts, pages_read_engagement and pages_show_list, with a Page token from someone who can perform the CREATE_CONTENT task, according to the videos reference and the publishing guide. Meta's Video API overview words it more strictly: the person should be able to perform admin-equivalent tasks on the Page, or hold an Admin role granted through Business Manager.

Which errors can a video post return?

Meta's videos reference lists these for POST /{page-id}/videos:

  • 389: unable to fetch video file from URL.
  • 382: the video file is too small; try again with a larger file.
  • 6000: a problem uploading the video file; try again with another file.
  • 6001: a problem uploading the video; try again.
  • 368: the action was deemed abusive or is otherwise disallowed.
  • 100: invalid parameter; 200: permissions error; 190: invalid OAuth 2.0 access token.

How does publish_facebook_post post a video?

It takes video_url, a public HTTPS link to the file, and message, and sends them to /{page-id}/videos as file_url and description, so Meta fetches the video itself. A post holds one video, and a link sent beside it is refused, so put the URL in the message. The result's post_id holds the ID Meta returned, which for a video is the video's own ID.

How is a video post scheduled?

Give publish_facebook_post a scheduled_at in ISO 8601 with a timezone, from 1 minute to 90 days ahead. easyCoexistence copies the video when the post is scheduled and publishes it to the Page at that time; list_scheduled_posts shows it, update_scheduled_post moves it or changes its text, and cancel_scheduled_post stops it. Meta's own scheduled_publish_time on the videos edge allows 10 minutes to 6 months.

Common mistakes

  • Pointing file_url at a page that plays the video rather than at the file. Meta downloads the address itself, and one it cannot fetch fails with error 389.
  • Uploading to graph-video.facebook.com. Meta's Video API overview marks that host deprecated for video uploads and asks for graph.facebook.com.
  • Announcing the video before it is ready. Check status until video_status reads ready, since processing continues after the publish call returns.
  • Sending a link with the video. publish_facebook_post refuses a link beside a file; write the URL into the message instead.
Doing this with EasyCoexistence

Your platform can do the same with POST /channels/:id/posts on the Partner API. 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 I upload a video from my computer to a Facebook Page through the API?

Yes, through Meta's Resumable Upload API, which returns a handle for /{page-id}/videos, or the chunked upload on that edge. publish_facebook_post takes a public HTTPS URL instead, so host the file first.

Can a video be uploaded without appearing in the Page's feed?

Yes. published set to false holds the post back, no_story suppresses the feed and timeline story, and secret keeps the video off Facebook and out of search.

Can one video be posted to several Pages?

Yes, by crossposting: a published video can go out on other Pages the person administers without being uploaded again, and it gets its own video ID on each Page.

How much does easyCoexistence cost for a Facebook Page?

US$ 9 to US$ 0.75 per connection per month, set by your total count of connections, with the first 3 days free. Each Page is one connection.

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