← ClaudeAtlas

igrantio-api-issuerlisted

Issuer group of the iGrant.io OpenID4VC API: create and maintain credential definitions (claim path pointers, display, revocation, scopes, logo and cover images, templates, URI preview), issue credentials InTime or Deferred over OpenID4VCI 1.0, read and delete issuance history, update the revocation status of an issued credential, and validate transaction data. Use this skill when you build the issuing side of an EUDI Wallet (EUDIW) or European Business Wallet (EUBW) integration, or whenever you need the exact issuer path, request field, or enum value.
L3-iGrant/skills · ★ 1 · Code & Development · score 75
Install: claude install-skill L3-iGrant/skills
# iGrant.io OpenID4VC API - Issuer ## When to use Use this skill when you issue credentials from an iGrant.io organisation. It covers the 26 operations of the **Issuer** group: the issuer global configuration, credential definitions, credential issuance, issuance history, revocation status, scopes, and transaction data validation. Use it when you must: - create or change a credential definition, or read the ready-made templates; - issue a credential and get the credential offer URI and the correlation id; - complete a deferred issuance; - revoke or suspend a credential that you issued; - read or delete the issuance history of your organisation. For the holder side, read `igrantio-api-holder`. For the verifier side, read `igrantio-api-verifier`. ## 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