API operational
Observe & engage

Comments & messages

Read comments on published targets, reply or moderate where supported, and continue existing direct-message conversations.

6

Endpoint summary

All operations in this resource, with the minimum accepted key scope.

Method & endpointPurposeScope
GET/api/posts/{id}/comments

List comments on a post

read
POST/api/posts/{id}/comments/{commentId}/reply

Queue a comment reply

publish
DELETE/api/posts/{id}/comments/{commentId}

Delete a comment where supported

publish
GET/api/conversations

List direct-message conversations

read
GET/api/conversations/{id}/messages

List conversation messages

read
POST/api/conversations/{id}/messages

Queue an outbound message

publish
01

Read and reply to comments

Comments belong to a published post target. Filter by profile_id when the same unified post was sent to multiple accounts.
Reply to a commentPostGate API
curl -X POST https://postgate.studio/api/posts/post_01JXYZ/comments/cmt_123/reply \
  -H "Authorization: Bearer $POSTGATE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "text": "Thanks for the question — yes, it is available now." }'
02

Continue existing conversations

List conversations by profile, load their messages, and send a reply by conversation ID. Outbound replies return 202 because the provider delivery runs asynchronously.
Send a direct messagePostGate API
curl -X POST https://postgate.studio/api/conversations/cnv_123/messages \
  -H "Authorization: Bearer $POSTGATE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "text": "We can help with that." }'
03

Check provider capability first

Comments, deletion, and direct messages are not universal. Read features.comments and features.messages from the platform capability matrix before showing an action.
Permission and review dependent
A platform may support a feature technically while your connected app still needs additional provider review or scopes.