Getting started
Migrate from PostProxy
Keep the familiar post envelope and move with a base URL, key, and delivery-handling change.
01
Change the origin and key
Point your client at PostGate, replace the Bearer token, and add a stable
Idempotency-Key to every logical create-post request.New API originPostGate API
https://postgate.studio/api02
Keep the PostProxy-style envelope
PostGate accepts the documented
post, profiles, and media envelope; profile-group context; unambiguous platform slugs; URL, base64, and pre-uploaded media; and page/per_page pagination.03
Treat create as acceptance
Consume
post.published, post.partial, and post.failed webhooks or poll the returned ID. Persist the target array so a partial result never hides successful destinations.04
Deliberate differences
Errors use a single structured envelope. Test keys always use the complete sandbox lifecycle. Approval-gated platforms report explicit capability state. MCP post creation remains a draft unless
confirm: true is present.Pre-upload large media
Use
POST /api/media and reuse the returned med_… ID for more reliable large-file delivery.