📄️ Create consent record
Creates the consent record of the individual for a data agreement. The operation takes no request body, and the new record always has `optIn: true`. Without `revisionId`, the record uses the latest revision of the data agreement. An individual has one record for each data agreement: a second create gives HTTP 400. To record a first withdrawal, create the record, then update it with `{'optIn': false}`.
📄️ Read consent record
This endpoint is used to read a consent record for an individial for a chosen data agreement. There should be one unambiguous consent record for an individual.
📄️ Create draft consent record
This endpoint is used to create a draft (unsaved) consent record and signature object (without a PKI) for a data agreement.
📄️ Create consent record and signature
This endpoint is used to create a consent record and signature object. This returns the same objects with the PK defined.
📄️ List all consent records for individual
This endpoint is used to list all consent records for an individual belonging to an organiation defined in the consent building block.
📄️ Delete all consent records
Deletes all consent records of the individual, for example when the individual uses the right to be forgotten. The answer is HTTP 200 with an empty body.
📄️ Update consent record
Updates a consent record of the individual. Send `{'optIn': true}` to allow or `{'optIn': false}` to withdraw. To change one sector, send `{'sectorPreference': {'sector': '<sector>', 'optIn': false}}`; the sector must be in the data agreement, and the record must be opted in. A body without `optIn` and without `sectorPreference` withdraws the consent. The service takes the individual from the request header, not from the path or the query. The record moves to the latest revision of the data agreement and becomes `unsigned`, so an earlier signature is no longer valid.
📄️ Creates blank signature
This endpoint is used to create a blank signature object for the consent record for an individual in an organiation defined in the consent building block. Creates and returns a blank Signature object for the consent record.
📄️ Update consent record signature
This endpoint is used to update a signature object for the consent record for an individual in an organiation defined in the consent building block.
📄️ List all consent records
This endpoint is used to list all consent records existing for a data agreement for an organisation defined in the consent building block. The response is paginated.
📄️ List consent record history
This endpoint is used to list all consent record history existing for an individual in an organisation defined in the consent building block. The response is paginated.