# EUDI Wallet and European Business Wallet Developer Docs and APIs | iGrant.io

Build on the European Digital Identity Wallet framework. Full support for OpenID4VC, SD-JWT, and ISO 18013-5 mdoc.

This is the developer documentation site for iGrant.io, a European EUDI and Business Wallet software provider offering production-ready APIs for credential issuance, verification and management built on eIDAS 2.0 and OpenID4VC standards.

Every page is available as raw markdown by appending `.md` to its URL (for example `https://docs.igrant.io/docs/dcql-overview.md`); each page's HTML also advertises this with a `<link rel="alternate" type="text/markdown">` tag. A single file with the full markdown of every page is at `https://docs.igrant.io/llms-full.txt`.

## Build with AI coding agents (Agent Skills)

Install the iGrant.io Agent Skills so an AI coding agent (Claude Code, Cursor, Codex, GitHub Copilot, or any SKILL.md agent) can build these integrations for you:

    npx skills add L3-iGrant/skills

Install a single workflow skill with `-s <skill>`, e.g. `npx skills add L3-iGrant/skills -s igrantio-dcql-trusted-authority`. Pages backed by a specific skill name it at the top of their markdown. See https://docs.igrant.io/docs/agent-skills/.

## About this site

- **URL**: https://docs.igrant.io
- **Documentation sections**:
  - Get Started: Developer guides and quickstarts
  - Concepts: Core concepts and architecture
  - Data Regulations: GDPR, eIDAS 2.0, Data Governance Act
  - Developer APIs: Complete API documentation

## Content Overview

This site contains 444 documentation files covering:

### Key Topics
- OpenID for Verifiable Credentials (OpenID4VC)
- Consent Management
- Data Exchange protocols
- EU Digital Identity Wallet
- eIDAS 2.0 regulations
- GDPR compliance

### API Documentation
- Consent Management APIs (Admin & Individual)
- OpenID4VC APIs (Issuer, Verifier, Holder)
- Aries Cloud Agent APIs
- Extension APIs

## All Documentation Files

- **Reference guide to EUDI Wallet abbreviations**: Browse common EUDI Wallet abbreviations and their meanings used across digital identity, verifiable credentials, and wallet documentation.
  URL: https://docs.igrant.io/docs/abbreviations/
  Markdown: https://docs.igrant.io/docs/abbreviations.md

- **Agent Skills catalogue**: Browse every iGrant.io Agent Skill for EUDI Wallet and European Business Wallet integrations, grouped by role, with what each skill does, its protocols and its dependencies.
  URL: https://docs.igrant.io/docs/agent-skills-catalogue/
  Markdown: https://docs.igrant.io/docs/agent-skills-catalogue.md

- **Agent Skills for EUDI Wallet integrations**: Install iGrant.io Agent Skills so your AI coding agent (Claude Code, Cursor, and any SKILL.md agent) can build EUDI Wallet and European Business Wallet integrations on the Organisation Wallet Suite and Consent Building Block.
  URL: https://docs.igrant.io/docs/agent-skills/
  Markdown: https://docs.igrant.io/docs/agent-skills.md

- **Get API Keys**: Get API keys and start integrating iGrant.io APIs for credential issuance, verification, consent management, and digital wallet workflows.
  URL: https://docs.igrant.io/docs/developer-apis/get-started/
  Markdown: https://docs.igrant.io/docs/developer-apis/get-started.md

- **Developer APIs**: Explore iGrant.io developer APIs for OpenID4VC credential issuance and verification, consent management, and digital wallet integration.
  URL: https://docs.igrant.io/docs/developer-apis/
  Markdown: https://docs.igrant.io/docs/developer-apis.md

- **Set up webhooks for OpenID4VC integrations**: Understand how to configure webhooks in OpenID4VC workflows to manage real‑time events like credential issuance, updates, and verification responses.
  URL: https://docs.igrant.io/docs/openid4vc-webhooks/
  Markdown: https://docs.igrant.io/docs/openid4vc-webhooks.md

- **Q1 2026 (January - March)**: Product updates for the Organisation Wallet Suite and Data Wallet in Q1 2026.
  URL: https://docs.igrant.io/docs/changelog/2026-q1/
  Markdown: https://docs.igrant.io/docs/changelog/2026-q1.md

- **Q2 2026 (April - June)**: Product updates for the Organisation Wallet Suite and Data Wallet in Q2 2026.
  URL: https://docs.igrant.io/docs/changelog/2026-q2/
  Markdown: https://docs.igrant.io/docs/changelog/2026-q2.md

- **Q3 2026 (July - September)**: Product updates for the Organisation Wallet Suite and Data Wallet in Q3 2026.
  URL: https://docs.igrant.io/docs/changelog/2026-q3/
  Markdown: https://docs.igrant.io/docs/changelog/2026-q3.md

- **Get consent record**: This endpoint is used to get a single consent record by ID in an organisation defined in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/audit-consent-record-read
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/audit-consent-record-read.md

- **Fetch all data agreements**: This endpoint is used to fetch all data agreements defined in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/audit-data-agreement-list
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/audit-data-agreement-list.md

- **Fetch all consent records**: This endpoint is used to fetch all consent records with pagination for individuals in an organisation defined in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/audit-data-agreement-records-list
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/audit-data-agreement-records-list.md

- **Get data agreement**: This endpoint is used to fetch a single data agreement for audit purposes, e.g. by an external third party.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/audit-read-record
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/audit-read-record.md

- **Create data agreement**: This endpoint creates a data agreement for an organisation.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-create-agreement
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-create-agreement.md

- **Create individual**: This endpoint creates an individual for an organisation in the consent building block. This is used to onboard existing or new users.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-create-individual
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-create-individual.md

- **Create data policy**: This endpoint creates a new data policy that can be reused as global parameter across all newly crearted data agremements.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-create-policy
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-create-policy.md

- **Create webhook**: This endpoint creates a webhook. The webhook sends the events that you subscribe to, to an external IT system. The payload URL must start with `http://` or `https://`, and it must be unique for the organisation. Subscribe to a minimum of 1 event type.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-create-webhook
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-create-webhook.md

- **Delete data agreement**: This endpoint allows the admin to delete all revisions of a chosen data agreement defined earlier in an organisation.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-delete-agreement
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-delete-agreement.md

- **Delete data policy**: This endpoint is used to delete an existing data policy.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-delete-policy
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-delete-policy.md

- **Delete webhook**: This endpoint deletes a webhook. The server disables the webhook and marks it as deleted. After the delete, the webhook sends no more events, and the other webhook endpoints do not find it. The response contains the webhook in its final state.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-delete-webhook
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-delete-webhook.md

- **List data agreement revisions**: This endpoint lists all revisions of a data agreement defined earlier in an organisation.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-list-agreement-revisions
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-list-agreement-revisions.md

- **List all data agreements**: This endpoint allows the admin to read all data agreements and their revisions defined earlier in an organisation.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-list-agreement
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-list-agreement.md

- **Read data attributes**: This endpoint reads all data attrinbutes defined in a data agreement.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-list-data-attribute
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-list-data-attribute.md

- **List all individuals**: This endpoint is used to list all individuals in the organisation defined in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-list-individuals
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-list-individuals.md

- **List data policy revisions**: This endpoint reads all data policy revisions defined in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-list-policy-revisions
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-list-policy-revisions.md

- **List all data policies**: This endpoint reads all data policies defined in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-list-policy
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-list-policy.md

- **List all webhooks**: This endpoint lists all the webhooks of the organisation. Each item in the list also gives the result of the last payload delivery to the webhook. The server does not list deleted webhooks. Use the `offset` and `limit` query parameters to page through the list.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-list-webhooks
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-list-webhooks.md

- **Read data agreement**: This endpoint allows the admin to view the latest data agreement defined
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-read-agreement
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-read-agreement.md

- **Read individual**: This endpoint is used to read an individual info defined for an organisation in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-read-individual
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-read-individual.md

- **Read data policy**: This endpoint reads a data policy with the latest revision info.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-read-policy
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-read-policy.md

- **Read webhook event types**: This endpoint lists all the webhook event types that you can subscribe to. Use these values in the `subscribedEvents` field when you create or update a webhook. The list is the same for all organisations.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-read-webhook-event-types
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-read-webhook-event-types.md

- **Read webhook**: This endpoint reads 1 webhook of the organisation by its ID.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-read-webhook
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-read-webhook.md

- **Update data agreement**: This endpoint allows the admin to update the latest data agreement defined earlier in an organisation. It also returns the updated revision number.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-update-agreement
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-update-agreement.md

- **Update data attribute**: This endpoint updates an existing data attribute defined in a data agreement. If updated, the associated data agreement revision is incremented automatically.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-update-data-attribute
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-update-data-attribute.md

- **Update individual**: This endpoint is used to udpated an individual for an organisation defined in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-update-individual
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-update-individual.md

- **Update data policy**: This endpoint is used to update and existing data policy. It updates the existing and returns the updated version info. Updating a data policy does not affect existing data agreements.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-update-policy
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-update-policy.md

- **Update webhook**: This endpoint updates a webhook. The request body replaces the payload URL, the content type, the subscribed events, the disabled flag, the secret key and the SSL verification flag of the webhook. The payload URL must start with `http://` or `https://`, and no other webhook of the organisation can use it. Subscribe to a minimum of 1 event type.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/config-update-webhook
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/config-update-webhook.md

- **List all webhook content types**: This endpoint lists the payload content types that a webhook can use. Use one of these values in the `contentType` field when you create or update a webhook. The server posts the payload as a JSON body for `application/json`. For `application/x-www-form-urlencoded`, the server makes a string of the payload and posts it as a form under the `payload` key. Note the capital `C` in the `ContentTypes` response field. The order of the values changes between calls.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/get-webhook-payload-content-types
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/get-webhook-payload-content-types.md

- **iGrant.io API documentation**: iGrant.io (™) is a Swedish data exchange and verification service provider. It uses self-sovereign identity, verifiable credentials, a digital wallet and solid pod technologies, enabling a new level of interoperability and automating compliance with data regulations in a fully auditable manner.
  URL: https://docs.igrant.io/docs/consent-management-admin-api/igrant-io-api-documentation
  Markdown: https://docs.igrant.io/docs/consent-management-admin-api/igrant-io-api-documentation.md

- **Create individual**: This endpoint creates an individual for an organisation in the consent building block. This is used to onboard existing or new users.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/config-create-policy
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/config-create-policy.md

- **Read individual**: This endpoint is used to read the individuals information as defined by the organisation in the consent building block. This is used in privacy dashboard where the individuals can mark their consents, sign data agreement etc.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/config-read-individual
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/config-read-individual.md

- **Update individual**: This endpoint is used to udpated an individual for an organisation defined in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/config-update-individual
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/config-update-individual.md

- **iGrant.io API documentation**: iGrant.io (™) is a Swedish data exchange and verification service provider. It uses self-sovereign identity, verifiable credentials, a digital wallet and solid pod technologies, enabling a new level of interoperability and automating compliance with data regulations in a fully auditable manner.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/igrant-io-api-documentation
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/igrant-io-api-documentation.md

- **List data attributes**: This endpoint is used to read the data attributes defined in a particular data agreement revision.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-agreement-data-read
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-agreement-data-read.md

- **List all active data agreements**: This endpoint is used to list all active data agreements by the organisation in consent building block. The results are returned with pagination.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-agreement-list
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-agreement-list.md

- **Read data agreement**: This endpoint is used to read the data agreement defined by the organisation in consent building block.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-agreement-read
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-agreement-read.md

- **Create consent record and signature**: This endpoint is used to create a consent record and signature object. This returns the same objects with the PK defined.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-create-individual-consent-record-and-signature
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-create-individual-consent-record-and-signature.md

- **Create draft consent record**: This endpoint is used to create a draft (unsaved) consent record and signature object (without a PKI) for a data agreement.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-create-individual-consent-record-draft
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-create-individual-consent-record-draft.md

- **Creates blank signature**: This endpoint is used to create a blank signature object for the consent record for an individual in an organiation defined in the consent building block. Creates and returns a blank Signature object for the consent record.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-create-individual-consent-record-signature
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-create-individual-consent-record-signature.md

- **Create consent record**: This endpoint is used to create a consent record when an individial records their consent (e.g. in the privacy dashboard) against a data agreement.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-create-individual-consent-record
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-create-individual-consent-record.md

- **Delete all consent records**: This endpoint is used to delete all consent records for an individual belonging to an organiation defined in the consent building block. This could be used, for example to exercise digital rights (Right to be forgotten) and deletes all consent records that shall not be retained and have a forgettable data agreement. This may also delete an unsigned consent record, for instance in cases where the user exits the signing process.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-delete-all-records
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-delete-all-records.md

- **List consent record history**: This endpoint is used to list all consent record history existing for an individual in an organisation defined in the consent building block. The response is paginated.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-list-data-agreement-record-history
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-list-data-agreement-record-history.md

- **List all consent records**: This endpoint is used to list all consent records existing for a data agreement for an organisation defined in the consent building block. The response is paginated.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-list-individual-agreement-consent-record-list
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-list-individual-agreement-consent-record-list.md

- **List all consent records for individual**: This endpoint is used to list all consent records for an individual belonging to an organiation defined in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-list-individual-consent-record-list
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-list-individual-consent-record-list.md

- **List all individuals**: lists individuals in the system This endpoint is used to list all individuals in the organisation defined in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-list-individuals
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-list-individuals.md

- **Read data policy**: This endpoint is used to read latest version of data policy defined in the organisation in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-policy-read
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-policy-read.md

- **Read data sharing UI**: This endpoint is used to render the data sharing UI during a data exchange as defined by a (data source) organisation in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-read-data-sharing-ui
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-read-data-sharing-ui.md

- **Read IdP details**: This endpoint is used to read the IdP details configured by the organisation in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-read-idp
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-read-idp.md

- **Read consent record**: This endpoint is used to read a consent record for an individial for a chosen data agreement. There should be one unambiguous consent record for an individual.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-read-individual-record-read
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-read-individual-record-read.md

- **Read organisation cover image**: This endpoint is used to retrieve the existing cover image for the organisation. The cover image is used to display in the privacy dashboard.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-read-organisation-cover-image
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-read-organisation-cover-image.md

- **Read organisation image**: This endpoint is used to read an organisation image as defined in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-read-organisation-image
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-read-organisation-image.md

- **Read organisation logo image**: Read organisation logo image This endpoint is used to retrieve the existing logo image for the organisation. The logo image is used to display in the privacy dashboard as well in data sharing UIs.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-read-organisation-logo-image
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-read-organisation-logo-image.md

- **Read organisation**: This endpoint is used to read the organisation information as configured by the organisation in the consent building block. This is used, for e.g., in the privacy dashboard.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-read-organisation
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-read-organisation.md

- **Update consent record signature**: This endpoint is used to update a signature object for the consent record for an individual in an organiation defined in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-update-individual-consent-record-signature
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-update-individual-consent-record-signature.md

- **Update consent record**: This endpoint is used to update an existing consent record for a given data agreement for an organiation defined in the consent building block. Note that updating a signed consent record invalidates its earlier signature.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-update-individual-consent-record
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-update-individual-consent-record.md

- **Read latest consent record**: This endpoint is used to read the latest consent record for an organisation in the consent building block.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-verification-agreement-consent-record-read
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-verification-agreement-consent-record-read.md

- **List all data agreements**: This endpoint is used to list all data agreements available for an organisation defined in the consent building block. The results are paginated.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-verification-agreement-list
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-verification-agreement-list.md

- **List all consent records**: This endpoint is used to list all consent records available for an organisation defined in the consent building block. The results are paginated.
  URL: https://docs.igrant.io/docs/consent-management-individual-api/service-verification-consent-record-list
  Markdown: https://docs.igrant.io/docs/consent-management-individual-api/service-verification-consent-record-list.md

