Comments
Read and answer comments on your customers' channels, moderate them, and turn a comment into a DM with an automation.
Comments arrive in the same workspace inbox as DMs. Your server hears about each new one through comment.received and answers through the comment endpoints. Reading needs a key with the viewer role. Replying, liking, hiding, and deleting need editor.
The incoming comment
{
"id": "evt_...",
"type": "comment.received",
"createdAt": "2026-11-10T12:00:00.000Z",
"workspaceId": "WORKSPACE_ID",
"data": {
"id": "COMMENT_ID",
"text": "Is this available in blue?",
"status": "open",
"isHidden": false,
"channelId": "CHANNEL_ID",
"platform": "instagram",
"postId": "POST_ID",
"parentId": null,
"externalPostId": "17890000000000000",
"authorUsername": "someone",
"authorName": "Someone",
"createdAt": "2026-11-10T11:59:58.000Z"
}
}channelIdtells you which customer the comment is for.postIdis set when the post was published through eksis.externalPostIdis the post's id on the platform, set either way.parentIdis set when the comment answers another comment eksis has.- How fast the event follows a real comment depends on the platform: some push new comments to eksis, others are checked on a schedule. Each platform specification says which.
Event reference: Comment received.
Answer and moderate
| Endpoint | What it does |
|---|---|
| Reply to a comment | POST /v1/comments/{commentId}/reply with text (up to 2,200 characters). It waits for the platform and marks the comment done. |
| Like a comment | Likes it as the channel. |
| Hide a comment and Show a hidden comment | Hides it on the platform. The person who wrote it is not told. |
| Mark a comment open or done | PATCH with status. Changes eksis only, not the platform. |
| Delete a comment | Deletes it on the platform. This cannot be undone. |
| List comments and Read one comment | Filter by status, channels, postId, or a search q. Your own comments are not included. |
curl -X POST https://api.eksis.io/v1/comments/COMMENT_ID/reply \
-H "Authorization: Bearer $EKSIS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text": "Yes, blue is in stock. We sent you the link by DM."}'A reply that the platform refuses comes back as an error right away: 424 when retrying will not help, 503 when you can try again later.
What each platform allows
Not every network lets an app like, hide, or delete a comment. Platform capabilities (GET /v1/capabilities) lists what each platform supports, and the platform specifications show the same in tables. For a single comment, Read one comment says which actions exist. Check before you offer an action in your own interface.
From a comment to a DM
The API has no endpoint that sends a private reply to a comment. An automation does it: a comment, or a comment with a keyword, on the posts it watches triggers the send_private_reply action, which sends the commenter a DM that answers their comment. When the person writes back, message.received arrives and your server can continue in that conversation as in Direct messages.
Create the automation in the app, or with Create an automation and an admin key. It is saved as a draft unless status is active, and an active automation starts sending DMs in the workspace's name right away. Instagram allows one private reply per comment, and eksis does not send one for a comment older than 7 days.