From API key to verified delivery.
PostGate gives SaaS products one tenant-safe API for connecting customer accounts, publishing and scheduling content, tracking provider delivery, measuring results, and handling engagement.
Authenticate your backend
Create a server-side key in the workspace. Test keys exercise the complete sandbox lifecycle; live keys can publish through connected providers.
curl https://postgate.studio/api/platforms \
-H "Authorization: Bearer $POSTGATE_API_KEY"Start with the authentication guide for modes, scopes, group-bound keys, and tenant context.
Connect a customer account
Create a profile group for the customer, request a short-lived hosted URL, and redirect their browser to it.
curl -X POST https://postgate.studio/api/profiles/connect \
-H "Authorization: Bearer $POSTGATE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"platform": "instagram",
"profile_group_id": "grp_acme123",
"return_url": "https://app.example.com/settings/social"
}'{
"platform": "instagram",
"url": "https://postgate.studio/connect/eyJ...",
"expires_in": 900
}Open url in the customer's browser. After the provider flow, persist the returned profile_id or list profiles by group.
Publish with idempotency
Send connected profile IDs and one stable idempotency key per logical post. The request may target several platforms and finish partially.
curl -X POST "https://postgate.studio/api/posts?profile_group_id=grp_acme123" \
-H "Authorization: Bearer $POSTGATE_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: launch-post-001" \
-d '{
"post": { "body": "Launch day. 🚀" },
"profiles": ["pro_instagram123", "pro_linkedin456"],
"media": ["https://cdn.example.com/launch.jpg"]
}'Add an ISO 8601 scheduled_at.
Use scheduled_at: "queue" for the next slot.
Add draft: true for approval.
Observe each target
The create response is acceptance. Read each target or subscribe to signed webhooks for publication, partial success, failure, and reconnect requirements.
Use the delivery lifecycle to model target state and the webhook guide to remove polling from your normal path.
Everything the API offers, documented by job.
Start with the resource you need, then use the interactive reference for exact schemas and response variants.
Tenant and brand publishing boundaries
3 endpointsHosted connections and token health
6 endpointsDraft, schedule, queue, publish, and inspect
8 endpointsURL ingest, file upload, and multipart
4 endpointsCron templates and recurring slots
4 endpointsNormalized performance and growth
3 endpointsComments and direct messages
6 endpointsSigned asynchronous events
4 endpointsCapabilities, limits, and provider apps
5 endpointsScoped server credentials
3 endpointsWhite-label and BYO provider apps
7 endpointsUse a smaller, draft-first tool surface.
The hosted MCP server exposes the common publishing and engagement workflow. Post creation remains a draft unless an agent explicitly confirms publication.