---
title: "Create a veto for a review"
method: POST
path: "/reviews/{reviewId}/vetos"
tags: ["Endpoints"]
---

# Create a veto for a review

`POST /reviews/{reviewId}/vetos`

This endpoint creates a veto for the specified review.
A veto flags a review as inappropriate and suggests that the review should be removed or investigated.
Veto objects consist of a comment, a reason and the associated channel name.

Note that whenever this method is called, eTrusted will create a ticket in Trusted Shops' Review Team board containing the veto data for further investigation.

## Path parameters

- `reviewId` string, required

## Request body

- ReviewVetoRequestDto
  - `comment` string, required — The veto comment. Provide additional information on the review or your veto here.
  - `reason` string, required — The reason for the veto. This string may only have the following values: * `UNTRUTHFUL` * `ABUSIVE`, * `VIOLATES_THE_TERMS_OF_USE` * `INAPPROPRIATE_IMAGE`
  - `vetoReporterEmail` string — The E-Mail address of the veto reporter.
  - `channelName` string — The name of the channel the review is associated with.

## Response `200`

The veto has been saved succesfully.

- ReviewVetoResponseDto — The veto has been saved successfully.
  - `id` string, required — The veto UUID.
  - `ticketId` string, required — A reference to the ticket that was created internally at Trusted Shops for this veto. The ID is a sequence of six digits.
  - `comment` string, required — The comment in the ticket that was created internally at Trusted Shops for this veto.
  - `reason` string, required — The reason for this veto. This string may only have the following values: * `UNTRUTHFUL` * `ABUSIVE` * `VIOLATES_THE_TERMS_OF_USE` * `INAPPROPRIATE_IMAGE`
  - `createdAt` string, date-time, required — The date and time when the veto was created, in the [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) and [RFC 3339](https://tools.ietf.org/html/rfc3339) compliant format yyyy-MM-dd’T’HH:mm:ss.SSSZ.
  - `updatedAt` string, date-time — The date and time when the veto was last modified, in the [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) and [RFC 3339](https://tools.ietf.org/html/rfc3339) compliant format yyyy-MM-dd’T’HH:mm:ss.SSSZ.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found

---

[API](https://skmtc.net/etrusted/apis/accounts-api.md) · [All operations](https://skmtc.net/etrusted/apis/accounts-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/etrusted/accounts-api/revisions/649ef7dac98c/schema)