Create individual
Creates an individual from your app or website, for example when a new user signs up. Keep the returned `id`: the consent record routes take it in the `X-ConsentBB-IndividualId` header. This route takes an API key only; a key with only the `individual:create` scope (`individuals:create`) is enough.
List individuals
Lists the individuals of the organisation, one page at a time, newest first. Use `externalIndividualId` to find the individual with that external ID. This route takes an API key, or a token of the identity provider of the organisation: with such a token, the list has only the individual of the token. An individual token and a token of the privacy dashboard login get `403`.
Read individual
Reads an individual. With a token of an individual (an individual token, a token of the privacy dashboard login or of the identity provider of the organisation), the individual can read only its own record: another ID gets `403`.
Update individual
Changes an individual, for example to save the push notification token of a new device. 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. With a token of an individual (an individual token, a token of the privacy dashboard login or of the identity provider of the organisation), the individual can change only its own record.
Delete individual
Deletes an individual. 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 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 that has this `mapperId`, for example to save the push notification token of a new device. Send only the members that you want to change: the service changes a member only when you send it with a value of at least two characters. A changed `name` or `email` also changes the login account of the individual, and a first `email` creates one.
Issue individual token
Returns a short-lived access token for one individual of your organisation, for the privacy dashboard SDKs in your app or website. With the token, the individual reads and changes only its own consent records and its own individual record. Call this route from your backend when your user opens the consent screen, and give the token to the SDK.