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. **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}/…`). | Method | Path | Purpose | | --- | --- | --- | | GET | `v2/config/digital-wallet/openid/notifications?limit=&offset=&search=&notificationType=` | list; the array is under the response's **`notification`** key | | GET | `v2/config/digital-wallet/openid/notification/{id}` | read one | | PUT | `v2/config/digital-wallet/openid/notification/{id}` | update one - body `{ "status": "<string>" }`, response `{ "notification": … }` | | DELETE | `v2/config/digital-wallet/openid/notification/{id}` | delete one (the usual "handled" signal, 204) | | DELETE | `v2/config/digital-wallet/openid/notifications` | delete all (204) | | GET (SSE) | `v2/config/digital-