- **Create webhook**: This endpoint creates a webhook. The webhook sends the events that you subscribe to, to an external IT system. The payload URL must start with `http://` or `https://`, and it must be unique for the organisation. Subscribe to a minimum of 1 event type.
  URL: https://docs.igrant.io/docs/datamarketplace-api/config-create-webhook
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/config-create-webhook.md

- **Delete webhook**: This endpoint deletes a webhook. The server disables the webhook and marks it as deleted. After the delete, the webhook sends no more events, and the other webhook endpoints do not find it. The response contains the webhook in its final state.
  URL: https://docs.igrant.io/docs/datamarketplace-api/config-delete-webhook
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/config-delete-webhook.md

- **List all webhooks**: This endpoint lists all the webhooks of the organisation. Each item in the list also gives the result of the last payload delivery to the webhook. The server does not list deleted webhooks. Use the `offset` and `limit` query parameters to page through the list.
  URL: https://docs.igrant.io/docs/datamarketplace-api/config-list-webhooks
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/config-list-webhooks.md

- **Read webhook event types**: This endpoint lists all the webhook event types that you can subscribe to. Use these values in the `subscribedEvents` field when you create or update a webhook. The list is the same for all organisations.
  URL: https://docs.igrant.io/docs/datamarketplace-api/config-read-webhook-event-types
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/config-read-webhook-event-types.md

- **Read webhook**: This endpoint reads 1 webhook of the organisation by its ID.
  URL: https://docs.igrant.io/docs/datamarketplace-api/config-read-webhook
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/config-read-webhook.md

- **Update webhook**: This endpoint updates a webhook. The request body replaces the payload URL, the content type, the subscribed events, the disabled flag, the secret key and the SSL verification flag of the webhook. The payload URL must start with `http://` or `https://`, and no other webhook of the organisation can use it. Subscribe to a minimum of 1 event type.
  URL: https://docs.igrant.io/docs/datamarketplace-api/config-update-webhook
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/config-update-webhook.md

- **Create Base Configurations**: Creates Base Configurations related to a Data Marketplace.
  URL: https://docs.igrant.io/docs/datamarketplace-api/create-base-configurations
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/create-base-configurations.md

- **Create Data Disclosure Agreement Template**: Creates a Data Disclosure Agreement Template.
  URL: https://docs.igrant.io/docs/datamarketplace-api/create-data-disclosure-agreement-template
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/create-data-disclosure-agreement-template.md

- **Create OAuth2.0 Client**: Creates an OAuth2 Client for use with a Data Marketplace.
  URL: https://docs.igrant.io/docs/datamarketplace-api/create-o-auth-2-0-client
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/create-o-auth-2-0-client.md

- **Delete Base Configurations**: Deletes Base Configurations related to a Data Marketplace.
  URL: https://docs.igrant.io/docs/datamarketplace-api/delete-base-configurations
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/delete-base-configurations.md

- **Delete Data Disclosure Agreement Template**: Deletes a Data Disclosure Agreement Template.
  URL: https://docs.igrant.io/docs/datamarketplace-api/delete-data-disclosure-agreement-template
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/delete-data-disclosure-agreement-template.md

- **Delete OAuth2.0 Client**: Deletes a Data Marketplace related OAuth2 Client.
  URL: https://docs.igrant.io/docs/datamarketplace-api/delete-o-auth-2-0-client
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/delete-o-auth-2-0-client.md

- **List all webhook content types**: This endpoint lists the payload content types that a webhook can use. Use one of these values in the `contentType` field when you create or update a webhook. The server posts the payload as a JSON body for `application/json`. For `application/x-www-form-urlencoded`, the server makes a string of the payload and posts it as a form under the `payload` key. Note the capital `C` in the `ContentTypes` response field. The order of the values changes between calls.
  URL: https://docs.igrant.io/docs/datamarketplace-api/get-webhook-payload-content-types
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/get-webhook-payload-content-types.md

- **iGrant.io API documentation**: iGrant.io (™) is a Swedish data exchange and verification service provider. It uses self-sovereign identity, verifiable credentials, a digital wallet and solid pod technologies, enabling a new level of interoperability and automating compliance with data regulations in a fully auditable manner.
  URL: https://docs.igrant.io/docs/datamarketplace-api/igrant-io-api-documentation
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/igrant-io-api-documentation.md

- **List all Data Disclosure Agreement Records**: Lists all Data Disclosure Agreement Records for the organisation, depending on  the role of the organisation for the record, data_source or  data_using_service.
  URL: https://docs.igrant.io/docs/datamarketplace-api/list-all-data-disclosure-agreement-records
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/list-all-data-disclosure-agreement-records.md

- **List all revisions for all Data Disclosure Agreement Records**: Lists all revisions of Data Disclosure Agreement Records, optionally filtered  by organisation role and/or DDA Template Revision.
  URL: https://docs.igrant.io/docs/datamarketplace-api/list-all-revisions-for-all-data-disclosure-agreement-records
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/list-all-revisions-for-all-data-disclosure-agreement-records.md

- **List Data Disclosure Agreement Record Revisions**: Lists Data Disclosure Agreement Record Revisions for a specific record.
  URL: https://docs.igrant.io/docs/datamarketplace-api/list-data-disclosure-agreement-record-revisions
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/list-data-disclosure-agreement-record-revisions.md

- **List Data Disclosure Agreement Template Revisions**: Lists Data Disclosure Agreement Template Revisions.
  URL: https://docs.igrant.io/docs/datamarketplace-api/list-data-disclosure-agreement-template-revisions
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/list-data-disclosure-agreement-template-revisions.md

- **List Data Disclosure Agreement Templates**: Lists Data Disclosure Agreement Templates.
  URL: https://docs.igrant.io/docs/datamarketplace-api/list-data-disclosure-agreement-templates
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/list-data-disclosure-agreement-templates.md

- **List OAuth2.0 Clients**: Lists OAuth2 Clients for use with a Data Marketplace.
  URL: https://docs.igrant.io/docs/datamarketplace-api/list-o-auth-2-0-clients
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/list-o-auth-2-0-clients.md

- **List Pull Data Records**: Lists Pull Data Records, optionally filtered by Data Disclosure Agreement  Template (Revision ID) and/or Data Disclosure Agreement Record (Revision ID).
  URL: https://docs.igrant.io/docs/datamarketplace-api/list-pull-data-records
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/list-pull-data-records.md

- **List Validate Access Records**: Lists Validate Access Records which show every time an access token was checked at the token verification and authorisation endpoint (validate access).
  URL: https://docs.igrant.io/docs/datamarketplace-api/list-validate-access-records
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/list-validate-access-records.md

- **Pull Data Endpoint**: The Pull Data endpoint allows a Data Using Service to Pull Data according to a  specific Data Disclosure Agreement record signed by themselves and a Data  Source, either anonymously or for a specific individual.
  URL: https://docs.igrant.io/docs/datamarketplace-api/pull-data-endpoint
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/pull-data-endpoint.md

- **Read Access Point Configuration**: Reads Access Point Configuration of the organisation.
  URL: https://docs.igrant.io/docs/datamarketplace-api/read-access-point-configuration
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/read-access-point-configuration.md

- **Read Base Configurations**: Reads Base Configurations related to a Data Marketplace.
  URL: https://docs.igrant.io/docs/datamarketplace-api/read-base-configurations
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/read-base-configurations.md

- **Read Data Disclosure Agreement Record Revision**: Reads a Data Disclosure Agreement Record Revision.
  URL: https://docs.igrant.io/docs/datamarketplace-api/read-data-disclosure-agreement-record-revision
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/read-data-disclosure-agreement-record-revision.md

- **Read Data Disclosure Agreement Record**: Reads a Data Disclosure Agreement Record.
  URL: https://docs.igrant.io/docs/datamarketplace-api/read-data-disclosure-agreement-record
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/read-data-disclosure-agreement-record.md

- **Read Data Disclosure Agreement Template Revision**: Reads a Data Disclosure Agreement Template Revision.
  URL: https://docs.igrant.io/docs/datamarketplace-api/read-data-disclosure-agreement-template-revision
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/read-data-disclosure-agreement-template-revision.md

- **Read Data Disclosure Agreement Template**: Reads a Data Disclosure Agreement Template.
  URL: https://docs.igrant.io/docs/datamarketplace-api/read-data-disclosure-agreement-template
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/read-data-disclosure-agreement-template.md

- **Read OAuth2.0 Client**: Reads a Data Marketplace related OAuth2 Client.
  URL: https://docs.igrant.io/docs/datamarketplace-api/read-o-auth-2-0-client
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/read-o-auth-2-0-client.md

- **Read Pull Data Record**: Reads a specific Pull Data Record.
  URL: https://docs.igrant.io/docs/datamarketplace-api/read-pull-data-record
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/read-pull-data-record.md

- **Read Validate Access Record**: Reads a specific Validate Access Record.
  URL: https://docs.igrant.io/docs/datamarketplace-api/read-validate-access-record
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/read-validate-access-record.md

- **Update Base Configurations**: Updates Base Configurations related to a Data Marketplace.
  URL: https://docs.igrant.io/docs/datamarketplace-api/update-base-configurations
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/update-base-configurations.md

- **Update Data Disclosure Agreement Template**: Updates a Data Disclosure Agreement Template. Partial updates are supported.  If publishing (set active=true), purpose,  purpose description, and lawful basis must either be provided or already be present from the draft version.  If changing the Data Agreement, all three fields must be provided (ID,  revision ID, and revision hash).
  URL: https://docs.igrant.io/docs/datamarketplace-api/update-data-disclosure-agreement-template
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/update-data-disclosure-agreement-template.md

- **Update OAuth2.0 Client**: Updates an OAuth2 Client for use with a Data Marketplace.
  URL: https://docs.igrant.io/docs/datamarketplace-api/update-o-auth-2-0-client
  Markdown: https://docs.igrant.io/docs/datamarketplace-api/update-o-auth-2-0-client.md

- **Access Point Configurations**: The Access Point Configuration Metadata endpoint for an organisations capabilities in regards to a Data Marketplace.
  URL: https://docs.igrant.io/docs/datamarketplace-individual-api/access-point-configurations
  Markdown: https://docs.igrant.io/docs/datamarketplace-individual-api/access-point-configurations.md

- **Authorisation Server Metadata**: The Authorisation Server Metadata endpoint for an organisations capabilities in regards to a Data Marketplace.
  URL: https://docs.igrant.io/docs/datamarketplace-individual-api/authorisation-server-metadata
  Markdown: https://docs.igrant.io/docs/datamarketplace-individual-api/authorisation-server-metadata.md

- **Get Individual is Opted-In**: Checks whether the individual is opted-in to the underlying  Data Agreement within the specified Data Disclosure Agreement Record.
  URL: https://docs.igrant.io/docs/datamarketplace-individual-api/get-individual-is-opted-in
  Markdown: https://docs.igrant.io/docs/datamarketplace-individual-api/get-individual-is-opted-in.md

- **iGrant.io API documentation**: iGrant.io (™) is a Swedish data exchange and verification service provider. It uses self-sovereign identity, verifiable credentials, a digital wallet and solid pod technologies, enabling a new level of interoperability and automating compliance with data regulations in a fully auditable manner.
  URL: https://docs.igrant.io/docs/datamarketplace-individual-api/igrant-io-api-documentation
  Markdown: https://docs.igrant.io/docs/datamarketplace-individual-api/igrant-io-api-documentation.md

- **List all Data Disclosure Agreement Records**: Lists all Data Disclosure Agreement Records for the organisation, depending on  the role of the organisation for the record, data_source or  data_using_service.
  URL: https://docs.igrant.io/docs/datamarketplace-individual-api/list-all-data-disclosure-agreement-records
  Markdown: https://docs.igrant.io/docs/datamarketplace-individual-api/list-all-data-disclosure-agreement-records.md

- **List Opted-In Individuals**: Lists individuals that have opted-in to the underlying Data Agreement within the specified Data Disclosure Agreement Record.
  URL: https://docs.igrant.io/docs/datamarketplace-individual-api/list-opted-in-individuals
  Markdown: https://docs.igrant.io/docs/datamarketplace-individual-api/list-opted-in-individuals.md

- **Pull Data Endpoint**: The Pull Data endpoint allows a Data Using Service to Pull Data according to a  specific Data Disclosure Agreement record signed by themselves and a Data  Source, either anonymously or for a specific individual.
  URL: https://docs.igrant.io/docs/datamarketplace-individual-api/pull-data-endpoint
  Markdown: https://docs.igrant.io/docs/datamarketplace-individual-api/pull-data-endpoint.md

- **Token Verification and Authorisation**: The Token Verification and Authorisation endpoint for an organisation in  regards to a Data Marketplace. An Access Token issued as a result of a Pull-Data request can be verified here, and an authorisation decision can be made  against the requested resource (defined by OpenAPI method and path). The  resource is checked against the OpenAPI specification of the underlying  Data Agreement within the Data Disclosure Agreement Records Template  connected to the Access Token.
  URL: https://docs.igrant.io/docs/datamarketplace-individual-api/token-verification-and-authorisation
  Markdown: https://docs.igrant.io/docs/datamarketplace-individual-api/token-verification-and-authorisation.md

- **DCQL: Claim Sets (Selective Disclosure)**: DCQL claim sets for selective disclosure, requesting preferred claims with fallback alternatives.
  URL: https://docs.igrant.io/docs/dcql-2-4-2-claim-set-age-verification
  Markdown: https://docs.igrant.io/docs/dcql-2-4-2-claim-set-age-verification.md

- **DCQL: Credential Sets (Alternatives)**: DCQL credential sets allowing a verifier to accept any one of several alternative credential types in a single query.
  URL: https://docs.igrant.io/docs/dcql-2-4-3-credential-set-proof-of-identity-alternatives/
  Markdown: https://docs.igrant.io/docs/dcql-2-4-3-credential-set-proof-of-identity-alternatives.md

- **DCQL: Combined Credential Sets**: DCQL combined credential sets requiring multiple mandatory credential groups, each with alternative options.
  URL: https://docs.igrant.io/docs/dcql-2-4-4-kyc-request-photo-id-address-proof/
  Markdown: https://docs.igrant.io/docs/dcql-2-4-4-kyc-request-photo-id-address-proof.md

- **DCQL: Mandatory and Optional Sets**: DCQL credential sets mixing mandatory and optional groups with selective claim disclosure in a single query.
  URL: https://docs.igrant.io/docs/dcql-2-4-5-student-transport-pass/
  Markdown: https://docs.igrant.io/docs/dcql-2-4-5-student-transport-pass.md

- **DCQL: Multiple Credential Instances**: DCQL multiple field for requesting several instances of the same credential type in a single verification flow.
  URL: https://docs.igrant.io/docs/dcql-2-4-6-loan-application-multiple-bank-statements/
  Markdown: https://docs.igrant.io/docs/dcql-2-4-6-loan-application-multiple-bank-statements.md

- **DCQL: Values Constraint**: DCQL values constraint for restricting accepted claim values to a predefined allowed list.
  URL: https://docs.igrant.io/docs/dcql-2-4-7-delivery-service-restricted-postal-codes/
  Markdown: https://docs.igrant.io/docs/dcql-2-4-7-delivery-service-restricted-postal-codes.md

- **DCQL: Trusted Authorities**: DCQL credential query filtered by trusted authorities (EU Trust List, EBSI, OpenID Federation) using iGrant.io Digital Wallets.
  URL: https://docs.igrant.io/docs/dcql-basic-credential-query-with-trusted-authority/
  Markdown: https://docs.igrant.io/docs/dcql-basic-credential-query-with-trusted-authority.md

- **DCQL (Digital Credential Query Language)**: Introduction to the Digital Credential Query Language (DCQL) as defined in OpenID4VP 1.0, with a summary of its building blocks and developer workflow examples.
  URL: https://docs.igrant.io/docs/dcql-overview/
  Markdown: https://docs.igrant.io/docs/dcql-overview.md

