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. ## Prerequisites - An **iGrant.io Organisation Wallet Suite (OWS) API key**. Get it from [support@igrant.io](mailto:support@igrant.io). Keep it on the server, in an environment variable or a secret manager. The browser never sees it. - The **OWS environment** the key belongs to. The default is **demo** (`https://demo-api.igrant.io`). Use **staging** (`https://staging-api.igrant.io`) only when the integrator asks for it. A key works only in its own environment. - `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. - The same organisation API key serves the Consent Building Block. ## Ask the integrator first Ask one question at a time. Wait for the answer. Give the recommended default with each question. Look up facts in the project (framework, environment variables, an existing backend) instead of asking for them. Record the answers before you write code. 1. **Environment** - demo or staging? _Default demo (`https://demo-api.igrant.io