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

# Revert a data point correction

> Reverts the most recent correction on a data point, restoring the value it held before that correction. The revert is appended to the history as a `revert` correction; nothing is deleted.

A revert is terminal. Once a data point's latest entry is a revert, its value is back to the reading it held before the correction and a second call returns 422. To change the value again, set a new one with `PUT` rather than reverting further.

Reverting does not recalculate anything downstream. A batch that was already generated keeps the value it was generated with.

Requires corrections to be enabled on the account.



## OpenAPI

````yaml DELETE /projects/{project_id}/events/{event_id}/data_points/{slug}/value
openapi: 3.1.0
info:
  title: Mangrove - API
  version: 1.1.0
servers:
  - url: https://app.gomangrove.com/api/v1
security:
  - sec0: []
paths:
  /projects/{project_id}/events/{event_id}/data_points/{slug}/value:
    delete:
      summary: Revert a data point correction
      description: >-
        Reverts the most recent correction on a data point, restoring the value
        it held before that correction. The revert is appended to the history as
        a `revert` correction; nothing is deleted.


        A revert is terminal. Once a data point's latest entry is a revert, its
        value is back to the reading it held before the correction and a second
        call returns 422. To change the value again, set a new one with `PUT`
        rather than reverting further.


        Reverting does not recalculate anything downstream. A batch that was
        already generated keeps the value it was generated with.


        Requires corrections to be enabled on the account.
      operationId: revert-a-data-point-correction
      parameters:
        - name: project_id
          in: path
          schema:
            type: string
          required: true
        - name: event_id
          in: path
          schema:
            type: string
          required: true
          description: >-
            Unique ID of the event in the `evt_XXXX` syntax. For example:
            `evt_DLnYvzbjSujNAvXE`
        - name: slug
          in: path
          schema:
            type: string
          required: true
          description: >-
            Data point type slug on the event's event type. For example:
            `ambient-temperature-c`
      responses:
        '204':
          description: Correction reverted.
        '403':
          description: >-
            Corrections are not enabled on the account, or the token does not
            have Data Collection write permission.
          content:
            application/json:
              examples:
                Corrections not enabled:
                  value:
                    errors:
                      - message: Corrections are not enabled
                Insufficient permission:
                  value:
                    errors:
                      - message: You are not authorized to perform this action
        '422':
          description: '422'
          content:
            application/json:
              examples:
                Nothing to revert:
                  value:
                    errors:
                      - message: No correction to revert
                Already restored:
                  value:
                    errors:
                      - message: >-
                          This value has already been restored to its original
                          value
                Unknown slug:
                  value:
                    errors:
                      - message: Unknown data point type 'ambient-temp'
      deprecated: false
components:
  securitySchemes:
    sec0:
      type: apiKey
      in: header
      name: Authorization
      x-bearer-format: ''

````