How Facebook Publishing Works with Postproxy
Facebook's publishing model
Facebook's Graph API supports publishing to Pages (not personal profiles — Meta removed that capability in 2018). Each Page has its own access token and permission set, and publishing requires the pages_manage_posts permission. The API differentiates between feed posts (text, links, photos, videos) and Stories (ephemeral content). Postproxy manages Page token handling and routes your content to the correct Graph API endpoint based on the format you specify.
Feed posts, Stories, and Reels
Facebook feed posts support text, link previews, single images, multi-photo posts, and videos — each with different API endpoints and payload structures. Stories use a separate publishing flow with different media requirements (vertical format, 24-hour expiry). Postproxy normalizes these into a single request format: set format to post or story, include your media and text, and the API handles endpoint routing and payload construction.
Common gotchas Postproxy handles for you
Facebook's Graph API has version-specific behaviors that change with each platform update (typically every few months). Rate limits are per-Page and per-app, with separate limits for posting and media uploads. Video uploads use a resumable upload protocol that requires chunking large files. The API also returns different error formats depending on the endpoint. Postproxy abstracts these inconsistencies, handles API versioning, and manages the chunked upload flow for videos.
First comments and multi-page management
A common pattern for Facebook Pages is posting content and immediately adding a first comment with links or hashtags to boost engagement. This requires a separate API call after the initial post succeeds. When managing multiple Pages, each needs its own token with the correct permissions. Postproxy lets you set first_comment in your request and handles the post-then-comment flow atomically, and manages tokens across all your connected Pages.
