igrantio-api-webhookslisted

# iGrant.io OID4VC API - Webhook group ## When to use Use this skill when you: - register an external IT system to receive OWS events; - must know the exact event type strings to subscribe to; - verify the `X-IGrant-Signature` header on an incoming delivery; - debug a receiver that gets no events, or reads a delivery record. Base URL for demo: `https://demo-api.igrant.io`. Auth header: `Authorization: ApiKey <key>` (note the trailing space in the prefix). A bearer access token also works. The webhook operations carry only the `Webhook` tag. They serve every building block, not the OID4VC wallet alone. ## 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 chang