igrantio-ows-overviewlisted

# iGrant.io OWS integration - overview ## When to use Read this skill before or alongside any of the `igrantio-*` backend/frontend skills. It defines the shared architecture and is the **single source of truth** for OWS endpoints, request payloads, the response fields you must process, and the integrator intake below. Every other skill in this collection assumes the contracts described here. ## 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. - For an issuer or a verifier that goes live: the organisation certificate registered in the trust list (see the section at the end). ## Ask the integrator first (the integrator intake) Run this interview before you write any integration code. Ask **one question at a time**. Wait for the answer. Give the recommended default with each question. Look up facts in the project (framework, existing env vars, an existing backend) instead of asking for them; only the decisions go to the integrator. Record the answers; every later choice hangs off them. 1. **Environment** - demo (`https://demo-api.igrant.io`) or staging (