iGrant.io holder notifications (REST + SSE)

When to use

Whenever a holder (wallet-side) application must react to wallet events: an incoming credential offer, a transaction-code prompt, a front-channel authorization step, a deferred credential becoming ready, or a verifier's presentation request. Notifications are the holder's event channel - the holder role has no webhooks; issuer/verifier backends use igrantio-backend-webhooks instead. igrantio-holder-backend composes this skill.

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.