Facebook Page posts API: publish text, links, photos and videos
The Graph API publishes four kinds of Page post: text and links through POST /{page-id}/feed, a photo through /{page-id}/photos from a URL already on the internet, and a video through /{page-id}/videos from an accessible file URL. Posts appear in the voice of the Page, need a Page access token with pages_manage_posts, and can wait unpublished for a scheduled time.
easyCoexistence publishes to Facebook Pages with publish_facebook_post from Claude, ChatGPT or your own code: text, a link, a photo or a video, now or scheduled up to 90 days ahead from easyCoexistence's queue, and list_social_posts reads the posts back.
Largest photo file Meta accepts for a Page; it recommends keeping PNG files under 1 MB to avoid pixelation.
Photo file types Meta lists for Page photos: JPEG, BMP, PNG, GIF and TIFF.
Error code when Meta cannot fetch the video file from the URL given to /{page-id}/videos.
Ranked, published posts per year the API returns when reading a Page's feed, at most 100 per request.
What can a Page post carry?
Four kinds of content, through three edges of the Page, and the posts appear in the voice of the Page. Text and links share the feed edge, where message or link has to be present; a photo and a video each have an edge of their own:
How does publish_facebook_post choose the edge?
From what it is given. A video_url goes to /videos with message as the description; otherwise an image_url goes to /photos with message as its text; otherwise message and link go to /feed. A link travels only on a text post, so with a photo or a video, put the URL in the message. Without scheduled_at the post goes out at once and the result carries post_id, the ID Meta returned, and url, its link on Facebook; with scheduled_at, easyCoexistence holds the post in its queue, from 1 minute to 90 days ahead, and publishes it then.
Where does the media have to be?
At an address Meta can reach, because Meta fetches the file itself. For a photo, url is a photo already uploaded to the internet; for a video, file_url is an accessible URL of the file, and a video Meta cannot fetch fails with error 389. A link post fails when the app cannot see the linked URL, and error 1609005 means Meta could not scrape data from the link.
Which photo files does Meta accept?
JPEG, BMP, PNG, GIF and TIFF files of up to 10 MB, according to Meta's photo reference, which recommends keeping PNG files under 1 MB because larger ones may look pixelated. Meta strips location metadata before publishing and resizes images to render at several sizes. A missing or invalid image fails with error 324.
What does a video post need?
A file Meta can download from file_url, with the post's text in description, which Meta may show with the post; a title is optional, and publish_facebook_post leaves it unset. Meta's Video API overview says the person behind the token should be able to perform admin-equivalent tasks on the Page, and its Resumable Upload API handles large files, resuming interrupted uploads.
How are posts read back and edited?
list_social_posts returns the Page's recent posts, 25 by default and up to 100 per call, each with its ID, text, creation time, permalink and picture. Meta's reference caps a feed read at 100 posts per request and returns approximately 600 ranked, published posts a year. Meta's API edits a post with POST /{page-post-id} and the new message, only for posts made with the same app; easyCoexistence has no tool for it, so a post is edited on Facebook or in Meta Business Suite.
Common mistakes
- Passing a link with a photo or a video. publish_facebook_post refuses a link beside a file, so write the URL into the message when the post has media.
- Publishing the same content twice in a row. Meta refuses consecutive duplicate posts with error 506, so change the text before trying again.
- Pointing at a file behind a login or a link about to expire. Meta fetches the photo or video from the URL itself, so the address has to stay public until the post is up.
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 publish a photo to a Facebook Page from a URL?
Yes. POST /{page-id}/photos takes url, the address of a photo already on the internet, and Meta fetches it itself.
Why does a Facebook Page post fail with error 506?
Meta refuses consecutive duplicate posts with error 506, so change the text before publishing again.
Can one Facebook post carry several photos?
Not through easyCoexistence: publish_facebook_post takes one photo. Meta documents multi-photo posts, built from photos uploaded unpublished and attached to a feed post, which its tools do not cover.
Can I edit a Facebook Page post through the API?
Yes, with POST to the post's ID, but only for posts made with the same app. easyCoexistence has no tool for it, so edit the post on Facebook or in Meta Business Suite.
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