- **Trust List Certificate Generator**: Generate a test X.509 certificate from a CSR and your organisation details - a root CA for issuers and wallet providers, or an access certificate for relying parties - ready to register in the trust list.
  URL: https://docs.igrant.io/docs/devtools-certificate-generator/
  Markdown: https://docs.igrant.io/docs/devtools-certificate-generator.md

- **Online Digital Certificate Viewer**: Parse, analyze and validate X.509 certificates in PEM format. View details, check validity, and verify signatures.
  URL: https://docs.igrant.io/docs/devtools-certificate-viewer/
  Markdown: https://docs.igrant.io/docs/devtools-certificate-viewer.md

- **JSON Schema Validator**: JSON Schema Validator for developers
  URL: https://docs.igrant.io/docs/devtools-json-schema-validator/
  Markdown: https://docs.igrant.io/docs/devtools-json-schema-validator.md

- **Decode JWT and SD-JWT VC tokens**: Free online JWT and SD-JWT VC decoder. Inspect headers, payloads, disclosures and key-binding JWTs, then verify the signature with an issuer key auto-derived from header.jwk, x5c, did:key or did:jwk.
  URL: https://docs.igrant.io/docs/devtools-jwt-decoder/
  Markdown: https://docs.igrant.io/docs/devtools-jwt-decoder.md

- **Decode mdoc CBOR (ISO/IEC 18013-5 IssuerSigned)**: Free online mdoc CBOR decoder. Inspect IssuerSigned structures, COSE_Sign1 issuer authentication, the Mobile Security Object, namespaces, and the issuer x5chain certificate.
  URL: https://docs.igrant.io/docs/devtools-mdoc-decoder/
  Markdown: https://docs.igrant.io/docs/devtools-mdoc-decoder.md

- **EUDI & Business Wallet Developer Debug Tools**: Debugging tools for issuers, holders, and verifiers working with EU Digital Identity (EUDI) Wallets and the European Business Wallet under eIDAS 2.0.
  URL: https://docs.igrant.io/docs/devtools-overview/
  Markdown: https://docs.igrant.io/docs/devtools-overview.md

- **Decode QR Codes with developer tools**: See how to decode QR codes to extract credential data securely, supporting verification workflows in digital identity implementations.
  URL: https://docs.igrant.io/docs/devtools-qrcode-decoder/
  Markdown: https://docs.igrant.io/docs/devtools-qrcode-decoder.md

- **Generate QR Codes with developer tools**: Learn how to create and use QR codes for credential sharing and verification in digital identity workflows using the developer tools.
  URL: https://docs.igrant.io/docs/devtools-qrcode-generator/
  Markdown: https://docs.igrant.io/docs/devtools-qrcode-generator.md

- **Admin login**: Authenticates an administrative user by validating the provided username and password. Upon successful authentication, a pair of JSON Web Tokens (JWT) - access and refresh - are issued, along with basic user details. These tokens are required for accessing protected endpoints within the system.
  URL: https://docs.igrant.io/docs/drv-bund-api/admin-login
  Markdown: https://docs.igrant.io/docs/drv-bund-api/admin-login.md

- **DRV Bund Controller API Documentation**: iGrant.io (™) is a Swedish data exchange and verification service provider. It uses self-sovereign identity, verifiable credentials, a digital wallet and solid pod technologies, enabling a new level of interoperability and automating compliance with data regulations in a fully auditable manner.
  URL: https://docs.igrant.io/docs/drv-bund-api/drv-bund-controller-api-documentation
  Markdown: https://docs.igrant.io/docs/drv-bund-api/drv-bund-controller-api-documentation.md

- **DRV Bund Controller API Documentation**: Overview of the DRV Bund Controller API powered by Organisation Wallet Suite APIs
  URL: https://docs.igrant.io/docs/drv-bund-api/overview
  Markdown: https://docs.igrant.io/docs/drv-bund-api/overview.md

- **Refresh access token**: Allows clients to obtain a new access token using a previously issued refresh token. This mechanism supports session continuation without requiring the user to re-authenticate.
  URL: https://docs.igrant.io/docs/drv-bund-api/refresh-access-token
  Markdown: https://docs.igrant.io/docs/drv-bund-api/refresh-access-token.md

- **Upload EHIC**: Submits electronic European Health Insurance Card (eEHIC) data for credential issuance. Each request may include multiple data entries. The system validates and processes the entries and issues the corresponding verifiable credentials.
  URL: https://docs.igrant.io/docs/drv-bund-api/upload-ehic
  Markdown: https://docs.igrant.io/docs/drv-bund-api/upload-ehic.md

- **Upload PDA1**: Processes submission of ESSPASS Portable Document A1 data for credential issuance. The request must include detailed personal, legal, employment, and organisational information structured across multiple sections.
  URL: https://docs.igrant.io/docs/drv-bund-api/upload-pda-1
  Markdown: https://docs.igrant.io/docs/drv-bund-api/upload-pda-1.md

- **EUDI Wallet Pilots and Production Deployments**: Real-world EUDI Wallet pilots and production deployments delivered by iGrant.io, including the first live EUDI Wallet payments at Banca Transilvania and Fast Ferries, the WE BUILD European Business Wallet pilot, CRANE PCP cross-border health data, ITU/GovStack Consent Building Block and EBSI conformance.
  URL: https://docs.igrant.io/docs/ecosystem-engagements/eudi-wallet-pilots-and-deployments
  Markdown: https://docs.igrant.io/docs/ecosystem-engagements/eudi-wallet-pilots-and-deployments.md

- **Interoperability & Compliance**: Interoperability achievements, compliance badges, ISO/IEC 27001:2022 certification, EWC RFC support, and standards contributions for the iGrant.io Organisation Wallet Suite.
  URL: https://docs.igrant.io/docs/ecosystem-engagements/interoperability-and-compliance
  Markdown: https://docs.igrant.io/docs/ecosystem-engagements/interoperability-and-compliance.md

- **WE BUILD Consortium: EUDI Wallet and European Business Wallet Large Scale Pilot**: iGrant.ios work in the WE BUILD Large-Scale Pilot for the EU Digital Identity Wallet and European Business Wallets, starting with verifiable eReceipts and account-to-account payments, alongside business registry, document signing and Qualified EAA use cases.
  URL: https://docs.igrant.io/docs/ecosystem-engagements/we-build-consortium
  Markdown: https://docs.igrant.io/docs/ecosystem-engagements/we-build-consortium.md

- **Consent Management Overview**: iGrant.io facilitates trusted data sharing and compliant data usage with consent management systems. Giving individuals control over their data.
  URL: https://docs.igrant.io/docs/consent-management-overview/
  Markdown: https://docs.igrant.io/docs/consent-management-overview.md

- **Consent Management APIs**: Get started with consent management APIs to create data agreements, manage consent records, and enable GDPR-compliant data sharing workflows.
  URL: https://docs.igrant.io/docs/consent-management-apis/
  Markdown: https://docs.igrant.io/docs/consent-management-apis.md

- **Consent Management SDKs**: Integrate the iGrant.io consent management Privacy Dashboard SDKs for Android, iOS, and cloud into your application.
  URL: https://docs.igrant.io/docs/consent-management-sdks/
  Markdown: https://docs.igrant.io/docs/consent-management-sdks.md

- **Consent Management Admin User Guide**: Learn how to configure and manage user consent, data agreements, and permissions using the Consent Management system for secure data sharing.
  URL: https://docs.igrant.io/docs/consent-management-admin-guide/
  Markdown: https://docs.igrant.io/docs/consent-management-admin-guide.md

- **Data Intermediation Service Provider APIs**: Integrate iGrant.io data intermediation APIs to enable secure, consent-based personal data exchange between organisations and individuals.
  URL: https://docs.igrant.io/docs/data-intermediation-service-provider-apis/
  Markdown: https://docs.igrant.io/docs/data-intermediation-service-provider-apis.md

- **Data Intermediation Service Provider Overview**: Understand how the Data Intermediation Service Provider facilitates secure data exchange between individuals and organisations with auditable consent.
  URL: https://docs.igrant.io/docs/data-intermediation-service-provider-overview/
  Markdown: https://docs.igrant.io/docs/data-intermediation-service-provider-overview.md

- **Data Wallet (UI) SDKs**: Integrate the Data Wallet UI SDKs for Android and iOS into your mobile application to enable secure credential storage and sharing.
  URL: https://docs.igrant.io/docs/data-wallet-sdks/
  Markdown: https://docs.igrant.io/docs/data-wallet-sdks.md

- **Data Wallet Features**: Review the main features of the Data Wallet, including secure storage, credential sharing, and privacy controls for digital identity management.
  URL: https://docs.igrant.io/docs/data-wallet-features/
  Markdown: https://docs.igrant.io/docs/data-wallet-features.md

- **Data Wallet (OpenID4VC) SDKs**: Integrate EUDI Wallet OpenID4VC SDKs for Android and iOS to enable credential issuance and verification using OpenID4VCI and OpenID4VP.
  URL: https://docs.igrant.io/docs/data-wallet-openID4vc-sdks/
  Markdown: https://docs.igrant.io/docs/data-wallet-openID4vc-sdks.md

- **Data Wallet Overview**: Learn how the Data Wallet enables individuals to securely store, manage, and share Verifiable Credentials for trusted digital identity interactions.
  URL: https://docs.igrant.io/docs/data-wallet-overview/
  Markdown: https://docs.igrant.io/docs/data-wallet-overview.md

- **Data Wallet - Try Out! **: Explore the interactive demo to experience how the Data Wallet stores and shares verifiable credentials for secure digital interactions.
  URL: https://docs.igrant.io/docs/data-wallet-tryitout/
  Markdown: https://docs.igrant.io/docs/data-wallet-tryitout.md

- **Organisation Wallet Suite Features**: Review key features of the Organisation Wallet Suite, including credential issuance, verification, and secure management for businesses and institutions.
  URL: https://docs.igrant.io/docs/organisation-wallet-features/
  Markdown: https://docs.igrant.io/docs/organisation-wallet-features.md

- **Explore documentation for EUDI Wallet integration**: Explore documentation for EUDI Wallet integration
  URL: https://docs.igrant.io/docs/
  Markdown: https://docs.igrant.io/docs.md

- **Age Verification**: Issue and verify EU age verification attestations (eu.europa.ec.av.1, ISO mdoc) with OpenID4VCI and OpenID4VP. Prove age over 18 without revealing identity.
  URL: https://docs.igrant.io/docs/eu-age-verification/
  Markdown: https://docs.igrant.io/docs/eu-age-verification.md

- **OpenID4VCI - Issue Credential (Deferred)**: Create credential definition and issue in-time credentials using OpenID for verifiable credentials (OpenID4VCI) issuance in deferred mode
  URL: https://docs.igrant.io/docs/openID4vci-issue-credential-deferred/
  Markdown: https://docs.igrant.io/docs/openID4vci-issue-credential-deferred.md

- **OpenID4VCI - Dynamic Credential Request**: Explore how OpenID4VCI enables dynamic credential requests, ensuring secure issuance and verification of verifiable credentials across digital identity systems.
  URL: https://docs.igrant.io/docs/openID4vci-issue-dynamic-credential-request/
  Markdown: https://docs.igrant.io/docs/openID4vci-issue-dynamic-credential-request.md

- **OpenID4VCI - Issue Credential (In-Time)**: Create credential definition and issue in-time credentials using OpenID for verifiable credentials issuance - Try OpenID4VCI with iGrant.io Digital Wallets.
  URL: https://docs.igrant.io/docs/openID4vci-issue-credential-intime/
  Markdown: https://docs.igrant.io/docs/openID4vci-issue-credential-intime.md

- **Organisation Wallet Suite - On-Premise Deployment Instructions**: Developer user guide for deploying the Organisation Wallet Suite using the official Helm chart.
  URL: https://docs.igrant.io/docs/organisation-wallet-on-premise-deployment/
  Markdown: https://docs.igrant.io/docs/organisation-wallet-on-premise-deployment.md

- **Organisation Wallet Suite Overview**: Learn how the Organisation Wallet Suite enables businesses to issue and verify Digital Credentials for secure, trusted online interactions.
  URL: https://docs.igrant.io/docs/organisation-wallet-overview/
  Markdown: https://docs.igrant.io/docs/organisation-wallet-overview.md

- **Passwordless Login with EUDI Wallets**: See how to enable passwordless authentication using the EUDI Wallet, improving security and user experience with Verifiable Credentials (VC).
  URL: https://docs.igrant.io/docs/eudi-passwordless-login-flow/
  Markdown: https://docs.igrant.io/docs/eudi-passwordless-login-flow.md

- **Payment Authenticator**: Follow the steps to issue verifiable payment wallet attestations using OpenID4VCI, enabling secure and trusted payment authentication workflows.
  URL: https://docs.igrant.io/docs/openID4vci-payment-wallet-attestation/
  Markdown: https://docs.igrant.io/docs/openID4vci-payment-wallet-attestation.md

- **OpenID4VP - Receive and Present Credential**: Learn how to receive and present Verifiable Credentials with OpenID4VP, enabling secure and privacy‑preserving data sharing in digital services.
  URL: https://docs.igrant.io/docs/openID4vp-receive-and-present-credentials/
  Markdown: https://docs.igrant.io/docs/openID4vp-receive-and-present-credentials.md

- **OpenID4VC - Receive and Store Credential**: Step‑by‑step guide to receiving and storing Verifiable Credentials using OpenID4VC flows within the Data Wallet for secure digital interactions.
  URL: https://docs.igrant.io/docs/openID4vc-receive-and-store-credential/
  Markdown: https://docs.igrant.io/docs/openID4vc-receive-and-store-credential.md

- **Verify Credentials with the DC API on Android (Chrome)**: Verify credentials in Chrome on Android using the Digital Credentials API, with Credential Manager picking the wallet over OpenID4VP or ISO 18013-7.
  URL: https://docs.igrant.io/docs/openID4vc-send-verify-credentials-dcapi-android/
  Markdown: https://docs.igrant.io/docs/openID4vc-send-verify-credentials-dcapi-android.md

- **Verify Credentials with the DC API on iOS (Safari)**: Request credentials in Safari on iPhone and iPad over ISO 18013-7 Annex C, same device or by scanning a desktop QR code, and verify the mdoc response.
  URL: https://docs.igrant.io/docs/openID4vc-send-verify-credentials-dcapi-ios/
  Markdown: https://docs.igrant.io/docs/openID4vc-send-verify-credentials-dcapi-ios.md

- **Digital Credentials API (DC API) - Overview**: An introduction to the W3C Digital Credentials API (DC API), how it works in the browser, what iGrant.io has implemented for send and verify, and the practical findings and limitations to plan around.
  URL: https://docs.igrant.io/docs/openID4vc-dcapi-overview/
  Markdown: https://docs.igrant.io/docs/openID4vc-dcapi-overview.md

- **Verify Credentials with OpenID4VP**: Step-by-step OpenID4VP verification: get an API key, build a presentation definition, generate the QR request, and validate the returned presentation, with code.
  URL: https://docs.igrant.io/docs/openID4vc-send-verify-credentials/
  Markdown: https://docs.igrant.io/docs/openID4vc-send-verify-credentials.md

- **Payment Data Confirmation**: Learn how to issue and confirm payment‑related Verifiable Credentials with OpenID4VCI, supporting secure transactions and data validation processes.
  URL: https://docs.igrant.io/docs/openID4vci-payment-data-confirmation/
  Markdown: https://docs.igrant.io/docs/openID4vci-payment-data-confirmation.md

- **Platform Admin Guide**: Administration guide for the iGrant.io platform.
  URL: https://docs.igrant.io/docs/platform-admin-guide/
  Markdown: https://docs.igrant.io/docs/platform-admin-guide.md

