igrantio-backend-webhookslisted

# iGrant.io backend webhooks (register + receive + verify) ## When to use Whenever your backend must be notified when a wallet completes an issuance or verification. Pairs with `igrantio-backend-sse` (which streams the stored events to the browser). Composed by `igrantio-issuer-backend` / `igrantio-verifier-backend`. ## 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@igrant.io](mailto:support@igrant.io) before you continue. 3. **Webhook reachability** - which public HTTPS URL receives OWS webhooks? _Local dev needs a tunnel or the polling fall