Skip to main content
Data requests

Update data request

PUT/v4/config/consent/organisation/data-request/{dataReqId}

Moves a data request of an individual to a new state, with an optional comment for the individual. Usually you set 2 (acknowledged) when you start to handle the request, then 6 or 7 when you finish it. A request in state 6, 7 or 8 is closed, and the server sets its closedDate.

The server checks only that the new state is not lower than the current state; it does not check the other values. The comment is stored for the new state: the comment of a data request is the comment of its current state.

In this answer, closedDate is still the value from before the update. Read the data request again to see the new value.

This route needs the feature consentManagement of your organisation.

Authorizations

  • Authorizationstringheaderrequired

    Your API key with the prefix ApiKey: ApiKey <your-api-key>. Get an API key.

    Scope:data-requests:update

Path parameters

  • dataReqIdstringrequired

    ID of the data request.

    Example:"6af19d442d6fb7b6ac6efd11"

Body

application/json
  • stateenum<integer>required

    The new state: 1 initiated, 2 acknowledged, 6 processed without action, 7 processed with action, 8 cancelled by the individual. It must not be lower than the current state.

    Available options:1,2,6,7,8

    Example:7

  • commentstring

    A comment for the individual about the new state. Leave it out for no comment.

    Example:"We sent the export of your data to your e-mail address."

Response

application/json

The data request in its new state.

  • dataRequestobject

    A request of an individual to delete, download or update personal data that your organisation holds. The individual makes it, your organisation handles it and moves it through its states, and the individual can cancel it.