igrantio-consent-recordslisted

# 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. ## Integrator intake Ask one question at a time, a recommended default with each; look up facts in the project, put only decisions to the integrator: 1. **Environment** - demo (`https://demo-api.igrant.io`), staging, or a custom Consent BB deployment (ask its base URL)? _Recommend demo to start._ 2. **API key** - organisation API key for the Consent Building Block? Server-side only, never the browser. 3. **Data agreement(s)** - which `dataAgreementId`(s) are consents recorded against? _Listed in the iGrant.io admin console; ask the integrator to paste them._ 4. **Erasure policy** - expose "delete all consents" (right to be forgotten) to end users, or admin-only? _Recommend admin-only unless the product requires self-service._ ## 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>` *