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. 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.