/api/facebook/post and /api/instagram/post. Keep payloads platform-specific; unified auth does not mean identical fields.Who this is for
Developers and automation teams who need multi-network publishing without maintaining six OAuth stacks.
Steps
- Follow Getting started.
- Connect destinations and verify with Authentication.
- Publish using Create a post examples.
- Track failures with Errors and Post History.
How to schedule posts on multiple platforms
Postifys executes a publish when your workflow or app calls it — the schedule time usually lives in your calendar source, CMS, or automation tool:
- n8n — use a Schedule Trigger or read a
scheduled_atcolumn from Airtable or Google Sheets, then call Postifys when the row is due. See schedule multi-account publishing in n8n. - REST API — your backend decides when to POST to each platform endpoint.
- Dashboard compose — publishes immediately when you submit (no built-in marketing calendar).
To post to Instagram, Facebook, and LinkedIn in one workflow, see post to Instagram, Facebook, and LinkedIn simultaneously.
Create account · Compatibility matrix
What this means in a real publishing workflow
Postifys provides one authentication layer for several social publishing endpoints while retaining platform-specific request shapes. The API key identifies the Postifys user; connected destination IDs determine where each post is sent.
Recommended implementation
- Create an API key and query the available connections.
- Resolve the exact Page, channel, board, or profile ID.
- Send the platform-specific payload with reachable media.
- Persist the returned Postifys ID and reconcile the final history state.
How to verify the fix
Start with one destination per platform. Once account selection and media handling are proven, add fan-out, scheduling, alerts, and safe retry logic.
Related Postifys resources
API documentation · Error reference · n8n automation guide · Safe retry guide · Compatibility matrix