> ## Documentation Index
> Fetch the complete documentation index at: https://developers.partoo.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete a review from a custom partner

> This endpoint lets you delete a review your organization pushed through a **custom review
partner**. Reviews synchronized natively by Partoo (Google, Facebook, TripAdvisor…) cannot
be deleted this way.

The deletion is a soft one: the review is kept with `state: deleted` and its author masked,
which is what lets a later
[push of the same `external_id`](/api-reference/reviews/push-a-review-from-a-custom-partner)
bring it back. Deleted reviews are excluded from statistics, and from searches that filter
them out with `state__notin=deleted`.

Deleting a review you already deleted answers `204` as well, so a retry is always safe.
The `review_updated` webhook fires on the first deletion only.

You must use an API key with `ORG_ADMIN` rights and the `review_edit` permission.




## OpenAPI

````yaml /assets/openapi/openapi-bundled.yaml delete /reviews/{review_id}
openapi: 3.1.0
info:
  title: Partoo Rest API
  version: v2
  license:
    name: © Copyright Partoo
    url: https://www.partoo.co/en/gtu-api/
  x-logo:
    url: >-
      https://partoo-client-images.s3.amazonaws.com/logo-partoo-restapi-white.png
  description: >
    ## Introduction

    The Partoo Rest API allows you to automate all the actions that are possible
    to do in the Partoo Web Application.


    The Partoo Rest API can be used for many different purposes:
      - Create/update/delete your businesses & users if you are a client.
      - Create/subscribe/manage organizations, businesses & users if you are a reseller.
      - Retrieve data on businesses you have access to if you are a publisher.
      - ...
servers:
  - url: https://api.partoo.co/v2
    description: Production server
  - url: https://api.sandbox.partoo.co/v2
    description: Sandbox server (dev environment for clients & partners)
security:
  - ApiKeyAuth: []
paths:
  /reviews/{review_id}:
    delete:
      tags:
        - Reviews
      summary: Delete a review from a custom partner
      description: >
        This endpoint lets you delete a review your organization pushed through
        a **custom review

        partner**. Reviews synchronized natively by Partoo (Google, Facebook,
        TripAdvisor…) cannot

        be deleted this way.


        The deletion is a soft one: the review is kept with `state: deleted` and
        its author masked,

        which is what lets a later

        [push of the same
        `external_id`](/api-reference/reviews/push-a-review-from-a-custom-partner)

        bring it back. Deleted reviews are excluded from statistics, and from
        searches that filter

        them out with `state__notin=deleted`.


        Deleting a review you already deleted answers `204` as well, so a retry
        is always safe.

        The `review_updated` webhook fires on the first deletion only.


        You must use an API key with `ORG_ADMIN` rights and the `review_edit`
        permission.
      operationId: deleteReview
      parameters:
        - in: path
          name: review_id
          required: true
          description: >-
            Partoo id of the review, as returned by the push and search
            endpoints.
          schema:
            $ref: '#/components/schemas/ReviewId'
      responses:
        '204':
          description: The review is deleted
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                      - success
        '401':
          $ref: '#/components/responses/401'
        '403':
          description: >
            You are not allowed to perform this action. Either:

            - the API key's user is not an `ORG_ADMIN` or lacks the
            `review_edit` permission
              (`errors.authorization`),
            - the review was not pushed by a custom partner, or your
            organization is no longer
              enabled for that partner (`errors.json`).
          content:
            application/json:
              schema:
                type: object
                properties:
                  errors:
                    type: object
                    description: The detail of the error encountered
                    properties:
                      json:
                        type: string
                        example: This review was not pushed by a custom partner
                      authorization:
                        type: string
                        example: Operation not allowed
        '404':
          description: >
            No such review. A review belonging to another organization answers
            `404` too, and is

            deliberately indistinguishable from an unknown id.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReviewError'
components:
  schemas:
    ReviewId:
      type: integer
      description: Review id
      example: 34
    ReviewError:
      description: Error returned when a review cannot be pushed or deleted
      type: object
      properties:
        errors:
          type: object
          description: The detail of the error encountered
          properties:
            json:
              type: string
              description: Reason the request was refused
              example: Partner not found
  responses:
    '401':
      description: You are not authenticated
      content:
        application/json:
          schema:
            description: Error that occurs when you are not authenticated
            type: object
            properties:
              errors:
                type: object
                description: The detail of the error encountered
                properties:
                  authentication:
                    type: string
                    default: User not authenticated
  securitySchemes:
    ApiKeyAuth:
      description: >
        The authentication system on Partoo API is using API Key that should be
        put in the header of the request (the name of the header is `x-APIKey`).
        An api_key is linked to a user. This user's role will give you different
        access level to the API features.
      type: apiKey
      in: header
      name: x-APIKey

````