Facebook API integration guide
Publish to connected Facebook surfaces, sync available feed data, normalize supported analytics, and manage compatible engagement workflows.
Publish to connected Facebook surfaces, sync available feed data, normalize supported analytics, and manage compatible engagement workflows.
Facebook integration overview
Publish to connected Facebook surfaces, sync available feed data, normalize supported analytics, and manage compatible engagement workflows.
Page identity, Page permissions, provider-app mode, and account scopes can change the available operations.
A provider appearing in this guide does not guarantee that every operation is enabled for every account. Use capability discovery before showing a control or promising automation.
Publishing workflows
- Text and link-oriented posts
- Supported image and video posts
- Multi-account targeting for connected Pages
Model a post as one parent workflow with a separate target for each Facebook account. This preserves the resolved content, delivery attempt, provider identifier, error, and retry state for every destination.
Connection and setup checklist
- 1
Choose a managed or customer-owned Meta provider app.
- 2
Connect the intended Facebook identity and select the resulting Page account.
- 3
Fetch capabilities and verify Page publishing and engagement scopes.
Media and validation
Validate placement-specific image and video limits through the account capability matrix before upload or dispatch.
Validate before dispatch as well as during composition because account permissions and provider constraints can change after a draft is saved. Return target-level provider errors with a safe message, stable error code, and request ID.
Feeds, analytics, and engagement
Feed, analytics, comments, mentions, messages, and replies are exposed only where the connected Page and provider permissions allow them.
Normalized analytics use null when a metric is unavailable. A missing provider metric is not the same as a measured zero, and client reports should preserve that distinction.
Frequently asked questions
Does App9 Post support every Facebook feature?
No. Support is determined by the connected account's current capability response, provider permissions, account type, provider review, and App9 Post certification status.
Should my composer hardcode Facebook limits?
No. Use the capability matrix for live validation and treat documentation as design guidance rather than a substitute for account-level constraints.
Can I use my own Facebook OAuth app?
App9 Post supports managed and customer-provided provider credentials where the provider connection is available. Customer-owned apps remain subject to the provider's review and policy requirements.