Inklate Docs
Channels

Facebook

Connect the Facebook pages you manage, then publish text and photo posts, video posts, reels, and stories — each authored as the page itself.

Connecting Facebook authorizes Inklate once and surfaces every page you manage as its own channel. Each page can publish text and photo feed posts, a video post, a 9:16 reel, or a story — always authored as the page itself, because Meta’s API does not allow posting to a personal timeline.

Connecting Facebook

Facebook publishing uses Meta’s Graph API with standard authorization-code OAuth. Click Connect on the Facebook card and your browser leaves for Facebook’s consent screen; you approve the requested page permissions there and return, never entering a password into Inklate. Inklate then lists the pages you administer, each with its name and picture, and you pick which become channels.

Behind the scenes each page carries its own page access token, which is what actually authors posts on that page. Facebook issues a long-lived token (about 60 days) and has no refresh token — Inklate re-issues it when you reconnect, so an expiring Facebook channel is renewed by reconnecting.

What you can publish

Facebook supports three formats. A feed post carries text with photos or a single video; reels and stories are video formats published through Meta’s dedicated video flows.

FormatMedia
PostText with up to 10 photos, or one video (photos and video not mixed)
ReelOne 9:16 MP4, 3 to 90 seconds
StoryOne MP4 video frame, up to 60 seconds

In prose: a Facebook feed post allows a very large text body (up to 63,206 characters) with up to 10 photos (JPEG, PNG, or GIF) or one video — the two can’t be mixed in one post. A reel is one vertical 9:16 MP4 from 3 to 90 seconds, and a story is a single MP4 video frame up to 60 seconds.

Facebook publishes media by pulling it from a URL Inklate provides rather than uploading bytes directly. Photos are registered unpublished and then attached to one feed story; a video post is handed to Facebook by file_url and may take a few seconds to appear; reels and stories run through Meta’s phased video flow, where Facebook fetches the clip from the same file_url pull model. Facebook auto-links plain URLs, and Inklate renders bold and italic with Unicode glyphs since the platform stores plain text.

Analytics

Facebook always reports reactions, comments, and shares from the post itself. Impressions and clicks come from Page Insights, which needs an additional permission and a page token; a page connected without it still reports reactions, comments, and shares, with impressions and clicks left unmeasured.