Unreleased documentation. These pages follow the main branch and can change before the next release. For supported guidance, use v0.26.1.
Accept a signed source synchronization hint
const url = 'https://casework.example.test/events/sources/example';const options = { method: 'POST', headers: { 'ce-specversion': '1.0', 'ce-id': '2489E9AD-2EE2-8E00-8EC9-32D5F69181C0', 'ce-source': 'https://example.com', 'ce-type': 'example', 'ce-time': '2026-04-15T12:00:00Z', 'ce-dataschema': 'https://example.com', 'x-registry-event-generation': 'example', 'x-registry-delivery-attempt': 'example', 'x-registry-delivery-time': '2026-04-15T12:00:00Z', 'idempotency-key': 'example', 'x-registry-signature': 'example', 'X-Registry-Signature': '<X-Registry-Signature>', 'Content-Type': 'application/cloudevents+json' }, body: '{}'};
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://casework.example.test/events/sources/example \ --header 'Content-Type: application/cloudevents+json' \ --header 'X-Registry-Signature: <X-Registry-Signature>' \ --header 'ce-dataschema: https://example.com' \ --header 'ce-id: 2489E9AD-2EE2-8E00-8EC9-32D5F69181C0' \ --header 'ce-source: https://example.com' \ --header 'ce-specversion: 1.0' \ --header 'ce-time: 2026-04-15T12:00:00Z' \ --header 'ce-type: example' \ --header 'idempotency-key: example' \ --header 'x-registry-delivery-attempt: example' \ --header 'x-registry-delivery-time: 2026-04-15T12:00:00Z' \ --header 'x-registry-event-generation: example' \ --header 'x-registry-signature: example' \ --data '{}'Authentication uses the configured BReg webhook signature and timestamp headers. The raw body is bounded to 1 MiB and grants no authority or display content.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Configured source identifier.
Header Parameters
Section titled “Header Parameters”Optional W3C trace context continued in the response.
CloudEvents version; exactly 1.0.
Event UUID.
Configured exact event source URI.
Configured exact request-lifecycle event type.
Event timestamp.
Configured event data schema URI.
Activated positive BReg source generation.
Positive delivery attempt number.
Signed delivery timestamp.
Signed delivery key derived from the exact event, delivery, generation, payload, and destination binding.
BReg Version 1 HMAC-SHA-256 signature over the exact request.
Request Bodyrequired
Section titled “Request Bodyrequired”object
Examplegenerated
{}object
Examplegenerated
{}Responses
Section titled “Responses”Signature accepted; authoritative readback is scheduled.
Headers
Section titled “Headers”W3C trace context for the request and response.
Problem response: request.invalid, source.signature-invalid
object
object
Example
{ "code": "request.invalid", "detail": "The Casework request is invalid.", "status": 400, "title": "Invalid request", "type": "https://id.registrystack.org/problems/registry-casework/request/invalid"}Headers
Section titled “Headers”W3C trace context for the request and response.
Problem response: source.not-found
object
Example
{ "code": "source.not-found", "detail": "The requested source is not registered.", "status": 404, "title": "Source not found", "type": "https://id.registrystack.org/problems/registry-casework/source/not-found"}Headers
Section titled “Headers”W3C trace context for the request and response.
Problem response: request.method-not-allowed
object
Example
{ "code": "request.method-not-allowed", "detail": "This route does not accept that HTTP method.", "status": 405, "title": "Method not allowed", "type": "https://id.registrystack.org/problems/registry-casework/request/method-not-allowed"}Headers
Section titled “Headers”W3C trace context for the request and response.
Problem response: request.body-too-large
object
Example
{ "code": "request.body-too-large", "detail": "The request body exceeds the one MiB limit.", "status": 413, "title": "Request body too large", "type": "https://id.registrystack.org/problems/registry-casework/request/body-too-large"}Headers
Section titled “Headers”W3C trace context for the request and response.
Problem response: runtime.failure
object
Example
{ "code": "runtime.failure", "detail": "Casework could not complete the request.", "status": 500, "title": "Casework runtime failure", "type": "https://id.registrystack.org/problems/registry-casework/runtime/failure"}Headers
Section titled “Headers”W3C trace context for the request and response.
Problem response: source.bad-gateway
object
Example
{ "code": "source.bad-gateway", "detail": "The source returned a response that does not match its registered contract.", "status": 502, "title": "Invalid source response", "type": "https://id.registrystack.org/problems/registry-casework/source/bad-gateway"}Headers
Section titled “Headers”W3C trace context for the request and response.
Problem response: service.unavailable, work-item.source-unavailable
object
object
Example
{ "code": "service.unavailable", "detail": "Casework storage is unavailable. Try again after the service recovers.", "status": 503, "title": "Casework service unavailable", "type": "https://id.registrystack.org/problems/registry-casework/service/unavailable"}Headers
Section titled “Headers”Seconds before retrying the unavailable dependency.
W3C trace context for the request and response.