Skip to main content
Data requests

Cancel a data download request of the individual

POST/v4/service/consent/organisation/data-download/{dataReqId}/cancel

Cancels a request of the individual to download its data: the request goes to state 8 (cancelled by the individual), and your organisation gets the webhook event data.download.cancelled. Get the ID from the status route or the list.

Send only the ID of an open download 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

  • 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"

Headers

  • X-ConsentBB-IndividualIdstring

    ID of the individual, or its externalId. Mandatory with an API key: without it the answer is 400 ("IndividualId is not present in request header"), and an unknown individual gets 400 too. 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 example consent-records:read), another route answers 400 to a request with this header.

    Example:"6af081b138e8f33dcf799628"

Response

application/json

The cancelled data request.

  • 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.