Unreleased documentation. These pages follow the main branch and can change before the next release. For supported guidance, use v0.26.1.
List the complete Evidence request shapes available to the authenticated caller
const url = 'https://example.com/v1/evidence-definitions';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
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/v1/evidence-definitions \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Responses
Section titled “ Responses ”Requester-scoped Evidence definitions
object
object
What the subject bindings in this requirement’s assertions are derived under. The vocabulary is closed and carries no default: absence means audience-scoped, stated here so a relying party reading a definition without the key knows the requirement issues audience-scoped assertions and is not reading an omission it has to resolve elsewhere. A definition that does carry the key states the mode explicitly.
object
object
object
object
object
object
object
The effective deployment ceiling for one holder-bound batch. A protocol adapter may advertise no larger batch than this value.
Example
{ "assuranceProfile": "local", "definitions": [ { "concepts": [ { "form": "boolean" } ], "kind": "criterion", "responseFormats": [ "signed-jws" ], "subjectBindingMode": "audience-scoped", "subjects": [ { "cardinality": "one", "selector": { "fields": [ { "type": "string" } ], "valueOrigin": "request" } } ] } ], "schema": "registry.evidence-definitions/v1"}Headers
Section titled “Headers”Evidence responses are never cacheable.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.
Malformed discovery request
object
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
object
object
object
object
object
object
object
object
object
object
Example
{ "code": "evidence.invalid_request", "detail": "the Evidence request is invalid", "status": 400, "title": "Evidence request is invalid", "type": "https://id.registrystack.org/problems/registry-evidence/evidence/invalid_request"}Headers
Section titled “Headers”Evidence responses are never cacheable.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.
Authentication failed
object
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
object
object
object
object
object
object
object
object
object
object
Example
{ "code": "auth.invalid_credential", "detail": "bearer access token validation failed", "status": 401, "title": "Bearer access token is invalid", "type": "https://id.registrystack.org/problems/registry-evidence/auth/invalid_credential"}Headers
Section titled “Headers”Evidence responses are never cacheable.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.
Request rate exceeded
object
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
object
object
object
object
object
object
object
object
object
object
Example
{ "code": "evidence.rate_limited", "detail": "the Evidence request rate is exhausted", "status": 429, "title": "Evidence request rate is exhausted", "type": "https://id.registrystack.org/problems/registry-evidence/evidence/rate_limited"}Headers
Section titled “Headers”Evidence responses are never cacheable.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.
Service temporarily unavailable
object
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
- Evidence public problem Version 1
object
object
object
object
object
object
object
object
object
object
Example
{ "code": "service.unavailable", "detail": "the request could not be served", "status": 503, "title": "Service is unavailable", "type": "https://id.registrystack.org/problems/registry-evidence/service/unavailable"}Headers
Section titled “Headers”Evidence responses are never cacheable.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.