Create individual
Creates an individual: a person whose consent your organisation records. Keep the returned `id`: the consent record routes take it in the `X-ConsentBB-IndividualId` header.
List individuals
Lists the individuals of the organisation, one page at a time, newest first. Use `search` to find individuals by part of their ID, name, email, phone, `externalId`, `iamId` or `mapperId`. Use `externalIndividualId` to get the individual with that external ID.
Read individual
Reads an individual of the organisation.
Update individual
Changes an individual. Send only the members that you want to change: the server changes a member only when you send it with a value of at least two characters, so you cannot empty a member. A changed `name` or `email` also changes the login account of the individual, and a first `email` creates one.
Delete individual
Deletes an individual of the organisation. The service marks the record as deleted, so no route finds the individual again, and deletes the login account of the individual, if it has one. The consent records of the individual are not deleted. The response returns the individual as it was.
Read individual by mapper ID
Reads the individual of the organisation that has this `mapperId`: the second ID that you gave the individual, for example its user ID in your mobile app.
Update individual by mapper ID
Changes the individual of the organisation that has this `mapperId`. It works as Update individual: send only the members that you want to change, because the service changes a member only when you send it with a value of at least two characters, so you cannot empty a member. A changed `name` or `email` also changes the login account of the individual, and a first `email` creates one.
Delete individual by mapper ID
Deletes the individual of the organisation that has this `mapperId`. It works as Delete individual: the service marks the record as deleted and deletes the login account of the individual, if it has one. The consent records of the individual are not deleted.