iGrant.io consent records (Consent BB individual API)

When to use

When your app must record and manage a user's consent for a data agreement - allow, read current state, withdraw, show history, or erase (right to be forgotten). Assumes you already have the individualId (from igrantio-individuals) and the dataAgreementId you are collecting consent for.

Prerequisites

• individualId - the Consent BB individual for the user (see igrantio-individuals; resolve it server-side from your session/userId mapping).
• dataAgreementId - the data agreement to record consent against.
• Organisation API key - server-side only.

API (Consent BB individual, base /v2)

Auth on every call: Authorization: ApiKey <key> and X-ConsentBB-IndividualId: <individualId>.