Skip to main content
POST
/
comments
/
{id}
/
reply
Reply to a comment
curl --request POST \
  --url https://api.salesive.com/api/v1/comments/{id}/reply \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data @- <<EOF
{
  "content": "Thanks for your feedback — we've shipped a fix!"
}
EOF
{
  "status": 201,
  "success": true,
  "message": "Reply posted",
  "data": {
    "_id": "66f1f0a3c2d4e5f6a7b8c9d1",
    "content": "Thanks for your feedback — we've shipped a fix!",
    "parent": "66f1f0a3c2d4e5f6a7b8c9d0",
    "shop": "6680aabbccddeeff00112200",
    "createdAt": "2026-06-21T12:30:00.000Z",
    "updatedAt": "2026-06-21T12:30:00.000Z"
  }
}
Posts a reply to the parent comment identified by {id}, which must be scoped to your store. The store is bound to your app token server-side — never send a shop id.

Authorizations

​
Authorization
string
header
required

Installed-app access token (prefix app_), issued by the OAuth install flow. The store is bound to the token server-side — never send a shop id.

Path Parameters

​
id
string
required

The comment's id (Mongo ObjectId).

Body

application/json
​
content
string
required

The reply text.

Response

The created reply.

Standard Salesive response envelope. The operation-specific payload is carried in data.

​
status
integer
required

HTTP status code, echoed in the body.

​
success
boolean
required

Whether the request succeeded.

​
message
string
required

Human-readable result message.

​
data
object

A storefront comment or reply belonging to the store.