One unified POST /api/posts call drafts, schedules, or queues content across Instagram, Facebook, LinkedIn, TikTok, YouTube, Threads, Bluesky, Mastodon, Telegram, Pinterest, Google Business Profile, and X — with cron-based recurring templates, per-target delivery evidence, and signed webhooks so your product knows exactly what happened, not just that a request was accepted.
draft: true saves a post for approval. An ISO 8601 scheduled_at publishes at a fixed instant. scheduled_at: "queue" drops a post into the next open recurring slot. Omit all three and delivery starts immediately. See Posts.
Create a kind: "cron" schedule with a standard cron expression and timezone for recurring templates, or a kind: "slots" schedule with comma-separated HH:mm times to build a posting queue. See Schedules & queues.
A post's aggregate status summarizes the request, but the targets array is the operational truth: status, attempt count, next retry, error, platform ID, and permalink for every destination. Partial delivery is a real, successful terminal state. See Delivery lifecycle.
Subscribe to post.published, post.partial, and post.failed events, verify the signed payload, and let PostGate retry deliveries to your endpoint on timeout or non-2xx response. See Webhooks.
Target posts by explicit profile IDs, not by inferred account matching, so the same request behaves the same way every time.
A stable Idempotency-Key makes a create request safe to retry for 72 hours without double-publishing.
Provider-specific fields live under post.options.<platform>, and body_overrides lets one target carry different copy while the rest of the post stays shared.
Free, Solo, Launch, and Build plans all include scheduling, queueing, and webhooks — the difference is connected profiles, posting volume, and entitlements like white-label and BYOK. See the full breakdown on the pricing page.