Observe & engage
Delivery lifecycle
Model asynchronous publishing with aggregate post status, target-level evidence, retries, and reconnect states.
3
Endpoint summary
All operations in this resource, with the minimum accepted key scope.
Method & endpointPurposeScope
GET
/api/posts/{id}Read aggregate and target status
readGET
/api/posts/{id}/logsRead delivery attempts and evidence
readGET
/api/profiles/{id}/healthCheck whether reconnection is required
read01
Aggregate post status
draft and scheduled are waiting states. processing means at least one target is active. published, partial, failed, and canceled are terminal for the aggregate post.02
Target status is the source of truth
Each platform target progresses through
pending, media_ready, publishing, and sometimes reconciling or retry_scheduled. Terminal outcomes are published, failed, or skipped. awaiting_reconnect needs customer action.03
Poll only when webhooks are not practical
The create response is acceptance, not proof of publication. Subscribe to terminal webhooks for normal operation. If polling, back off between reads and stop when every target is terminal.
Inspect one postPostGate API
curl https://postgate.studio/api/posts/post_01JXYZ \
-H "Authorization: Bearer $POSTGATE_API_KEY"04
Use logs for support and operations
Delivery logs expose a sanitized attempt timeline without leaking provider tokens. Correlate requests with the response’s
X-Request-Id header and the post’s trace_id.