---
title: "OpenID Metadata"
description: "Via the openid-metadata config, the verifier service can be configured to expose details such as verifier name and logo in a standardized way with other services such as digital wallets. These services can then use this…"
stack: "Enterprise Stack (commercial) — version 0.21.0"
stack_version: "0.21.0"
stack_comparison: https://docs.walt.id/community-vs-enterprise.md
canonical_url: https://docs.walt.id/enterprise-stack/services/verifier-service/configurations/openid-metadata
generated: 2026-07-20
---
# OpenID Metadata

Via the openid-metadata config, the verifier service can be configured to expose details such as verifier name and logo
in a
standardized way with other services such as digital wallets. These services can then use this information to display
a human-readable verifier name and logo to the end-user during credential exchange.

Learn more about the `name` and `logo` info exposure in the OAuth 2.0
standard [here](https://www.rfc-editor.org/rfc/rfc7591.html#section-2:~:text=code%22%20response%20type.-,client_name%0A%20%20%20%20%20%20Human%2Dreadable%20string%20name%20of%20the%20client%20to%20be%20presented,this%20field%20MAY%20be%20internationalized%2C%20as%20described%20in%0A%20%20%20%20%20%20Section%202.2.,-scope%0A%20%20%20%20%20%20String%20containing).

The configured info will be exposed via the public
endpoint `/.well-known/openid-configuration`.

## Get OpenID Metadata

**Option: CURL**

Endpoint: `/v1/{target}/verifier-service-api/configuration/openid-metadata/view` | [API Reference](https://enterprise.sandbox.walt.id/swagger/index.html#/Service%20%7C%20Verifier/get_v1__target__verifier_service_api_configuration_openid_metadata_view)

**Example Request**

```bash
curl -X 'GET' \
  'https://{orgID}.enterprise-sandbox.waltid.dev/v1/{target}/verifier-service-api/configuration/openid-metadata/view' \
  -H 'Authorization: Bearer {yourToken}' \
  -H 'Content-Type: application/json'
```

**Path Parameters**

- `orgID`: - When performing operations within an organization, it is essential to use the organization's Base URL or
  another valid host alias. For example, if your organization is named `test`, your default Base URL will
  be `test.enterprise-sandbox.walt.dev` when using the sandbox environment.
- `target`: _resourceIdentifier_ - The target indicates the organization + tenant + verifier service from which to receive
  the configuration(`{organizationID}.{tenantID}.{verifierServiceID}`), e.g. `waltid.tenant1.verifier1`

**Example Response**

- `200` - metadata retrieved successfully.

```json
{
  "name": "walt.id Enterprise Verifier",
  "logoUri": "http://cdn.walt.id/verifier/logo.png"
}
```

- `name` _String_: Human-readable string name of the verifier.
- `logoUri` _String_: URL string that references a logo for the verifier.

**Note:**

  If no metadata is setup the body will be empty.

- `401` - Invalid authentication

## Update OpenID Metadata

**Option: CURL**

Endpoint: `/v1/{target}/verifier-service-api/configuration/openid-metadata/update` | [API Reference](https://enterprise.sandbox.walt.id/swagger/index.html#/Service%20%7C%20Verifier/get_v1__target__verifier_service_api_configuration_openid_metadata_view)

**Example Request**

```bash
curl -X 'PUT' \
  'https://{orgID}.enterprise-sandbox.waltid.dev/v1/{target}/verifier-service-api/configuration/openid-metadata/update' \
  -H 'Authorization: Bearer {yourToken}' \
  -H 'Content-Type: application/json' \
  -d '{
  "name": "walt.id Enterprise Verifier",
  "logoUri": "http://cdn.walt.id/verifier/logo.png"
}'
```

**Path Parameters**

- `orgID`: - When performing operations within an organization, it is essential to use the organization's Base URL or
  another valid host alias. For example, if your organization is named `test`, your default Base URL will
  be `test.enterprise-sandbox.walt.dev` when using the sandbox environment.
- `target`: _resourceIdentifier_ - The target indicates the organization + tenant + verifier service in which to update
  the configuration(`{organizationID}.{tenantID}.{verifierServiceID}`), e.g. `waltid.tenant1.verifier1`

**Body**

```json
{
  "name": "walt.id Enterprise Verifier",
  "logoUri": "http://cdn.walt.id/verifier/logo.png"
}
```

**Body Parameters**

- `name` (optional) _String_: Human-readable string name of the verifier.
- `logoUri` (optional) _String_: URL string that references a logo for the verifier.

---

**Example Response**

- `200` - metadata updated successfully.

```json
{
  "name": "walt.id Enterprise Verifier",
  "logoUri": "http://cdn.walt.id/verifier/logo.png"
}
```

- `401` - Invalid authentication

## Delete OpenID Metadata

**Option: CURL**

Endpoint: `/v1/{target}/verifier-service-api/configuration/openid-metadata/delete` | [API Reference](https://enterprise.sandbox.walt.id/swagger/index.html#/Service%20%7C%20Verifier/delete_v1__target__verifier_service_api_configuration_openid_metadata_delete)

**Example Request**

```bash
curl -X 'DELETE' \
  'https://{orgID}.enterprise-sandbox.waltid.dev/v1/{target}/verifier-service-api/configuration/openid-metadata/delete' \
  -H 'accept: */*' \
  -H 'Authorization: Bearer {yourToken}' 
```

**Path Parameters**

- `orgID`: - When performing operations within an organization, it is essential to use the organization's Base URL or
  another valid host alias. For example, if your organization is named `test`, your default Base URL will
  be `test.enterprise-sandbox.walt.dev` when using the sandbox environment.
- `target`: _resourceIdentifier_ - The target indicates the organization + tenant + verifier service in which to delete
  the configuration(`{organizationID}.{tenantID}.{verifierServiceID}`), e.g. `waltid.tenant1.verifier1`

---

**Example Response**

- `200` - metadata deleted successfully.

- `401` - Invalid authentication