Reviews

After an order is delivered, Tuppence asks the shopper for a review. You read each one, publish it, and reply once. You can keep a review off the page only for a rule of your published review policy, and the writer is told which. Being negative is never a reason.

Deliveredthe request goes after a few days
Writtenpending, or published at once
Publishedon the product's page

1. List the pending ones

curl -sS "https://api.tuppence.ai/v1/product_reviews?status=pending" \
  -H "Authorization: Bearer $TUPPENCE_SECRET_KEY"

2. Publish, reply or reject

Route	Does
`POST /v1/product_reviews/{id}/publish`	Shows it on the product’s page
`POST /v1/product_reviews/{id}/reply`	Your reply (`body`), beneath it. Sent again, it replaces the last
`POST /v1/product_reviews/{id}/reject`	Keeps it off the page. `reason` is required

Reasons to reject

`reason`	The review
`unlawful`	Contains something unlawful
`personal_data`	Contains someone’s personal details
`abusive`	Is hateful or abusive
`spam`	Is spam, or about something else
`conflict_of_interest`	Was written by someone with a conflict of interest, such as staff
`unverified`	Is from someone who didn’t buy it here, when you publish verified buyers only

Settings

GET and POST /v1/product_reviews/settings: whether requests go, how many days after delivery (5 by default, 14 for health and beauty), verified buyers only, and any incentive.

Events

Event	When
`product_review.requested`	A request went to a shopper
`product_review.published`	A review went on the page
`product_review.rejected`	A review was kept off it

Over MCP and the assistant

Tool	Scope	Does
`list_product_reviews`	`reviews:read`	Reviews, by status or product
`publish_product_review`, `reply_to_product_review`	`reviews:write`	A person approves each one
`reject_product_review`	`reviews:write`	Only for a rule of your policy. A person approves it

Next