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.

Before you build: run the integrator intake in igrantio-ows-overview - environment, API key, tenancy, backend host, webhooks, frontend - one question at a time, a recommended default with each.

Contract

Paths are relative to the OWS base URL; the browser calls them through the tenant backend proxy ({backend}/ows/{tenant}/…).