Skip to main content
PUT
Reply to review
Replies are public. Whatever you send here appears under the review on your storefront, next to the customer’s original words.

How it works

A review holds one reply, stored on the review itself rather than as a thread. That shapes the whole endpoint:
  • PUT overwrites. Call it again on the same review and you replace the previous reply - this is also how you edit one. There is no separate update endpoint.
  • There is no delete. reply is required and must be at least 8 characters, so you cannot blank it out to remove a reply. Replace it with better wording instead.

Request

Permission

Requires stores.update, not a review-specific scope. A key that can reply to reviews can also change other store settings, so scope keys with that in mind.

Finding what to reply to

Use Get Reviews with hasReply==false to fetch the ones still waiting, worst first:
A reply is read by far more future buyers than by the reviewer. Answer the question the next shopper is silently asking - what went wrong, and what you did about it.

Authorizations

Authorization
string
header
required

Your API key goes here

Path Parameters

storeId
string<uuid>
required

The ID of the store that the review belongs to

reviewId
string<uuid>
required

The ID of the review to make the reply on

Body

The form containing the reply to the review

Form for replying to a review

reply
string
required

The reply to give the user on the review, this is displayed publicly

Required string length: 8 - 4096

Response

The operation was successfully completed.

Represents a default generic response for API endpoints.

success
boolean
required

Indicates whether the operation or response was successful.

message
string | null

A descriptive message providing additional context or information about the response.

code
string | null

The error code (if there was an error) to use when referencing the error

data
any | null

Represents the data associated with a response.

Last modified on August 2, 2026