igrantio-holder-notificationslisted

Composable building block: the iGrant.io OWS holder notifications inbox - the wallet-side channel that tells a HOLDER a credential offer, transaction code, front-channel authorization, deferred credential, or presentation request needs action. REST endpoints to list and delete notifications, a live Server-Sent Events stream (auth via the authorization query parameter because EventSource cannot send headers), a backend relay that injects the key, and a dependency-free browser client with reconnect/backoff and a notification-to-next-action decision table. Composed by igrantio-holder-backend.
L3-iGrant/skills · ★ 1 · API & Backend · score 75

Install: claude install-skill L3-iGrant/skills

# 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](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. ## 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@