Unreleased documentation. These pages follow the main branch and can change before the next release. For supported guidance, use v0.15.2.
Produce ordered evidence outcomes for several subjects
const url = 'https://example.com/v1/evidence/batch';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"items":[{"requestNonce":"example","subjects":[{"role":"example","selector":{"profile":"example","values":{"additionalProperty":"example"}}}]}],"purpose":"example","requirement":"https://example.com"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/v1/evidence/batch \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "items": [ { "requestNonce": "example", "subjects": [ { "role": "example", "selector": { "profile": "example", "values": { "additionalProperty": "example" } } } ] } ], "purpose": "example", "requirement": "https://example.com" }'The exact application/vnd.registrystack.evidence.request-batch+json Accept value selects this signed-JWS-only operation. The request carries one common requirement and purpose and between one and sixteen ordered subject items. The authenticated token supplies the common audience. Every item is validated and authorized before source access, and rate admission costs the complete item count atomically. Singular unavailable outcomes appear positionally inside a 200 response. Any other failure aborts the complete request. The serialized response is limited to 1048576 bytes and is released only after one durable terminal audit event.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”object
Examplegenerated
{ "items": [ { "requestNonce": "example", "subjects": [ { "role": "example", "selector": { "profile": "example", "values": { "additionalProperty": "example" } } } ] } ], "purpose": "example", "requirement": "https://example.com"}Responses
Section titled “Responses”One ordered signed-evidence or evidence-not-available result per request item
object
Example
{ "items": [ { "result": "evidence" } ], "schema": "registry.evidence-request-batch/v1", "type": "EvidenceRequestBatchResponse"}Headers
Section titled “Headers”Evidence responses are never cacheable.
The response format is negotiated through the exact Accept matrix.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.
Malformed batch request or invalid selector
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
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.
The response format is negotiated through the exact Accept matrix.
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.
The response format is negotiated through the exact Accept matrix.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.
At least one batch item is not authorized for signed audience-scoped evidence
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.denied", "detail": "the Evidence request is not permitted", "status": 403, "title": "Evidence request is not permitted", "type": "https://id.registrystack.org/problems/registry-evidence/evidence/denied"}Headers
Section titled “Headers”Evidence responses are never cacheable.
The response format is negotiated through the exact Accept matrix.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.
The exact request-batch response media type was not selected
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": "format.unsupported", "detail": "the requested format is not supported", "status": 406, "title": "Requested format is not supported", "type": "https://id.registrystack.org/problems/registry-evidence/format/unsupported"}Headers
Section titled “Headers”Evidence responses are never cacheable.
The response format is negotiated through the exact Accept matrix.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.
Atomic item-count rate admission was refused
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.
The response format is negotiated through the exact Accept matrix.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.
A dependency, protocol, signing, serialization, or audit failure aborted the complete 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
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": "source.unavailable", "detail": "the authoritative source is unavailable", "status": 503, "title": "Authoritative source is unavailable", "type": "https://id.registrystack.org/problems/registry-evidence/source/unavailable"}Headers
Section titled “Headers”Evidence responses are never cacheable.
The response format is negotiated through the exact Accept matrix.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.