Publish the active and retained public verification keys

GET

/.well-known/evidence/jwks.json

const url = 'https://example.com/.well-known/evidence/jwks.json';
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/evidence/jwks.json

Responses

200

Evidence public verification keys

application/jwk-set+json

Evidence public JWKS Version 1

object

keys

required

Array<object>

>= 1 items <= 33 items unique items

object

alg

required

string

Allowed values: ES256

crv

required

string

Allowed values: P-256

kid

required

string

/^[A-Za-z0-9_-]{43}$/

kty

required

string

Allowed values: EC

required

string

/^[A-Za-z0-9_-]{43}$/

required

string

/^[A-Za-z0-9_-]{43}$/

Example

{
  "keys": [
    {
      "alg": "ES256",
      "crv": "P-256",
      "kty": "EC"
    }
  ]
}

Headers

Cache-Control

string

Allowed values: no-store

Evidence responses are never cacheable.

X-Request-Id

string

/^[0-9A-HJKMNP-TV-Z]{26}$/

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.