Skip to main content

Delete trust authority

DELETE 

/v2/config/digital-wallet/openid/trust-authority/:trustAuthorityId

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.

Request

Path Parameters

    trustAuthorityId uuidrequired

    Unique identifier of a trust authority of the organisation. The value must be a UUID, so the identifiers 0 and 1 of the two built-in trust lists are not valid here.

    Example: b7d1f4a2-8c3e-4a91-9f52-0d3c6e7a1b45

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 deleted the trust authority. The response has no body.

Response Headers
    Loading...