igrantio-api-verifierlisted

# iGrant.io OpenID4VC API - Verifier ## When to use Use this skill when your organisation asks a holder for credentials. It covers the 18 operations of the **Verifier** group: the verifier global configuration, presentation definitions, transaction data templates, the V3 verification request, the verification history, the Digital Credentials API response, and revalidation. Use it when you must: - write a DCQL query and store it as a presentation definition; - send an Authorization Request and get the `openid4vp://` URI and the correlation id; - read the disclosed claims and the `verified` result; - take a Digital Credentials API response from the browser; - check a finished exchange again after a revocation. For the wallet side of a presentation, read `igrantio-api-holder`. For issuance, read `igrantio-api-issuer`. ## 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, a