Data requests

List data delete requests of the individual

GET/v4/service/consent/organisation/data-delete

Lists all the requests of the individual to delete its data in your organisation, open and closed, in no fixed order. dataRequests is null when the individual has made none.

Language of the request sample

curl 'https://demo-api.igrant.io/v4/service/consent/organisation/data-delete' \
  -H 'Authorization: ApiKey <your-api-key>'

{
  "dataRequests": [
    {
      "id": "6af19d442d6fb7b6ac6efd11",
      "userId": "6af081b138e8f33dcf799628",
      "userName": "[email protected]",
      "organisationId": "6ae2bf741c3dadfeb27982ec",
      "type": 1,
      "typeStr": "Delete Data",
      "state": 2,
      "requestedDate": "2026-11-09 10:15:32 +0000 UTC",
      "closedDate": "0001-01-01 00:00:00 +0000 UTC",
      "stateStr": "Request acknowledged",
      "comment": "We are checking your request."
    }
  ]
}

Authorizations

Authorizationstringheaderrequired
Your API key with the prefix ApiKey: ApiKey <your-api-key>. Get an API key.
Scope:data-requests:read

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 data delete requests of the individual.

dataRequestsobject[] | null