Cancel a data delete request of the individual
Cancels a request of the individual to delete its data: the request goes to state 8 (cancelled by the individual), and your organisation gets the webhook event data.delete.cancelled. Get the ID from the status route or the list.
Send only the ID of an open delete request: the server does not check the type or the state of the request, and sets any request of the individual to state 8 (the webhook event then has the type of that request). In this answer, closedDate is still the value from before the cancel. This route takes an API key or a token of the identity provider of the organisation, not an individual token or a token of the privacy dashboard login.
Authorizations
AuthorizationstringheaderrequiredYour API key with the prefix
ApiKey:ApiKey <your-api-key>. Get an API key.Scope:
data-requests:update
Path parameters
dataReq Id stringrequiredID of the data request.
Example:
"6af19d442d6fb7b6ac6efd11"
Headers
X-Consent BB- Individual Id stringID of the individual, or its
externalId. Mandatory with an API key: without it the answer is400("IndividualId is not present in request header"), and an unknown individual gets400too. With an individual token, leave it out: the server takes the individual from the token. Send it only on the routes that list it: with an API key that has resource scopes (for exampleconsent-records:read), another route answers400to a request with this header.Example:
"6af081b138e8f33dcf799628"
Response
The cancelled data request.
dataRequest objectA 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.