Unreleased documentation. These pages follow the main branch and can change before the next release. For supported guidance, use v0.15.2.
Publish JWT VC Issuer Metadata for the SD-JWT VC response format
GET
/.well-known/jwt-vc-issuer
const url = 'https://example.com/.well-known/jwt-vc-issuer';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/.well-known/jwt-vc-issuerDiscovery is not a trust anchor. The document republishes the same public keys under the provider identity the assertion names, and resolution is meaningful only when that identity is the HTTPS origin of the deployment.
Responses
Section titled “Responses”Provider identity and public verification keys
Media typeapplication/json
object
issuer
required
string
jwks_uri
required
string format: uri
Examplegenerated
{ "issuer": "example", "jwks_uri": "https://example.com"}Headers
Section titled “Headers”Cache-Control
string
Evidence responses are never cacheable.
X-Request-Id
string
Server-minted operation identifier for this request. It is generated by Evidence, never taken from the caller, and is the identifier a caller quotes to an operator. Problem responses repeat it in the operation member.