igrantio-individualslisted

# iGrant.io individuals (Consent BB admin Individual API) ## When to use When your app onboards a user, create a matching **individual** in the iGrant.io Consent Building Block and store the returned `individualId` against your own `userId`. That mapping is what later lets `igrantio-consent-records` record and manage consents for the right person. ## 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. - 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`); a switch later is a configuration change._ 2. **API key** - do you have the OWS API key for that environment? If not, request it from [support@igrant.io](mailto:support@igrant.io) before you continue. 3. **Mapping storage** - a