Skip to main content

List trust authority

GET 
/v2/config/digital-wallet/openid/trust-authorities

Lists the trust authorities of the organisation. The service uses these trust lists to validate issuers and verifiers in OID4VCI and OpenID4VP flows.

The list starts with two built-in trust lists that the service returns for every organisation. They have the IDs 0 and 1, and disabled, createdAt and updatedAt always hold false, 0 and 0 for them. The trust authorities that the organisation created come after them. pagination.totalItems counts the two built-in records, and they fill the first page.

The largest value of limit is 100. A larger value gives HTTP 400.

Request​

Query Parameters

    offset integerrequired

    Default value: 0

    Number of records to skip for pagination. A negative or unreadable value falls back to 0.

    limit integerrequired

    Default value: 10

    Maximum number of records to return per page.

Header Parameters

    X-SandboxOrgId stringrequired

    Optional. Unique identifier of the sandbox organisation to use for this request. When you send this header, the service runs the operation in the context of the named sandbox organisation, that is, against the wallet of that sandbox organisation and not against the main wallet of the organisation. Leave the header out to use the main wallet.

    The service reads this header only when you authenticate with a bearer access token. When you authenticate with an API key, the service takes the sandbox organisation from the API key and ignores this header. To run an API-key call in a sandbox organisation, bind the key to the sandbox organisation with PUT /v2/config/admin/apikey/{apiKeyId}/sandbox-org instead.

    X-SubwalletId is the deprecated name of this header. The service continues to accept it, but X-SandboxOrgId wins if you send both headers.

    The sandbox organisation must exist, must belong to your organisation and must be deployed. An unknown identifier, an identifier of a sandbox organisation that is not deployed, and an identifier that belongs to a different organisation all make the call fail with HTTP 400.

    Example: 6889e1a4c5b2f30001a3d710

Responses​

The service returns the trust authorities and the pagination data.

Response Headers
    Schema
      trustAuthority object[]required

      The trust authorities on the current page. The first two records are the built-in trust lists, which have the IDs 0 and 1.

    • Array [
      • id stringrequired

      Unique identifier of the trust authority record. Records that the organisation created have a UUID. The two built-in trust lists have the identifiers 0 and 1, and you cannot read, update, toggle or delete them with the per-identifier operations.

      type stringrequired

      Possible values: [ETSI_TL]

      Type of the trust list. The service accepts ETSI_TL (ETSI TS 119 612 trusted list) only.

      value stringrequired

      Location of the trust list. For the ETSI_TL type, this is the HTTP or HTTPS URL of the trusted list document.

      name stringrequired

      Name of the trust authority. The value is an empty string when the create or update request gave no name.

      disabled booleanrequired

      When true, this trust authority is disabled and not used for credential or verifier trust validation. The two built-in trust lists always return false.

      createdAt numberrequired

      Unix timestamp (in seconds) when this trust authority was registered. The two built-in trust lists always return 0.

      updatedAt numberrequired

      Unix timestamp (in seconds) when this trust authority was last modified. The two built-in trust lists always return 0.

    • ]
      • pagination objectrequired
      currentPage integer

      Current page number

      totalItems integer

      Total number of items available

      totalPages integer

      Total number of pages based on limit

      limit integer

      Number of items per page

      hasPrevious boolean

      Indicates if there's a previous page

      hasNext boolean

      Indicates if there's a next page

    Loading...
    Last updated on