Read an open data update request of the individual
Tells if the individual has an open request (state 1 or 2) to update its data in your organisation, and gives its ID, state and date. The individual can have more than one open update request: the answer then gives one of them. Use the list to see all of them. 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:read
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
An open update request, or requestOngoing false.
requestOngoing booleantruewhen the individual has an open request of this type.Example:
trueidstringID of the open request, or
"".Example:
"6af19d442d6fb7b6ac6efd11"stateenum<integer>State of the open request:
1initiated,2acknowledged.0when there is no open request.Available options:
0,1,2Example:
2stateStr enum<string>Name of the state, or
"".Available options:
,Request initiated,Request acknowledgedExample:
"Request acknowledged"requestedDate stringDate and time of the open request in UTC, in the text form
YYYY-MM-DD hh:mm:ss +0000 UTC(not RFC 3339), or"".Example:
"2026-11-09 10:15:32 +0000 UTC"