Delete all consent records of the individual
Deletes all consent records of the individual, for example when the individual uses the right to erasure. The answer is 200 with an empty body. The revisions and the history entries of the records stay, and so does the individual. This route takes an API key or a token of the identity provider of the organisation, not an individual token.
Authorizations
AuthorizationstringheaderrequiredYour API key with the prefix
ApiKey:ApiKey <your-api-key>. Get an API key.Scope:
consent-records:delete
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 server deleted the consent records. The body is empty.
No body.