- **Sandbox Organisations**: Create isolated test environments to simulate multi-party credential ecosystems
  URL: https://docs.igrant.io/docs/sandbox-organisations/
  Markdown: https://docs.igrant.io/docs/sandbox-organisations.md

- **European Business Wallet Owner ID (EBWOID)**: Issue European Business Wallet Owner ID (EBWOID) credentials for organisations using OpenID4VCI. Previously known as Legal Person Identification Data (LPID).
  URL: https://docs.igrant.io/docs/european-business-wallet-owner-id/
  Markdown: https://docs.igrant.io/docs/european-business-wallet-owner-id.md

- **Account Information Access**: Request consented access to a customers payment account information using an SCA Attestation presented from their EUDI Wallet.
  URL: https://docs.igrant.io/docs/extensions/account-information-access
  Markdown: https://docs.igrant.io/docs/extensions/account-information-access.md

- **Age Verification**: Verify customer age using digital credentials presented from an EUDI Wallet
  URL: https://docs.igrant.io/docs/extensions/age-verification
  Markdown: https://docs.igrant.io/docs/extensions/age-verification.md

- **Document Signing**: Sign PDF documents using a Qualified Electronic Signature from an EUDI Wallet
  URL: https://docs.igrant.io/docs/extensions/document-signing
  Markdown: https://docs.igrant.io/docs/extensions/document-signing.md

- **Extensions**: Pre-built extensions for the Organisation Wallet Suite that add turnkey verification, authentication, and signing capabilities using EUDI Wallets.
  URL: https://docs.igrant.io/docs/extensions/overview
  Markdown: https://docs.igrant.io/docs/extensions/overview.md

- **Know Your Customer (KYC)**: Verify customer identity using digital credentials presented from an EUDI Wallet
  URL: https://docs.igrant.io/docs/extensions/know-your-customer
  Markdown: https://docs.igrant.io/docs/extensions/know-your-customer.md

- **Passwordless Login**: Enable passwordless login using digital credentials from an EUDI Wallet via OpenID Connect
  URL: https://docs.igrant.io/docs/extensions/passwordless-login
  Markdown: https://docs.igrant.io/docs/extensions/passwordless-login.md

- **Payment Authorisation (for Banks)**: Authorise payments initiated at the payers own bank using an SCA Attestation presented from their EUDI Wallet.
  URL: https://docs.igrant.io/docs/extensions/payment-authorisation-for-banks
  Markdown: https://docs.igrant.io/docs/extensions/payment-authorisation-for-banks.md

- **Payment Authorisation (for Merchants)**: Authorise payments at a merchant or Payment Initiation Service Provider using an SCA Attestation presented from the customers EUDI Wallet.
  URL: https://docs.igrant.io/docs/extensions/payment-authorisation-for-merchants
  Markdown: https://docs.igrant.io/docs/extensions/payment-authorisation-for-merchants.md

- **Payment Credential Issuance (TS12)**: Issue SCA Attestations representing a payment account, card or user to the customers EUDI Wallet.
  URL: https://docs.igrant.io/docs/extensions/payment-credential-issuance
  Markdown: https://docs.igrant.io/docs/extensions/payment-credential-issuance.md

- **Photo ID Credential Issuance**: Issue Photo ID credentials derived from a machine-readable travel document to the customers EUDI Wallet.
  URL: https://docs.igrant.io/docs/extensions/photoid-credential-issuance
  Markdown: https://docs.igrant.io/docs/extensions/photoid-credential-issuance.md

- **PID Credential Issuance**: Issue Person Identification Data (PID) credentials to the customers EUDI Wallet under the EUDI framework.
  URL: https://docs.igrant.io/docs/extensions/pid-credential-issuance
  Markdown: https://docs.igrant.io/docs/extensions/pid-credential-issuance.md

- **Recurring Payment Mandate (TS12)**: Obtain consent for recurring or merchant-initiated payments using an e-mandate SCA Attestation presented from the customers EUDI Wallet.
  URL: https://docs.igrant.io/docs/extensions/recurring-payment-mandate
  Markdown: https://docs.igrant.io/docs/extensions/recurring-payment-mandate.md

- **Risk-based Authentication (TS12)**: Protect login and sensitive actions with Strong Customer Authentication using an SCA Attestation presented from the users EUDI Wallet.
  URL: https://docs.igrant.io/docs/extensions/risk-based-authentication
  Markdown: https://docs.igrant.io/docs/extensions/risk-based-authentication.md

- **upload pdf file**: Uploads a PDF file for use in OpenID4VP transaction data signing workflows.
  URL: https://docs.igrant.io/docs/extensions-api/config-create-digital-wallet-open-id-upload-file
  Markdown: https://docs.igrant.io/docs/extensions-api/config-create-digital-wallet-open-id-upload-file.md

- **Delete uploaded file**: Deletes a previously uploaded PDF file used in OpenID4VP transaction data signing.
  URL: https://docs.igrant.io/docs/extensions-api/config-delete-digital-wallet-open-id-file
  Markdown: https://docs.igrant.io/docs/extensions-api/config-delete-digital-wallet-open-id-file.md

- **List uploaded files**: Lists all uploaded PDF files available for OpenID4VP transaction data signing.
  URL: https://docs.igrant.io/docs/extensions-api/config-list-digital-wallet-open-id-file
  Markdown: https://docs.igrant.io/docs/extensions-api/config-list-digital-wallet-open-id-file.md

- **Download uploaded file**: Downloads a previously uploaded PDF file used in OpenID4VP transaction data signing.
  URL: https://docs.igrant.io/docs/extensions-api/config-read-digital-wallet-open-id-file
  Markdown: https://docs.igrant.io/docs/extensions-api/config-read-digital-wallet-open-id-file.md

- **Create OIDC Client**: Creates an OpenID Connect client. The client enables passwordless login with EUDI Wallet by requesting verifications from individuals. During client creation, a presentation definition specifies which credentials to request - appearing as a QR code or deep link on the authentication page.
  URL: https://docs.igrant.io/docs/extensions-api/create-oidc-client
  Markdown: https://docs.igrant.io/docs/extensions-api/create-oidc-client.md

- **Delete OIDC Client**: Permanently removes an OpenID Connect client and its associated configuration. This action cannot be undone. System-managed clients cannot be deleted.
  URL: https://docs.igrant.io/docs/extensions-api/delete-oidc-client
  Markdown: https://docs.igrant.io/docs/extensions-api/delete-oidc-client.md

- **Discovery Endpoint**: OpenID Provider configuration endpoint that returns the OpenID Provider metadata as a JSON document
  URL: https://docs.igrant.io/docs/extensions-api/get-oid-configuration
  Markdown: https://docs.igrant.io/docs/extensions-api/get-oid-configuration.md

- **Authorisation Endpoint**: OpenID Connect authorization endpoint that initiates the authentication flow. Returns an HTML page where individuals can authenticate using their EUDI Wallet through QR code or deep link verification.
  URL: https://docs.igrant.io/docs/extensions-api/get-oidc-auth-sandbox
  Markdown: https://docs.igrant.io/docs/extensions-api/get-oidc-auth-sandbox.md

- **Authorisation Endpoint**: OpenID Connect authorization endpoint that initiates the authentication flow. Returns an HTML page where individuals can authenticate using their EUDI Wallet through QR code or deep link verification.
  URL: https://docs.igrant.io/docs/extensions-api/get-oidc-auth
  Markdown: https://docs.igrant.io/docs/extensions-api/get-oidc-auth.md

- **Discovery Endpoint**: OpenID Provider configuration endpoint that returns the OpenID Provider metadata as a JSON document
  URL: https://docs.igrant.io/docs/extensions-api/get-oidc-configuration-sandbox
  Markdown: https://docs.igrant.io/docs/extensions-api/get-oidc-configuration-sandbox.md

- **JWKS Endpoint**: JSON Web Key Set (JWKS) endpoint that provides the public keys used to verify the signatures of JWT tokens issued by this OpenID Provider. These keys are used by relying parties to validate ID tokens and other signed responses.
  URL: https://docs.igrant.io/docs/extensions-api/get-oidcjwks-sandbox
  Markdown: https://docs.igrant.io/docs/extensions-api/get-oidcjwks-sandbox.md

- **JWKS Endpoint**: JSON Web Key Set (JWKS) endpoint that provides the public keys used to verify the signatures of JWT tokens issued by this OpenID Provider. These keys are used by relying parties to validate ID tokens and other signed responses.
  URL: https://docs.igrant.io/docs/extensions-api/get-oidcjwks
  Markdown: https://docs.igrant.io/docs/extensions-api/get-oidcjwks.md

- **UserInfo Endpoint**: OpenID Connect UserInfo endpoint that returns claims about the authenticated end-user. Requires a valid access token obtained from the token endpoint to be provided in the `Authorization` header.
  URL: https://docs.igrant.io/docs/extensions-api/get-post-oidc-auth
  Markdown: https://docs.igrant.io/docs/extensions-api/get-post-oidc-auth.md

- **UserInfo Endpoint**: OpenID Connect UserInfo endpoint that returns claims about the authenticated end-user. Requires a valid access token obtained from the token endpoint to be provided in the `Authorization` header.
  URL: https://docs.igrant.io/docs/extensions-api/get-post-oidc-user-info-sandbox
  Markdown: https://docs.igrant.io/docs/extensions-api/get-post-oidc-user-info-sandbox.md

- **iGrant.io API documentation**: iGrant.io (™) is a Swedish data exchange and verification service provider. It uses self-sovereign identity, verifiable credentials, a digital wallet and solid pod technologies, enabling a new level of interoperability and automating compliance with data regulations in a fully auditable manner.
  URL: https://docs.igrant.io/docs/extensions-api/igrant-io-api-documentation
  Markdown: https://docs.igrant.io/docs/extensions-api/igrant-io-api-documentation.md

- **List extension**: Lists all available extensions in the platform
  URL: https://docs.igrant.io/docs/extensions-api/list-extensions
  Markdown: https://docs.igrant.io/docs/extensions-api/list-extensions.md

- **List OIDC Client**: Retrieves a list of all OpenID Connect clients configured for the organisation, including their verification request settings and configurations.
  URL: https://docs.igrant.io/docs/extensions-api/list-oidc-client
  Markdown: https://docs.igrant.io/docs/extensions-api/list-oidc-client.md

- **Token Endpoint**: OpenID Connect token endpoint that exchanges an authorization code for access and ID tokens. Client authentication is required using HTTP Basic Auth with `client_id` as username and `client_secret` as password.
  URL: https://docs.igrant.io/docs/extensions-api/post-oidc-token-sandbox
  Markdown: https://docs.igrant.io/docs/extensions-api/post-oidc-token-sandbox.md

- **Token Endpoint**: OpenID Connect token endpoint that exchanges an authorization code for access and ID tokens. Client authentication is required using HTTP Basic Auth with `client_id` as username and `client_secret` as password.
  URL: https://docs.igrant.io/docs/extensions-api/post-oidc-token
  Markdown: https://docs.igrant.io/docs/extensions-api/post-oidc-token.md

- **Read Account Information Access extension (TS12)**: Read Account Information Access (TS12) extension
  URL: https://docs.igrant.io/docs/extensions-api/read-account-information-access-extension-ts-12
  Markdown: https://docs.igrant.io/docs/extensions-api/read-account-information-access-extension-ts-12.md

- **Read age verification with eudi wallet extension**: Read Age verification with eudi wallet extension
  URL: https://docs.igrant.io/docs/extensions-api/read-age-verification-with-eudi-wallet-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/read-age-verification-with-eudi-wallet-extension.md

- **Read document signing with eudi wallet extension**: Read document signing with eudi wallet extension
  URL: https://docs.igrant.io/docs/extensions-api/read-document-signing-with-eudi-wallet-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/read-document-signing-with-eudi-wallet-extension.md

- **Read kyc with eudi wallet extension**: Read KYC with eudi wallet extension
  URL: https://docs.igrant.io/docs/extensions-api/read-kyc-with-eudi-wallet-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/read-kyc-with-eudi-wallet-extension.md

- **Read OIDC Client**: Retrieves details of an OpenID Connect client. The client enables passwordless login with EUDI Wallet by requesting verifications from individuals. The client configuration includes presentation definition that specifies which credentials to request - appearing as a QR code or deep link on the authentication page.
  URL: https://docs.igrant.io/docs/extensions-api/read-oidc-client
  Markdown: https://docs.igrant.io/docs/extensions-api/read-oidc-client.md

- **Read Payment Authorisation - (for Banks) TS12 extension**: Read Payment Authorisation - (for Banks) TS12 extension
  URL: https://docs.igrant.io/docs/extensions-api/read-payment-authorisation-for-banks-ts-12-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/read-payment-authorisation-for-banks-ts-12-extension.md

- **Read Payment Authorisation (for Merchants) TS12 extension**: Read Payment Authorisation (for Merchants) TS12 extension
  URL: https://docs.igrant.io/docs/extensions-api/read-payment-authorisation-for-merchants-ts-12-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/read-payment-authorisation-for-merchants-ts-12-extension.md

- **Read Payment Credential Issuance (TS12) extension**: Read Payment Credential Issuance (TS12) extension
  URL: https://docs.igrant.io/docs/extensions-api/read-payment-credential-issuance-ts-12-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/read-payment-credential-issuance-ts-12-extension.md

- **Read Photo ID Credential Issuance extension**: Read Photo ID Credential Issuance extension
  URL: https://docs.igrant.io/docs/extensions-api/read-photo-id-credential-issuance-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/read-photo-id-credential-issuance-extension.md

- **Read PID Credential Issuance extension**: Read PID Credential Issuance extension
  URL: https://docs.igrant.io/docs/extensions-api/read-pid-credential-issuance-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/read-pid-credential-issuance-extension.md

- **Read Recurring Payment Mandate (TS12) extension**: Read Recurring Payment Mandate (TS12) extension
  URL: https://docs.igrant.io/docs/extensions-api/read-recurring-payment-mandate-ts-12-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/read-recurring-payment-mandate-ts-12-extension.md

- **Read Risk-based Authentication extension (TS12)**: Read Risk-based Authentication (TS12) extension
  URL: https://docs.igrant.io/docs/extensions-api/read-risk-based-authentication-extension-ts-12
  Markdown: https://docs.igrant.io/docs/extensions-api/read-risk-based-authentication-extension-ts-12.md

- **Toggle extension**: Enable or disable extensions in the platform. For example, enabling the OpenID Connect extension allows users to log in without passwords using their EUDI wallet.
  URL: https://docs.igrant.io/docs/extensions-api/set-extension-enabled-state
  Markdown: https://docs.igrant.io/docs/extensions-api/set-extension-enabled-state.md

- **Update age verification identity credentials with EUDI Wallet extension**: Update the identity credentials for age verification using the EUDI Wallet extension
  URL: https://docs.igrant.io/docs/extensions-api/update-age-verification-identity-credentials-with-eudi-wallet-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/update-age-verification-identity-credentials-with-eudi-wallet-extension.md

- **Update KYC identity credentials with EUDI Wallet extension**: Update the identity credentials for KYC using the EUDI Wallet extension
  URL: https://docs.igrant.io/docs/extensions-api/update-kyc-identity-credentials-with-eudi-wallet-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/update-kyc-identity-credentials-with-eudi-wallet-extension.md

- **Update OIDC Client**: Updates the configuration of an existing OpenID Connect client. Allows modification of the clients name, redirect URIs, allowed origins, identity matching attributes, or callback configuration.
  URL: https://docs.igrant.io/docs/extensions-api/update-oidc-client
  Markdown: https://docs.igrant.io/docs/extensions-api/update-oidc-client.md

- **Update Payment Authorisation - (for Banks) TS12 extension**: Update Payment Authorisation - (for Banks) TS12 extension
  URL: https://docs.igrant.io/docs/extensions-api/update-payment-authorisation-for-banks-ts-12-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/update-payment-authorisation-for-banks-ts-12-extension.md

