Reject a review or question
Turns a review or question down, citing a published rule and explaining why. Both reason_detail and rejection_reason are required, and rejection_reason must be the identifier of an active rejection reason (see Conversation Rejection Reasons). The body is validated before anything else: an invalid body changes nothing and sends no e-mail.
On success:
statusbecomesrejectedandis_publicbecomesfalse. A published conversation is taken off the storefront and out of the product's review statistics, which are cached: the change can take up to about 20 minutes to show on the product detail page and up to about 25 minutes on search listings.A
rejectedevent is recorded with the staff account the request was made with, the request's audited headers inrequest_headers(naming the Omnitron user for a request sent through the Omnitron remote proxy), thereason_detailand the cited reason.The author is e-mailed — with the Review Rejected or Question Rejected template, in the author's language — stating that the post was not published, the
reason_detailand the reason'stext— its translation into the author's language when the reason has one. The e-mail is skipped when the template is switched off throughDISABLED_EMAIL_TEMPLATES.
A rejected review does not block its author from writing a new review of the same purchase.
Allowed from pending, from approved (taking a published post down) and from null. Rejecting twice is refused, so the author is never mailed twice for one decision.
Token credential sent in the Authorization header, in the form: Token <your-token>. Requires a staff (admin) account.
The unique identifier of the conversation.
The grounds for rejecting a review or question. Both are e-mailed to the author.
The moderator's own explanation of why the post was not published. Must not be blank.
The identifier (pk) of the rejection reason cited — the published rule the post broke. Must be an active reason.
The conversation was rejected and is not public.
The storefront visibility of a conversation after a moderation decision.
true after approval, false after rejection.
The body is invalid. Errors are field-keyed lists.
Authentication credentials were not provided or are invalid.
The authenticated user does not have administrator privileges.
No conversation exists with the given identifier. An identifier that is not a number is answered with Not found. instead.
The body is valid but the conversation cannot be rejected. non_field_errors is a single string, not a list; match on error_code.
POST /api/v1/remote/1/conversations/{id}/reject/ HTTP/1.1
Host: sandbox.akinon.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 76
{
"reason_detail": "The third sentence contains a slur.",
"rejection_reason": 3
}{
"is_public": false
}Last updated
Was this helpful?

