Create consent record
Records that the individual allows a data agreement. The request has no body: the new record has `optIn: true` and the state `unsigned`. It refers to the latest revision of the data agreement, or to the revision in `revisionId`. For a data agreement with data using services, the record has a sector preference for each of their industry sectors, all allowed.
Read consent record of a data agreement
Reads the consent record of the individual for a data agreement. Use it to show the current choice of the individual. When the individual has no record for the data agreement, the answer is `200` with `'consentRecord': null`.
List consent records of the individual
Lists the consent records of the individual, one page at a time. Records of deleted data agreements are not in the list. Use it to show all the choices of the individual, for example in a privacy dashboard.
List consent records of a data agreement
Lists the consent records of the individual for one data agreement, one page at a time. An individual has at most one consent record for each data agreement, so the list has zero or one item.
Update consent record
Changes the choice of the individual in a consent record. Send one of these bodies:
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.
List consent history of the individual
Lists the consent changes of the individual over all data agreements, newest first, one page at a time. Each entry has a `log` line that says the new value, the purpose and the organisation in words. Use it to show the individual what they changed and when. The entries stay after 'Delete all consent records of the individual'.