← 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`. ## Protocol scope - The issuer implements **OpenID4VCI 1.0**. Set `version` to `version_01` on the credential definition. Always send `version`, because the issuer falls back to an earlier version of the specification when you leave the field out. You cannot change the value after you create the credential definition. - Claims use **claim path pointers** (`claims.claims[].path`), not the older flat claim maps. - Draft protocol versions are not a supported surface of this group. - Presentation Exchange is not supported. When an issuance also asks the holder for a credential (`presentationDefinitionId`), the request uses a stored presentation definition that holds a **DCQL** query. ## Authentication Send the API key in