- **Update Payment Authorisation (for Merchants) TS12 extension**: Update Payment Authorisation (for Merchants) TS12 extension
  URL: https://docs.igrant.io/docs/extensions-api/update-payment-authorisation-for-merchants-ts-12-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/update-payment-authorisation-for-merchants-ts-12-extension.md

- **Update Payment Credential Issuance (TS12) extension**: Update Payment Credential Issuance (TS12) extension
  URL: https://docs.igrant.io/docs/extensions-api/update-payment-credential-issuance-ts-12-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/update-payment-credential-issuance-ts-12-extension.md

- **Update Recurring Payment Mandate (TS12) extension**: Update Recurring Payment Mandate (TS12) extension
  URL: https://docs.igrant.io/docs/extensions-api/update-recurring-payment-mandate-ts-12-extension
  Markdown: https://docs.igrant.io/docs/extensions-api/update-recurring-payment-mandate-ts-12-extension.md

- **Get Started with Digital Wallets**: This guide provides an overview of iGrant.io’s service libraries and enterprise solutions tailored for developers. Familiarity with iGrant.io’s commercial policy is recommended to fully benefit from t...
  URL: https://docs.igrant.io/docs/intro-main
  Markdown: https://docs.igrant.io/docs/intro-main.md

- **Powered by MDX**: export const Highlight = ({children, color}) => ( <span style={{
  URL: https://docs.igrant.io/docs/mdx
  Markdown: https://docs.igrant.io/docs/mdx.md

- **Accept credential**: Accepts a received credential in the holders wallet. The wallet changes the credential status to `credential_accepted` and sends an OID4VCI notification to the issuer. This operation has no request body.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-accept-digital-wallet-open-id-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-accept-digital-wallet-open-id-credential.md

- **Configure auto presentation for the credential**: Configures whether a credential should be automatically presented when a matching OpenID4VP Authorization Request is received. The wallet applies the same setting to the related credentials that the same issuance created, but returns only the credential that you gave in the path.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-configure-auto-present-for-digital-wallet-open-id-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-configure-auto-present-for-digital-wallet-open-id-credential.md

- **Create API key**: Creates an API key for the organisation. Use the key to call the OID4VCI and OpenID4VP endpoints from a server, in place of a bearer access token. Send the key as `Authorization: ApiKey <apiKey>`.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-api-key
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-api-key.md

- **Create credential definition**: Creates a new credential definition for OpenID for Verifiable Credential Issuance (OID4VCI) 1.0. Each entry of the `credentialDefinitions` array holds one credential configuration, with its credential format, claims and issuance settings. The issuer publishes every entry in the OID4VCI Credential Issuer Metadata and uses it as the template for the credentials it issues. Upload the card artwork with the update logo image and update cover image operations after this operation returns.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-credential-definition
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-credential-definition.md

- **Create global configuration**: Creates the global configuration of the OID4VCI issuer. The configuration gives the default branding, the default validity, and the Credential Issuer Metadata settings that all credential definitions of the organisation use.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-global-configuration.md

- **Create holder global configuration**: Creates a global configuration for the holder wallet. The configuration sets credential encryption support, the credential status refresh interval, and the redirect URL for OID4VCI and OpenID4VP flows.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-holder-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-holder-global-configuration.md

- **Create trust authority**: Creates a trust authority for the organisation. A trust authority points to a trust list. The service uses the trust lists to validate issuers and verifiers in OID4VCI and OpenID4VP flows.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-trust-authority
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-trust-authority.md

- **Send verification request**: Sends an OpenID4VP Authorization Request (V3) with enhanced features including transaction data, data agreements, and PDF signing support.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-verification-request-v-3
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-verification-request-v-3.md

- **Create verifier global configuration**: Creates the global configuration of the OpenID4VP verifier.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-verifier-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-verifier-global-configuration.md

- **Create wallet unit**: Registers a new wallet unit with the wallet provider. The wallet provider uses this registration to issue a Wallet Unit Attestation (WUA) to the wallet instance. The organisation must have the wallet provider capability enabled. To enable it, use `PUT /v2/config/digital-wallet/openid`.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-wallet-unit
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-create-digital-wallet-open-id-wallet-unit.md

- **Create organisation admin**: Creates an admin in the organisation. The dashboard uses this operation on the Manage Team page.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-create-organisation-admin
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-create-organisation-admin.md

- **Create sandbox organisation**: Creates a sandbox organisation for the organisation. A sandbox organisation is a separate wallet inside your organisation. It has its own credential definitions, presentation definitions, webhooks and keys, so you can test an issuance or a verification flow without a change to the main wallet.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-create-sandbox-org
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-create-sandbox-org.md

- **Create webhook**: This endpoint creates a webhook. The webhook sends the events that you subscribe to, to an external IT system. The payload URL must start with `http://` or `https://`, and it must be unique for the organisation. Subscribe to a minimum of 1 event type.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-create-webhook
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-create-webhook.md

- **Delete all notifications**: Deletes all wallet notifications for the organisation. There is no filter and no confirmation parameter. Unlike the delete operation for one notification, this operation keeps the credentials that the notifications refer to. The wallet keeps no response body.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-all-digital-wallet-open-id-notification
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-all-digital-wallet-open-id-notification.md

- **Delete API key**: Deletes an API key. The service marks the key as deleted and stops accepting it. The key no longer shows in the list of API keys.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-api-key
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-api-key.md

- **Delete credential definition**: Deletes a credential definition and removes its credential configurations from the OID4VCI Credential Issuer Metadata. The issuer also deletes every credential issuance history record of this credential definition. Credentials that the issuer already gave to a holder stay valid; revoke them first if you must withdraw them.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-credential-definition
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-credential-definition.md

- **Delete issuance history**: Deletes a credential exchange record from the issuance history. The issuer marks the record as deleted and no longer returns it in the issuance history list. The issuer tells the issuance backend in the background, so the response does not show the result of that step.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-credential-history
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-credential-history.md

- **Delete credential**: Deletes a credential from the holders wallet. The wallet marks the credential record as deleted, no longer returns it in the credential list, and no longer uses it for presentations. The wallet tells the issuance backend in the background, so the response does not show the result of that step.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-credential.md

- **Delete global configuration**: Deletes a global configuration for the OID4VCI issuer.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-global-configuration.md

- **Delete holder global configuration**: Deletes a holder global configuration for OID4VCI and OpenID4VP flows. The wallet keeps no response body.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-holder-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-holder-global-configuration.md

- **Delete notification**: Deletes a wallet notification. When the notification has the type `credential_acked` and the related credential is still in the state `credential_acked`, the wallet also deletes that credential. The wallet keeps no response body.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-notification
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-notification.md

- **Delete presentation definition**: Deletes a presentation definition.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-presentation-definition
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-presentation-definition.md

- **Delete trust authority**: Deletes one trust authority of the organisation. Give the trust authority ID in the path. The ID must be a UUID, so this operation does not delete the two built-in trust lists. After deletion, the service no longer uses this trust list to validate issuers and verifiers.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-trust-authority
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-trust-authority.md

- **Delete verification history**: Deletes a verification exchange record.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-verification-history
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-verification-history.md

- **Delete verification**: Deletes a presentation record from the wallet of the holder. The response has no body.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-verification
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-verification.md

- **Delete verifier global configuration**: Deletes the global configuration of the OpenID4VP verifier.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-verifier-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-verifier-global-configuration.md

- **Delete wallet unit**: Deletes one wallet unit that the wallet provider manages. The organisation must have the wallet provider capability enabled. The response body is empty.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-wallet-unit
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-digital-wallet-open-id-wallet-unit.md

- **Delete organisation admin**: Deletes an admin from the organisation. The service gives the admin as it was at the moment of the delete.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-organisation-admin
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-organisation-admin.md

- **Delete sandbox organisation**: Deletes one sandbox organisation of the organisation. Give the sandbox organisation ID in the path. The service removes the wallet of the sandbox organisation and all the data in it.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-sandbox-org
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-sandbox-org.md

- **Delete webhook**: This endpoint deletes a webhook. The server disables the webhook and marks it as deleted. After the delete, the webhook sends no more events, and the other webhook endpoints do not find it. The response contains the webhook in its final state.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-delete-webhook
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-delete-webhook.md

- **Deploy digital wallet**: Deploys the OID4VC digital wallet for the organisation. The service registers the organisation with the OpenID wallet backend and returns the endpoints of the new deployment. Call this operation once, before you create a global configuration, a credential definition or a presentation definition.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-deploy-digital-wallet-open-id
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-deploy-digital-wallet-open-id.md

- **Configure Qualified Trust Service Provider (QTSP) credential**: Selects the Qualified Trust Service Provider (QTSP) signing credential that the wallet uses for remote qualified electronic signatures. Configure and enable the QTSP vault before you call this operation. The service returns an empty body.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-configure-qtsp-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-configure-qtsp-credential.md

- **Configure secure vault**: Configures the secure vaults that hold the cryptographic keys for OID4VCI and OpenID4VP operations. The iGrant.io vault must stay enabled. If you enable the Hashicorp vault, you must give the username, the password, the address and the namespace. If you enable the QTSP vault, you must give the CSC URL, the client ID, the client secret and the user ID.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-configure-secure-vault
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-configure-secure-vault.md

- **Create key**: Creates a new ECDSA P-256 key in a secure vault. The wallet uses the key to sign OID4VCI credentials and OpenID4VP responses. The vault sets the key type, the curve and the algorithm, so there is no parameter for them.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-create-key
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-create-key.md

- **Delete key**: Deletes a key from the secure vault. This operation needs a request body: send `{confirm: DELETE}`. The service refuses the request when the body is missing.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-delete-key
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-delete-key.md

- **Exchange code and receive credential**: Exchanges an authorization code for an access token and receives the credential in the OID4VCI Authorization Code Flow. Call this endpoint after the authorization server redirects the holder back with a code.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-exchange-code-and-receive-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-exchange-code-and-receive-credential.md

- **Generate CSR**: Generates a Certificate Signing Request (CSR) for a key in the secure vault. Send the CSR to a Certificate Authority, then upload the signed certificate chain with the upload certificate chain operation.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-generate-csr
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-generate-csr.md

- **Create credential offer**: Creates an OID4VCI Credential Offer that can be presented to a holder via QR code or deep link. OpenID4VCI 1.0 offers are not yet supported on this operation - the service refuses `version_01` with a 400 - so use `draft_13` until the backend adds 1.0 support. The wallet builds a Credential Offer by value with the Authorization Code Flow. The mandatory fields depend on the version of the OID4VCI specification. Version `draft_13` needs `credentialConfigurationIds`. Version `draft_17` needs `scope`, and does not accept `credentialConfigurationIds`. The offer always uses the Authorization Code Flow with an empty `issuer_state`. This operation does not create a Pre-Authorized Code Flow offer and does not add a `tx_code`.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-holder-create-credential-offer
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-holder-create-credential-offer.md

- **Issue credential**: Issues a Verifiable Credential to a holder using the OpenID for Verifiable Credentials Issuance (OID4VCI) protocol. Supports two issuance modes: **InTime** (credential issued immediately via the Credential Endpoint) and **Deferred** (credential issued later via the Deferred Credential Endpoint by calling the [Issue deferred credential](/docs/openid4vc-api/config-update-digital-wallet-open-id-credential-history) API). Supports W3C VC (JWT), IETF SD-JWT VC, and ISO 18013-5 mDoc/mDL credential formats.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-issue-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-issue-credential.md

- **List keys**: Lists the signing keys of the organisation, grouped by secure vault. The wallet uses these keys to sign OID4VCI credentials and OpenID4VP responses.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-list-keys
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-list-keys.md

- **List Qualified Trust Service Provider (QTSP) Credentials**: Lists the Qualified Trust Service Provider (QTSP) signing credentials that the organisation can use. The wallet reads the list from the QTSP through the Cloud Signature Consortium (CSC) API. Configure and enable the QTSP vault before you call this operation.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-list-qtsp-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-list-qtsp-credential.md

- **Create presentation definition**: Creates a presentation definition. The presentation definition gives the credential types and the claims that the verifier needs for an OpenID4VP verification.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-presentation-definition
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-presentation-definition.md

- **Read credential issuer metadata**: Retrieves the OID4VCI Credential Issuer Metadata for a credential issuer. The wallet reads the `.well-known/openid-credential-issuer` document of the given credential issuer, checks it against the metadata model of the selected version, and returns the checked result. The wallet removes the keys that the model does not define, including `signed_metadata`, and returns the optional keys that the issuer left out with the value `null`. Each entry of `display` gets the default values `Not Discoverable` for `name` and `description` when the issuer gives no value. The wallet does not change the contents of `credential_configurations_supported`.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-read-issuer-metadata
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-read-issuer-metadata.md

- **Read Qualified Trust Service Provider (QTSP) credential**: Reads the details of 1 Qualified Trust Service Provider (QTSP) signing credential. The wallet reads the details from the QTSP through the Cloud Signature Consortium (CSC) API. Configure and enable the QTSP vault before you call this operation.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-read-qtsp-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-read-qtsp-credential.md

- **Read secure vault**: Reads the current secure vault configuration of the organisation. The response shows each vault and tells you if it is enabled. The service does not send a field that has no value.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-read-secure-vault
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-read-secure-vault.md

- **Update secure vault**: Updates the secure vaults that hold the cryptographic keys for OID4VCI and OpenID4VP operations. Send the full configuration. The iGrant.io vault must stay enabled. If you enable the Hashicorp vault, you must give the username, the password, the address and the namespace. If you enable the QTSP vault, you must give the CSC URL, the client ID, the client secret and the user ID.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-update-secure-vault
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-update-secure-vault.md

- **Upload certificate chain**: Uploads a certificate chain and links it to a key in the secure vault. The wallet then adds the chain as the `x5c` value of the key.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-upload-certificate-chain
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-upload-certificate-chain.md

- **Validate transaction data**: Validates the transaction data that a holder approved during an OID4VCI credential issuance.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-validate-transaction-data
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-digital-wallet-open-id-validate-transaction-data.md

- **Filter verification**: Filters the credentials in the wallet of the holder against the request of the verifier and returns the matches. Call this operation after the receive operation, and use the result to build the request body of the send operation.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-filter-digital-wallet-open-id-verification
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-filter-digital-wallet-open-id-verification.md

- **List all webhook deliveries**: This endpoint is used to read recent webhook deliveries with pagination from the consent building block that were sent to an external IT system.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-all-recent-webhook-deliveries
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-all-recent-webhook-deliveries.md

- **List API keys**: Lists the API keys of the organisation, with pagination. The service sorts them with the most recently written key first.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-api-key
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-api-key.md

- **List credential definition templates**: Lists the pre-defined credential schema templates that you can use to create a credential definition. The platform returns only the latest version of each schema. A claim path pointer schema has one entry for each credential format, so the same `name` and `version` can appear more than once. When the platform cannot read the schema repository, it returns an empty `templates` array and no `pagination` object.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-credential-definition-templates
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-credential-definition-templates.md

- **List credential definition**: Lists all credential definitions configured for OID4VCI credential issuance, with the newest change first. Each entry also holds the issuance counts of the credential definition, and the response holds the aggregate issuance counts of the organisation. `search` matches the label and the credential definition ID. `sortOrder` sorts on the last modification time. `vct`, `doctype` and `type` match the value at the top level of a record and in its credential configurations.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-credential-definition
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-credential-definition.md

- **List issuance history**: Lists credential exchange records with pagination and optional status filtering. Each record represents a single OID4VCI credential issuance lifecycle. The issuer sorts the records by `updatedAt` and leaves out the records that you deleted. The response also holds aggregate issuance counts for the whole organisation. The parameters `status`, `accepted`, `inProgress` and `denied` all filter on the same status field. Use only one of them in a request: if you send more than one, the issuer keeps only the last one in the order `status`, `accepted`, `inProgress`, `denied`.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-credential-history
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-credential-history.md

- **List credential**: Lists all credentials stored in the holders wallet with pagination support. The wallet sorts the records by the last update time and leaves out the credentials that you deleted. Use the query parameters to filter the list by status, credential type, expiry, or a search term. The wallet replaces a value that it cannot read with the default value and does not refuse the request.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-credential.md

- **List global configuration**: Lists the global configurations of the OID4VCI issuer. The service sorts them by `updatedAt`, newest first. An organisation holds one issuer global configuration, so the array holds zero or one record.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-global-configuration.md

- **List holder global configuration**: Lists the holder global configurations for OID4VCI and OpenID4VP flows. The wallet sorts the configurations by last update time, newest first.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-holder-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-holder-global-configuration.md

- **List secure vaults**: Lists the secure vaults that you can configure for OID4VCI and OpenID4VP key storage. The organisation must have a deployed OpenID digital wallet.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-list-secure-vaults
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-list-secure-vaults.md

- **Stream notifications (SSE)**: Streams wallet notifications for OID4VCI credential lifecycle events over Server-Sent Events. The server keeps the connection open and writes one frame for each new notification.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-notification-sse
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-notification-sse.md

- **List notification**: Lists the wallet notifications for OID4VCI credential lifecycle events. You can filter the notifications by read status, by notification type and by a search term.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-notification
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-notification.md

- **List organisation wallet units**: Lists the organisation wallet units that the wallet provider manages. For each organisation, the response gives the status of the Legal Person Identification Data (LPID) credential, the status of the Wallet Unit Attestation (WUA), and usage counts. The organisation must have the wallet provider capability enabled.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-organisation-wallet-unit
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-organisation-wallet-unit.md

- **Performance statistics of a wallet provider**: Reads the performance statistics of a wallet provider. The statistics give the OID4VCI issuance totals, the OpenID4VP verification totals, the monthly issuance history, and the counts of individual and organisation wallet units. The service caches the statistics and refreshes them in the background. The organisation must have the wallet provider capability enabled.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-performance-statistics
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-performance-statistics.md

- **List presentation definition templates**: Lists the presentation definition templates of the platform schema repository. Use a template as the starting point for a new presentation definition.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-presentation-definition-templates
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-presentation-definition-templates.md

- **List presentation definition**: Lists the presentation definitions of the organisation. The server sorts them by `updatedAt` and uses `sortOrder` for the direction.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-presentation-definition
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-presentation-definition.md

- **List scope**: Lists the OAuth 2.0 scopes available for OID4VCI credential issuance, as published in the Credential Issuer Metadata. Use a value from this list in `credentialDefinitions[].scope` of a create or update credential definition request, when `authorizationRequestType` is `scope_based`.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-scopes
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-scopes.md

- **List transaction data templates**: Lists the transaction data templates that the digital wallet supports.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-transaction-data-templates
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-transaction-data-templates.md

- **List transaction data**: Lists the transaction data records of the organisation. The server sorts them by the last modification time, and puts the newest record first.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-transaction-data
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-transaction-data.md

- **List trust authority**: Lists the trust authorities of the organisation. The service uses these trust lists to validate issuers and verifiers in OID4VCI and OpenID4VP flows.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-trust-authority
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-trust-authority.md

- **List verification history**: Lists verification exchange records. Each record holds one OpenID4VP verification lifecycle. The server sorts the records by `updatedAt` and uses `sortOrder` for the direction.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-verification-history-v-3
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-verification-history-v-3.md

- **List verification**: Lists the presentation records (V3) in the wallet of the holder. You can filter the records by status and by a search term, and set the sort order. The wallet sorts the records by `updatedAt`.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-verification-v-3
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-verification-v-3.md

- **List verifier global configuration**: Lists the global configurations of the OpenID4VP verifier. The server sorts them by `updatedAt`, newest first.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-verifier-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-verifier-global-configuration.md

- **List wallet units**: Lists the wallet units that the wallet provider manages. Use the query parameters to filter by holder DID or by device platform, and to page through the results. The organisation must have the wallet provider capability enabled.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-wallet-unit
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-digital-wallet-open-id-wallet-unit.md

- **List organisation admins**: Lists the admins of the organisation, with pages. Use the `search` parameter to filter the admins by name or email address. The dashboard uses this operation for the table on the Manage Team page.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-organisation-admins
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-organisation-admins.md

- **List sandbox organisations**: Lists the sandbox organisations of the organisation. The service sorts the list by the time of the last update, and it does not list deleted sandbox organisations.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-sandbox-orgs
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-sandbox-orgs.md

- **List all webhooks**: This endpoint lists all the webhooks of the organisation. Each item in the list also gives the result of the last payload delivery to the webhook. The server does not list deleted webhooks. Use the `offset` and `limit` query parameters to page through the list.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-list-webhooks
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-list-webhooks.md

- **Stream Authenticator issuance status (SSE)**: Establishes a Server-Sent Events (SSE) connection to monitor the iGrant.io Authenticator credential issuance. The connection stays alive with `: keep-alive` comments and closes automatically on success or timeout.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-passwordless-login-issue-authenticator-sse
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-passwordless-login-issue-authenticator-sse.md

- **Issue iGrant.io Authenticator credential for passwordless login**: Issues an iGrant.io Authenticator credential to the EUDI Wallet of the admin that owns the access token. The service gives a credential offer and a one-time PIN. The admin scans the credential offer with the wallet and enters the PIN to accept the credential. Monitor the result with the SSE operation on `/v3/config/admin/authentication/oidc/user/authenticator/sse`.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-passwordless-login-issue-authenticator
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-passwordless-login-issue-authenticator.md

- **Remove iGrant.io Authenticator passwordless login method**: Removes the iGrant.io Authenticator passwordless login method of the admin that owns the access token. After this operation, the admin cannot log in with the Authenticator credential.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-passwordless-login-remove-authenticator
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-passwordless-login-remove-authenticator.md

- **Remove PID passwordless login method**: Removes the PID (Person Identification Data) passwordless login method of the admin that owns the access token. After this operation, the admin cannot log in with the PID credential.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-passwordless-login-unlink-pid
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-passwordless-login-unlink-pid.md

- **Stream PID verification status (SSE)**: Establishes a Server-Sent Events (SSE) connection to monitor the PID (Person Identification Data) verification for passwordless login. The connection stays alive with `: keep-alive` comments and closes automatically on success or timeout.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-passwordless-login-verify-pid-sse
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-passwordless-login-verify-pid-sse.md

- **Verify admin with PID credential for passwordless login**: Starts a verification of the admin with a PID (Person Identification Data) credential from an EUDI Wallet. The service gives a QR code. The admin scans the QR code with the wallet and presents the PID credential. A successful presentation links the wallet to the admin for passwordless login. Monitor the result with the SSE operation on `/v3/config/admin/authentication/oidc/user/verify/sse`.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-passwordless-login-verify-pid
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-passwordless-login-verify-pid.md

- **Ping webhook**: This endpoint pings a webhook that was defined to trigger events to an external IT system. Use it to check that the payload URL answers.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-ping-webhook
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-ping-webhook.md

- **Preview credential definition from URI**: Fetches a credential schema document from a URI so that you can inspect it before you create a credential definition from it. The service downloads the document at `credentialDefinitionUri` and returns it unchanged in `credentialDefinition`. For OpenID4VCI 1.0, the document is a claim path pointer document: its `claims` array holds one entry per claim, each with a `path` array. Send one request per URI.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-preview-digital-wallet-open-id-credential-definition
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-preview-digital-wallet-open-id-credential-definition.md

- **Read admin authentication configuration**: Reads the authentication configuration of the admin that owns the access token. The answer shows if password login is enabled, if passwordless login with EUDI Wallet is enabled, and if the admin has linked a wallet.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-admin-authentication
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-admin-authentication.md

- **Read admin avatar image**: Reads the avatar image of the admin that owns the access token. The service gives the binary image data.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-admin-avatar
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-admin-avatar.md

- **Read admin profile**: Reads the profile of the admin that owns the access token. The dashboard uses this operation on the Manage User page and after login.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-admin-profile
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-admin-profile.md

- **Read credential definition cover image**: Retrieves the cover image of an OID4VCI credential definition. This operation needs no authentication, because wallets read the image from the URL that the issuer publishes in the OID4VCI Credential Issuer Metadata. Anybody who knows the credential definition ID can read the image.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-credential-cover-image
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-credential-cover-image.md

- **Read credential definition**: Retrieves a credential definition by its ID, with the credential configurations that it holds in `credentialDefinitions`. Each configuration holds the credential format, the claims and the issuance settings.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-credential-definition
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-credential-definition.md

- **Read issuance history**: Retrieves a credential exchange record by ID, including the issuance status, credential offer details, and holder information. The issuer reads the stored record and does not contact the issuance backend. A record that you deleted from the issuance history is still available through this operation.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-credential-history
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-credential-history.md

- **Read credential definition logo image**: Retrieves the logo image of an OID4VCI credential definition. This operation needs no authentication, because wallets read the image from the URL that the issuer publishes in the OID4VCI Credential Issuer Metadata. Anybody who knows the credential definition ID can read the image.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-credential-logo-image
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-credential-logo-image.md

- **Read credential revocation status**: Checks the current revocation status of a credential by querying the IETF Token Status List. The wallet reads the status list token of the issuer, updates the stored credential record, and returns the record.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-credential-revocation-status
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-credential-revocation-status.md

- **Read credential**: Retrieves a credential stored in the holders wallet by its ID.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-credential.md

- **Read global configuration**: Reads the global configuration of the OID4VCI issuer. Give the value of `globalConfigurationId` in the path. The organisation must have a deployed digital wallet.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-global-configuration.md

- **Read holder global configuration**: Retrieves a holder global configuration by its ID for OID4VCI and OpenID4VP flows.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-holder-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-holder-global-configuration.md

- **Read notification**: Retrieves a wallet notification by its ID. The wallet creates a notification for each OID4VCI credential lifecycle event.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-notification
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-notification.md

- **Read presentation definition**: Reads one presentation definition by its `presentationDefinitionId`.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-presentation-definition
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-presentation-definition.md

- **Read transaction data**: Reads one transaction data record by its `transactionDataId`.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-transaction-data
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-transaction-data.md

- **Read trust authority**: Reads one trust authority of the organisation. Give the trust authority ID in the path. The ID must be a UUID, so this operation does not read the two built-in trust lists that the list operation returns with the IDs `0` and `1`.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-trust-authority
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-trust-authority.md

- **Read verification history**: Reads one verification exchange record by its identifier.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-verification-history-v-3
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-verification-history-v-3.md

- **Read verification**: Retrieves a presentation record (V3) from the wallet of the holder. The V3 record adds DCQL, transaction data, trust list and response encryption fields.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-verification-v-3
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-verification-v-3.md

- **Read verifier global configuration**: Reads the global configuration of the OpenID4VP verifier by its identifier.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-verifier-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-verifier-global-configuration.md

- **Read wallet unit status**: Reads the wallet unit status from the holders point of view. The status follows the Wallet Unit Attestation (WUA) lifecycle and the presence of a Legal Person Identification Data (LPID) credential in the wallet.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-wallet-unit-status
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-wallet-unit-status.md

- **Read wallet unit**: Reads one wallet unit that the wallet provider manages. Give the wallet unit identifier in the path. The organisation must have the wallet provider capability enabled.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-wallet-unit
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id-wallet-unit.md

- **Read digital wallet deployment**: Reads the OID4VC digital wallet deployment of the organisation. The response gives the deployment status, the service endpoints, and the well-known metadata URLs that wallets and verifiers use.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-digital-wallet-open-id.md

- **Read organisation admin**: Reads one admin of the organisation.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-organisation-admin
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-organisation-admin.md

- **Read webhook delivery**: This endpoint reads 1 payload delivery of a webhook. Give the webhook ID and the delivery ID in the path.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-recent-webhook-delivery
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-recent-webhook-delivery.md

- **Read sandbox organisation**: Reads one sandbox organisation of the organisation. Give the sandbox organisation ID in the path.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-sandbox-org
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-sandbox-org.md

- **Read webhook event types**: This endpoint lists all the webhook event types that you can subscribe to. Use these values in the `subscribedEvents` field when you create or update a webhook. The list is the same for all organisations.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-webhook-event-types
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-webhook-event-types.md

- **Read webhook**: This endpoint reads 1 webhook of the organisation by its ID.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-read-webhook
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-read-webhook.md

- **Receive deferred credential**: Polls the OID4VCI Deferred Credential Endpoint to retrieve a credential that was not immediately available during issuance. The wallet uses the acceptance token of the credential record to make the request. If the issuer is not ready, the wallet returns the credential record with the status `credential_pending`. This operation has no request body.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-receive-deferred-digital-wallet-open-id-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-receive-deferred-digital-wallet-open-id-credential.md

- **Receive credential**: Processes an OID4VCI Credential Offer and initiates the credential issuance flow. The wallet resolves the issuers metadata, performs token exchange, and receives the credential.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-receive-digital-wallet-open-id-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-receive-digital-wallet-open-id-credential.md

- **Receive DC API verification response**: Receives an OpenID4VP Authorization Response delivered over the W3C Digital Credentials API (DC API) transport for a previously created verification request.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-receive-digital-wallet-open-id-dc-api-response
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-receive-digital-wallet-open-id-dc-api-response.md

- **Receive verification**: Processes an OpenID4VP Authorization Request (V3) received from a verifier. The wallet resolves the verifiers requirements and identifies matching credentials. The V3 record adds DCQL, transaction data, trust list and response encryption fields.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-receive-digital-wallet-open-id-verification-v-3
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-receive-digital-wallet-open-id-verification-v-3.md

- **Receive credential with user PIN**: Submits the transaction code (tx_code) required for the OID4VCI Pre-Authorized Code Flow. The wallet sends the transaction code with the pre-authorized code to the Token Endpoint of the issuer, and then requests the credential.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-receive-user-pin-for-digital-wallet-open-id-credential
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-receive-user-pin-for-digital-wallet-open-id-credential.md

- **Request credential re-issuance**: Requests reissuance of an expired or near-expiry credential via the OID4VCI protocol. The wallet uses the stored refresh token of the credential to get a new access token, and then asks the issuer for a new credential. Reissuance is not applicable to a Wallet Unit Attestation. This operation has no request body.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-request-digital-wallet-open-id-credential-reissuance
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-request-digital-wallet-open-id-credential-reissuance.md

- **Reset admin password**: Changes the password of the admin that owns the access token. The admin must give the current password and the new password.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-reset-admin-password
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-reset-admin-password.md

- **Revalidate verification**: Revalidates a verification exchange that the holder already answered.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-revalidate-digital-wallet-open-id-verification
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-revalidate-digital-wallet-open-id-verification.md

- **Send verification**: Builds the Verifiable Presentation from the credentials that the holder selected and sends it to the verifier.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-send-digital-wallet-open-id-verification-presentation-v-3
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-send-digital-wallet-open-id-verification-presentation-v-3.md

- **Enable or disable passwordless login for an admin**: Enables or disables passwordless login with EUDI Wallet for one admin of the organisation. When passwordless login is enabled, the admin can link a wallet and log in with a PID (Person Identification Data) credential or an iGrant.io Authenticator credential in place of a password.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-set-passwordless-login-for-admin
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-set-passwordless-login-for-admin.md

- **Toggle trust authority**: Enables or disables a trust authority. A disabled trust authority is not used for credential or verifier trust validation. Give the wanted end state in `disabled`. The ID in the path must be a UUID, so this operation does not change the two built-in trust lists.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-toggle-digital-wallet-open-id-trust-authority
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-toggle-digital-wallet-open-id-trust-authority.md

- **Update admin avatar image**: Updates the avatar image of the admin that owns the access token. Send the image as `multipart/form-data` in the `avatarimage` field.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-admin-avatar
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-admin-avatar.md

- **Update admin profile**: Updates the profile of the admin that owns the access token, for example the name or the phone number.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-admin-profile
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-admin-profile.md

- **Bind API key to sandbox organisation**: Binds an API key to a sandbox organisation, or binds it back to the main wallet.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-api-key-sandbox-org
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-api-key-sandbox-org.md

- **Update API key**: Updates the name, the scopes and the lifetime of an API key.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-api-key
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-api-key.md

- **Update credential definition cover image**: Uploads or updates the cover image of an OID4VCI credential definition. This operation is the only way to upload your own cover image, because the create and update credential definition operations ignore `display.backgroundImage.uri`. The server stores the image, then sets `display.backgroundImage.uri` of the credential definition and of every credential configuration that it holds to the URL of the new image. Use this operation after you create the credential definition.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-credential-cover-image
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-credential-cover-image.md

- **Update credential definition**: Updates an existing credential definition. The changes apply to future credential issuances that use this definition. This operation replaces the whole `credentialDefinitions` array, so always send every credential configuration that the issuer must keep. Set `credentialDefinitions[].id` to the identifier of an existing configuration to change it, and omit the field to add a new one. The issuer always discards `display.logo.uri` and `display.backgroundImage.uri` from the request body and keeps the stored images; use the update logo image and update cover image operations to change the artwork. `version`, `trustAnchor`, `kid`, `supportRevocation` and `revocationMethod` are immutable after creation, and this operation does not accept them.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-credential-definition
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-credential-definition.md

- **Issue deferred credential**: Updates a credential exchange record. Used to issue a credential via the OID4VCI Deferred Credential Endpoint by providing the credential claims for a pending issuance.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-credential-history
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-credential-history.md

- **Update credential definition logo image**: Uploads or updates the logo image of an OID4VCI credential definition. This operation is the only way to upload your own logo, because the create and update credential definition operations ignore `display.logo.uri`. The server stores the image, then sets `display.logo.uri` of the credential definition and of every credential configuration that it holds to the URL of the new image. Use this operation after you create the credential definition.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-credential-logo-image
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-credential-logo-image.md

- **Update credential revocation status**: Updates the revocation status of an issued credential using the IETF Token Status List.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-credential-revocation-status
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-credential-revocation-status.md

- **Update global configuration**: Updates the global configuration of the OID4VCI issuer.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-global-configuration.md

- **Update holder global configuration**: Updates a holder global configuration for OID4VCI and OpenID4VP flows. The wallet replaces all settings with the values in the request body, so send every field that you want to keep.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-holder-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-holder-global-configuration.md

- **Update notification**: Marks a wallet notification as read. The wallet accepts only the value `read`, because a notification cannot go back to the `unread` state.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-notification
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-notification.md

- **Update presentation definition**: Updates a presentation definition.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-presentation-definition
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-presentation-definition.md

- **Update sandbox organisation cover image**: Updates the cover image of one sandbox organisation. Give the sandbox organisation ID in the path and send the image as multipart form data in the `coverimage` form field.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-sandbox-org-cover
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-sandbox-org-cover.md

- **Update sandbox organisation logo image**: Updates the logo image of one sandbox organisation. Give the sandbox organisation ID in the path and send the image as multipart form data in the `logoimage` form field.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-sandbox-org-logo
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-sandbox-org-logo.md

- **Update sandbox organisation name**: Updates the name of one sandbox organisation. Give the sandbox organisation ID in the path.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-sandbox-org-name
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-sandbox-org-name.md

- **Update trust authority**: Updates one trust authority of the organisation. Give the trust authority ID in the path. Send all three fields with valid values. The service forwards each field, and it rejects an empty field.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-trust-authority
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-trust-authority.md

- **Update verifier global configuration**: Updates the global configuration of the OpenID4VP verifier.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-verifier-global-configuration
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-verifier-global-configuration.md

- **Update wallet unit**: Updates one wallet unit that the wallet provider manages. All fields in the body are optional, but `isAuthorised` behaves differently from the others: the service always forwards it, so if you do not give `isAuthorised`, the service sets it to `false` and the wallet unit loses its authorisation. Always send the value that you want to keep. If you leave out `clientId`, `clientUrl` or `clientPublicKey`, the service keeps the stored value. The organisation must have the wallet provider capability enabled.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-wallet-unit
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id-wallet-unit.md

- **Enable wallet provider**: Enables the wallet provider capability for the organisation. Send `isWalletProvider` with the value `true`. The service then registers the organisation as a wallet provider and the organisation can register wallet units and issue Wallet Unit Attestations. If you send `false`, the service keeps the current value and returns the deployment details.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-digital-wallet-open-id.md

- **Update sandbox organisation**: Updates the name and the description of one sandbox organisation. Give the sandbox organisation ID in the path.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-sandbox-org
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-sandbox-org.md

- **Update webhook**: This endpoint updates a webhook. The request body replaces the payload URL, the content type, the subscribed events, the disabled flag, the secret key and the SSL verification flag of the webhook. The payload URL must start with `http://` or `https://`, and no other webhook of the organisation can use it. Subscribe to a minimum of 1 event type.
  URL: https://docs.igrant.io/docs/openid4vc-api/config-update-webhook
  Markdown: https://docs.igrant.io/docs/openid4vc-api/config-update-webhook.md

- **List all webhook content types**: This endpoint lists the payload content types that a webhook can use. Use one of these values in the `contentType` field when you create or update a webhook. The server posts the payload as a JSON body for `application/json`. For `application/x-www-form-urlencoded`, the server makes a string of the payload and posts it as a form under the `payload` key. Note the capital `C` in the `ContentTypes` response field. The order of the values changes between calls.
  URL: https://docs.igrant.io/docs/openid4vc-api/get-webhook-payload-content-types
  Markdown: https://docs.igrant.io/docs/openid4vc-api/get-webhook-payload-content-types.md

- **iGrant.io API documentation**: iGrant.io provides a complete implementation of the OpenID for Verifiable Credentials Issuance (OID4VCI) and OpenID for Verifiable Presentation (OpenID4VP) protocols. This API enables organizations to issue, hold, and verify digital credentials using standards-compliant flows with support for W3C VC (JWT), IETF SD-JWT VC, and ISO 18013-5 mDoc/mDL credential formats.
  URL: https://docs.igrant.io/docs/openid4vc-api/igrant-io-api-documentation
  Markdown: https://docs.igrant.io/docs/openid4vc-api/igrant-io-api-documentation.md

- **Quickstart**: Get started with the Organisation Wallet Suite by iGrant.io
  URL: https://docs.igrant.io/docs/get-started/
  Markdown: https://docs.igrant.io/docs/get-started.md

- **Technical references and resources | EUDI Wallet**: Access key technical references, standards, and resources supporting digital identity, verifiable credentials, and wallet implementations.
  URL: https://docs.igrant.io/docs/references/
  Markdown: https://docs.igrant.io/docs/references.md

- **Template Example**: To serve as an example page when styling markdown based Docusaurus sites.
  URL: https://docs.igrant.io/docs/template
  Markdown: https://docs.igrant.io/docs/template.md

- **Terminology**: Refer to our commonly used industry-related terminologies that will help the users understand concepts and find relevant links to dive deep into developer docs
  URL: https://docs.igrant.io/docs/terminology/
  Markdown: https://docs.igrant.io/docs/terminology.md

- **Trust in the Wallet Ecosystem**: Understand how the iGrant.io wallets establish trust in credential issuers and verifiers using the EU Trust List, EBSI, X.509 certificates and related trust frameworks.
  URL: https://docs.igrant.io/docs/trust-overview/
  Markdown: https://docs.igrant.io/docs/trust-overview.md

- **Register as a Wallet-Relying Party**: Get your service listed on the iGrant.io recognised Trust List, operated as a test network, so the Data Wallet treats you as a trusted wallet-relying party.
  URL: https://docs.igrant.io/docs/trust-relying-party-registration/
  Markdown: https://docs.igrant.io/docs/trust-relying-party-registration.md

- **The Issuer / service provider not verified notice**: Learn what the Issuer not verified / Service provider not verified notice (formerly Untrusted Service Provider) in the iGrant.io Data Wallet means, why it appears, and how to make an issuer or verifier recognised.
  URL: https://docs.igrant.io/docs/trust-untrusted-service-provider/
  Markdown: https://docs.igrant.io/docs/trust-untrusted-service-provider.md

- **Explore the IEEE Paper on data exchange agreements**: Review how auditable data exchange agreements enhance transparency and trust in digital wallet ecosystems, as detailed in the IEEE publication.
  URL: https://docs.igrant.io/concepts/dataexchange-agreements-ieee-paper/
  Markdown: https://docs.igrant.io/concepts/dataexchange-agreements-ieee-paper.md

- **EUDI Wallet Business Use Cases & Benefits (eIDAS 2.0)**: How businesses use the EUDI Wallet under eIDAS 2.0: instant verified onboarding, qualified e-signatures, legal entity credentials, and fraud reduction, with ARF guidance.
  URL: https://docs.igrant.io/concepts/eu-digital-identity-eudi-wallet-business-benefits-use-cases-eidas/
  Markdown: https://docs.igrant.io/concepts/eu-digital-identity-eudi-wallet-business-benefits-use-cases-eidas.md

- **Understanding Digital Credential Query Language (DCQL) in the EUDI Wallet Ecosystem**: Learn how the Digital Credentials Query Language (DCQL), introduced in OpenID4VP v1.0, enables precise, privacy-preserving credential sharing in EUDI Wallets, with a case study from the EWC Large Scale Pilot on merchant-led business wallet payments.
  URL: https://docs.igrant.io/concepts/eudi-wallet-dcql-openid4vp-business-wallet-payments/
  Markdown: https://docs.igrant.io/concepts/eudi-wallet-dcql-openid4vp-business-wallet-payments.md

- **Verifiable Credential Formats in the EUDI Wallet - SD-JWT VC and ISO/IEC-mdoc**: Explore the credential formats in the EUDI Wallet under the amended Implementing Acts, including IETF SD-JWT VC and ISO/IEC-mdoc (ISO 18013-5)
  URL: https://docs.igrant.io/concepts/eudi-wallet-verifiable-credential-formats/
  Markdown: https://docs.igrant.io/concepts/eudi-wallet-verifiable-credential-formats.md

- **OpenID4VC: OpenID4VCI, OpenID4VP & SIOPv2 Explained**: Compare the three OpenID4VC protocols: OpenID4VCI for issuance, OpenID4VP for presentation, and SIOPv2 for authentication, with EUDI wallet workflows and real EU use cases.
  URL: https://docs.igrant.io/concepts/openID4vc/
  Markdown: https://docs.igrant.io/concepts/openID4vc.md

- **Credential issuance lifecycle (OpenID4VCI): From offer to acceptance**: A comprehensive guide to the OpenID4VCI (OpenID for Verifiable Credential Issuance) credential issuance lifecycle for developers, solution architects, and product managers building on EUDI Wallets, European Business Wallets, and digital identity ecosystems.
  URL: https://docs.igrant.io/concepts/credential-issuance-lifecycle/
  Markdown: https://docs.igrant.io/concepts/credential-issuance-lifecycle.md

- **Credential Issuance for EUDI Wallets (OpenID4VCI)**: OpenID4VCI (OID4VCI) is the protocol EUDI wallets use to receive verifiable credentials. Learn the credential offer, authorization and pre-authorized code flows, with examples.
  URL: https://docs.igrant.io/concepts/openid4vci-credential-issuance/
  Markdown: https://docs.igrant.io/concepts/openid4vci-credential-issuance.md

- **Credential Verification for EUDI Wallets (OpenID4VP)**: OpenID4VP (OID4VP) is the protocol EUDI wallet verifiers use to request and validate verifiable presentations. Learn the presentation request, VP token response and verification flow, with examples.
  URL: https://docs.igrant.io/concepts/openid4vp-credential-verification/
  Markdown: https://docs.igrant.io/concepts/openid4vp-credential-verification.md

- **Revocation chaining in the EUDI Wallet: How revoking a Wallet Unit reaches the PID**: How revocation reaches the PID in the EUDI Wallet: Token Status Lists, the 24-hour re-check, implicit verification, and the risk-analysed keystore case.
  URL: https://docs.igrant.io/concepts/revocation-chaining/
  Markdown: https://docs.igrant.io/concepts/revocation-chaining.md

- **WSCD and WSCA in the EUDI Wallet: where the keys live and how they are protected**: What the Wallet Secure Cryptographic Device (WSCD) and Application (WSCA) are in the EUDI Wallet: the Secure Cryptographic Interface, the four WSCD architectures, ISO/IEC 18045 levels, and how they underpin the Wallet Unit Attestation (WUA).
  URL: https://docs.igrant.io/concepts/wallet-secure-cryptographic-application-device/
  Markdown: https://docs.igrant.io/concepts/wallet-secure-cryptographic-application-device.md

- **Wallet Unit Attestation (WUA): How the EUDI Wallet proves it is genuine and its keys are protected**: A developer and architects guide to the Wallet Unit Attestation (WUA) in the EUDI Wallet: what it is, how the Wallet Instance Attestation and Key Attestation work, how they are used during OpenID4VCI issuance, and how the TS3 profile tightens the rules.
  URL: https://docs.igrant.io/concepts/wallet-unit-attestation/
  Markdown: https://docs.igrant.io/concepts/wallet-unit-attestation.md

- **What are EU Digital Identity (EUDI) Wallets**: Learn what EU Digital Identity (EUDI) Wallets are, what they store, who runs them, and when certified national wallets arrive under eIDAS 2.0 rules.
  URL: https://docs.igrant.io/concepts/what-is-the-eu-digital-identity-wallet/
  Markdown: https://docs.igrant.io/concepts/what-is-the-eu-digital-identity-wallet.md

- **EUDI Wallet Insights**: Technical deep dives, business guides, and specifications for building on the European Digital Identity Wallet ecosystem.
  URL: https://docs.igrant.io/concepts/
  Markdown: https://docs.igrant.io/concepts.md

- **Understanding eIDAS2.0: The Future of Digital Identity**: eIDAS2.0 is the updated European Union regulation for electronic identification and trust services, aimed at enhancing security and interoperability for digital transactions across member states.
  URL: https://docs.igrant.io/concepts/eidas/eidas-main
  Markdown: https://docs.igrant.io/concepts/eidas/eidas-main.md

- **Introduction to eIDAS2.0 and Digital Wallets**: eIDAS 2.0 enhances digital identity across EU member states with secure, interoperable digital wallets, improving user control and cross-border trust services.
  URL: https://docs.igrant.io/concepts/eidas2-and-digital-wallets/
  Markdown: https://docs.igrant.io/concepts/eidas2-and-digital-wallets.md

- **Business Wallets - Enabling Trust and Scale in the European Digital Identity (EUDI) Wallet Ecosystem**: Explore how European Business Wallets enable legal entities to hold and present verifiable credentials for secure, cross-border digital transactions.
  URL: https://docs.igrant.io/concepts/european-business-wallets/
  Markdown: https://docs.igrant.io/concepts/european-business-wallets.md

- **What are data agreements in the digital identity ecosystem**: Learn how data agreements define consent, purpose, and usage terms for secure and transparent data sharing in digital wallet ecosystems.
  URL: https://docs.igrant.io/concepts/data-agreements/
  Markdown: https://docs.igrant.io/concepts/data-agreements.md

- **See versions of data agreements explained**: Explore different versions of data agreements, their evolution, and how they enable structured, transparent consent in digital identity solutions.
  URL: https://docs.igrant.io/concepts/data-agreements-versions
  Markdown: https://docs.igrant.io/concepts/data-agreements-versions.md

- **Understand the data exchange landscape**: Explore the evolving data exchange landscape, including standards, protocols, and frameworks driving trusted digital identity ecosystems.
  URL: https://docs.igrant.io/concepts/data-exchange-landscape
  Markdown: https://docs.igrant.io/concepts/data-exchange-landscape.md

- **Learn Data Disclosure Agreements (DDA) with iGrant.io**: Understand how data disclosure agreements govern what data is shared, with whom, and under what terms in digital identity ecosystems.
  URL: https://docs.igrant.io/concepts/data-disclosure-agreements/
  Markdown: https://docs.igrant.io/concepts/data-disclosure-agreements.md

- **Explore the concepts of Data Disclosure Agreements**: See how data disclosure agreement versions evolve to support transparent, auditable data sharing between individuals and organisations.
  URL: https://docs.igrant.io/concepts/data-disclosure-agreements-versions
  Markdown: https://docs.igrant.io/concepts/data-disclosure-agreements-versions.md

- **Overview of Data Intermediation Service Provider**: Learn how a Data Intermediation Service Provider facilitates secure, consent‑based data exchange between individuals and organisations.
  URL: https://docs.igrant.io/concepts/disp-overview/
  Markdown: https://docs.igrant.io/concepts/disp-overview.md

- **High-level Architecture**: The overall iGrant.io platform with software components delivering iGrant.io services are as illustrated below.
  URL: https://docs.igrant.io/concepts/mdoDocs/mdo-main
  Markdown: https://docs.igrant.io/concepts/mdoDocs/mdo-main.md

- **Mobile SDKs and Data Wallet**: Apart from providing all services as RESTful APIs, the platform also provides out-of-the-box mobile SDKs  (iOS and Android). This consists of personal data dashboard features and data wallets as descr...
  URL: https://docs.igrant.io/concepts/mdoDocs/mdo-mobagents
  Markdown: https://docs.igrant.io/concepts/mdoDocs/mdo-mobagents.md

- **Personal Data Portal**: Apart from providing all services as RESTful APIs, the platform also provides  ReactJS portals that can be automatically deployed once the data agreement models are defined in the Enterprise Dashboard...
  URL: https://docs.igrant.io/concepts/mdoDocs/mdo-pdd
  Markdown: https://docs.igrant.io/concepts/mdoDocs/mdo-pdd.md

- **Explore the Minimum Disclosure Option (MDO) Model**: Understand the MDO reference model, which enables privacy‑preserving sharing of only essential data in digital identity transactions.
  URL: https://docs.igrant.io/concepts/mdoDocs/mdo-ref-model
  Markdown: https://docs.igrant.io/concepts/mdoDocs/mdo-ref-model.md

- **EU Implementing Regulations Overview**: Browse all EU Implementing Regulations for the European Digital Identity Framework, covering EUDI Wallet certification, protocols, trust frameworks, and more.
  URL: https://docs.igrant.io/regulations/implementing-acts-overview/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-overview.md

- **European Business Wallets**: The full text of the proposed EU Regulation on the establishment of European Business Wallets (COM(2025) 838 final), a Commission proposal not yet adopted.
  URL: https://docs.igrant.io/regulations/reg-eu-business-wallets/
  Markdown: https://docs.igrant.io/regulations/reg-eu-business-wallets.md

- **European Data Act**: Learn how the EU Data Act governs data access and sharing between businesses and individuals, fostering fairness and innovation in digital ecosystems.
  URL: https://docs.igrant.io/regulations/reg-eu-data-act/
  Markdown: https://docs.igrant.io/regulations/reg-eu-data-act.md

- **European Data Governance Act**: Learn how the EU Data Governance Act enables secure data sharing and consent frameworks to build trust in digital identity ecosystems.
  URL: https://docs.igrant.io/regulations/reg-eu-data-governance-act/
  Markdown: https://docs.igrant.io/regulations/reg-eu-data-governance-act.md

- **European Digital ID Framework**: Explore how the EU Digital ID Framework supports trusted digital identities and wallets, enabling secure cross‑border online services in Europe.
  URL: https://docs.igrant.io/regulations/reg-eu-digital-id-framework/
  Markdown: https://docs.igrant.io/regulations/reg-eu-digital-id-framework.md

- **General Data Protection Regulation**: Understand the key GDPR principles that guide personal data protection, consent, and compliance in digital identity ecosystems.
  URL: https://docs.igrant.io/regulations/reg-eu-gdpr/
  Markdown: https://docs.igrant.io/regulations/reg-eu-gdpr.md

- **European Health Data Space**: Discover how the EU Health Data Space enables secure, consent‑based access and exchange of healthcare data, empowering patient-centred digital services.
  URL: https://docs.igrant.io/regulations/reg-eu-health-data-space/
  Markdown: https://docs.igrant.io/regulations/reg-eu-health-data-space.md

- **EUDI Wallet - Accreditation of conformity assessment bodies**: Learn about the EU Implementing Acts on accreditation of conformity assessment bodies for EU Digital Identity Wallets.
  URL: https://docs.igrant.io/regulations/implementing-acts-accreditation-conformity/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-accreditation-conformity.md

- **eIDAS - Annual reports by supervisory bodies**: Understand the EU Implementing Acts on annual reports by supervisory bodies on trust services and digital identity.
  URL: https://docs.igrant.io/regulations/implementing-acts-annual-reports/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-annual-reports.md

- **EUDI Wallet - Certification**: Explore how the EU Implementing Act defines certification rules and requirements to ensure secure and compliant digital identity solutions for EUDI wallets.
  URL: https://docs.igrant.io/regulations/implementing-acts-certification/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-certification.md

- **eIDAS - Certified creation devices**: Understand the EU Implementing Acts on notification of certified qualified electronic signature and seal creation devices.
  URL: https://docs.igrant.io/regulations/implementing-acts-certified-creation-devices/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-certified-creation-devices.md

- **EUDI Wallet - Cross-border identity matching**: Understand the EU Implementing Acts on cross-border identity matching for EU Digital Identity Wallets.
  URL: https://docs.igrant.io/regulations/implementing-acts-cross-border-identity/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-cross-border-identity.md

- **eIDAS - Formats of advanced electronic signatures and seals**: Understand the EU Implementing Acts on formats for advanced electronic signatures and seals under eIDAS.
  URL: https://docs.igrant.io/regulations/implementing-acts-formats-signatures-seals/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-formats-signatures-seals.md

- **EUDI Wallet - Identity and qualified certificates**: Learn about the EU Implementing Acts on identity verification and qualified certificates for EU Digital Identity Wallets.
  URL: https://docs.igrant.io/regulations/implementing-acts-identity-qualified-certificates/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-identity-qualified-certificates.md

- **EUDI Wallet - Integrity and core functionalities**: Learn how the EU Implementing Acts define integrity and core functions for EU Digital Identity Wallets, ensuring interoperability and trust across borders.
  URL: https://docs.igrant.io/regulations/implementing-acts-integrity-and-core-functions/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-integrity-and-core-functions.md

- **eIDAS - List of certificates**: Understand the EU Implementing Acts on the list of certificates for trust services.
  URL: https://docs.igrant.io/regulations/implementing-acts-list-certificates/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-list-certificates.md

- **EUDI Wallet - Peer review of electronic identification schemes**: Learn about the EU Implementing Acts on peer review processes for electronic identification schemes.
  URL: https://docs.igrant.io/regulations/implementing-acts-peer-review-eid/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-peer-review-eid.md

- **EUDI Wallet - Person identification data and electronic attestations of attributes**: Learn how the EU Implementing Acts define using PID and Electronic Attestation Attributes (EAAs) for secure and trusted digital identity verification.
  URL: https://docs.igrant.io/regulations/implementing-acts-pid-and-eaass/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-pid-and-eaass.md

- **EUDI Wallet - Protocols and interfaces to be supported**: See which protocols and interfaces are mandated by the Implementing Acts to ensure EU Digital Identity Wallet compatibility and secure data exchange.
  URL: https://docs.igrant.io/regulations/implementing-acts-protocols-and-interfaces-to-be-supported/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-protocols-and-interfaces-to-be-supported.md

- **eIDAS - Qualified certificates for electronic signatures and seals**: Understand the EU Implementing Acts on qualified certificates for electronic signatures and seals.
  URL: https://docs.igrant.io/regulations/implementing-acts-qualified-certificates/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-qualified-certificates.md

- **eIDAS - Qualified electronic archiving services**: Understand the EU Implementing Acts on requirements for qualified electronic archiving services under eIDAS.
  URL: https://docs.igrant.io/regulations/implementing-acts-qualified-electronic-archiving/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-qualified-electronic-archiving.md

- **eIDAS - Qualified electronic registered delivery services**: Learn about the EU Implementing Acts on qualified electronic registered delivery services.
  URL: https://docs.igrant.io/regulations/implementing-acts-qualified-delivery/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-qualified-delivery.md

- **eIDAS - Qualified electronic ledgers**: Understand the EU Implementing Acts on requirements for qualified electronic ledgers under eIDAS.
  URL: https://docs.igrant.io/regulations/implementing-acts-qualified-electronic-ledgers/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-qualified-electronic-ledgers.md

- **eIDAS - Qualified preservation services for electronic signatures and seals**: Learn about the EU Implementing Acts on qualified preservation services for electronic signatures and seals.
  URL: https://docs.igrant.io/regulations/implementing-acts-qualified-preservation/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-qualified-preservation.md

- **eIDAS - Qualified electronic time stamps**: Understand the EU Implementing Acts on qualified electronic time stamps.
  URL: https://docs.igrant.io/regulations/implementing-acts-qualified-timestamps/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-qualified-timestamps.md

- **eIDAS - Qualified trust service applications**: Understand the EU Implementing Acts on qualified trust service applications.
  URL: https://docs.igrant.io/regulations/implementing-acts-qualified-trust-apps/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-qualified-trust-apps.md

- **eIDAS - Qualified trust service providers**: Understand the EU Implementing Acts on requirements for qualified trust service providers under eIDAS.
  URL: https://docs.igrant.io/regulations/implementing-acts-qualified-trust-service-providers/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-qualified-trust-service-providers.md

- **eIDAS - Qualified certificates for website authentication**: Understand the EU Implementing Acts on qualified certificates for website authentication under eIDAS.
  URL: https://docs.igrant.io/regulations/implementing-acts-qualified-website-auth-certs/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-qualified-website-auth-certs.md

- **eIDAS - Recognition of qualified validation services**: Learn about the EU Implementing Acts on recognition of qualified validation services.
  URL: https://docs.igrant.io/regulations/implementing-acts-recognition-validation/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-recognition-validation.md

- **eIDAS - Reference standards and validation procedures**: Understand the EU Implementing Acts on reference standards and validation procedures for qualified trust services.
  URL: https://docs.igrant.io/regulations/implementing-acts-reference-standards/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-reference-standards.md

- **eIDAS - Registration of relying parties (standards update)**: Understand Implementing Regulation (EU) 2026/1730, which updates the standards and specifications for the registration of wallet-relying parties.
  URL: https://docs.igrant.io/regulations/implementing-acts-registration-relying-parties-update/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-registration-relying-parties-update.md

- **EUDI Wallet - Registration of relying parties**: Learn about the EU Implementing Acts on registration of relying parties for EU Digital Identity Wallets.
  URL: https://docs.igrant.io/regulations/implementing-acts-registration-relying-parties/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-registration-relying-parties.md

- **EUDI Wallet - Remote onboarding**: Understand the EU Implementing Acts on reference standards and specifications for remote onboarding of users to EUDI Wallets using eID means at assurance level substantial.
  URL: https://docs.igrant.io/regulations/implementing-acts-remote-onboarding/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-remote-onboarding.md

- **eIDAS - Remote qualified electronic signature and seal creation devices**: Understand the EU Implementing Acts on remote qualified electronic signature and seal creation devices.
  URL: https://docs.igrant.io/regulations/implementing-acts-remote-creation-devices/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-remote-creation-devices.md

- **eIDAS - Risk management for non-qualified trust service providers**: Learn about the EU Implementing Acts on risk management procedures for non-qualified trust service providers.
  URL: https://docs.igrant.io/regulations/implementing-acts-risk-management/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-risk-management.md

- **EUDI Wallet - Security breaches**: Understand the EU Implementing Acts on handling security breaches for EU Digital Identity Wallets.
  URL: https://docs.igrant.io/regulations/implementing-acts-security-breaches/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-security-breaches.md

- **eIDAS - Trusted lists**: Understand the EU Implementing Acts on trusted lists for trust service providers.
  URL: https://docs.igrant.io/regulations/implementing-acts-trusted-lists/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-trusted-lists.md

- **EUDI Wallet - Trust framework**: Learn how the EU Implementing Act supports trust frameworks to ensure the trustworthiness and transparency of entities within the digital wallet ecosystem.
  URL: https://docs.igrant.io/regulations/implementing-acts-trustframework/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-trustframework.md

- **eIDAS - Verification of electronic attestations (standards update)**: Understand Implementing Regulation (EU) 2026/1735, which updates the standards and specifications for verifying electronic attestations of attributes.
  URL: https://docs.igrant.io/regulations/implementing-acts-verification-attestations-update/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-verification-attestations-update.md

- **EUDI Wallet - Verification of electronic attestation of attributes**: Learn about the EU Implementing Acts on verification of electronic attestation of attributes for EU Digital Identity Wallets.
  URL: https://docs.igrant.io/regulations/implementing-acts-verification-attestations/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-verification-attestations.md

- **eIDAS - EUDI Wallet core acts (standards update)**: Understand Implementing Regulation (EU) 2026/1731, which updates the standards and specifications across four core EUDI Wallet implementing acts.
  URL: https://docs.igrant.io/regulations/implementing-acts-wallet-standards-update/
  Markdown: https://docs.igrant.io/regulations/implementing-acts-wallet-standards-update.md

- **eIDAS and EU Regulations**: Reference documentation for the European regulations underpinning the EUDI Wallet ecosystem, including eIDAS, GDPR, Data Governance Act, and Data Act.
  URL: https://docs.igrant.io/regulations/
  Markdown: https://docs.igrant.io/regulations.md

- **Data Agreement Vocab - Version 1.0**: The Data Agreement Vocabulary provides terms to describe and represent information related to processing of personal data based on established requirements such as for the EU General Data Protection R...
  URL: https://docs.igrant.io/schema/data-agreements/v1.0
  Markdown: https://docs.igrant.io/schema/data-agreements/v1.0.md

- **Data Disclosure Agreement Vocab - Version 1.0**: The Data Disclosure Agreement Vocabulary provides terms to describe and represent information related to processing of personal data based on established requirements such as for the EU General Data P...
  URL: https://docs.igrant.io/schema/data-disclosure-agreements/v1.0
  Markdown: https://docs.igrant.io/schema/data-disclosure-agreements/v1.0.md

- **Data Agreement Vocab - Version 1.1**: The Data Agreement Vocabulary provides terms to describe and represent information related to processing of personal data based on established requirements such as for the EU General Data Protection R...
  URL: https://docs.igrant.io/schema/data-agreements/v1.1
  Markdown: https://docs.igrant.io/schema/data-agreements/v1.1.md

- **Data Disclosure Agreement Vocab - Version 1.0**: The Data Agreement Vocabulary provides terms to describe and represent information related to processing of personal data based on established requirements such as for the EU General Data Protection R...
  URL: https://docs.igrant.io/dda/data-disclosure-agreements/v1.0
  Markdown: https://docs.igrant.io/dda/data-disclosure-agreements/v1.0.md

## Contact Information

- **Support**: support@igrant.io
- **GitHub**: https://github.com/L3-iGrant
- **Website**: https://igrant.io

---

This llms.txt file was generated automatically to help AI assistants understand the content and structure of this documentation site.
Last updated: 2026-09-03T12:49:20.622Z
Total files: 444