Reconcile a bounded source-owned busy snapshot
const url = 'https://scheduling.example.test/v1/source-busy/apply?profile=example';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"coverage":{"end":"2026-04-15T12:00:00Z","resources":["example"],"start":"2026-04-15T12:00:00Z"},"expectedRevision":1,"freshUntil":"2026-04-15T12:00:00Z","observedAt":"2026-04-15T12:00:00Z","records":[{"end":"2026-04-15T12:00:00Z","externalRevision":"example","externalUid":"example","resource":"example","start":"2026-04-15T12:00:00Z"}],"status":"fresh"}'};
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://scheduling.example.test/v1/source-busy/apply?profile=example' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "coverage": { "end": "2026-04-15T12:00:00Z", "resources": [ "example" ], "start": "2026-04-15T12:00:00Z" }, "expectedRevision": 1, "freshUntil": "2026-04-15T12:00:00Z", "observedAt": "2026-04-15T12:00:00Z", "records": [ { "end": "2026-04-15T12:00:00Z", "externalRevision": "example", "externalUid": "example", "resource": "example", "start": "2026-04-15T12:00:00Z" } ], "status": "fresh" }'Atomically applies a bounded snapshot under expectedRevision and a canonical request digest, preserving facts outside the source authority and coverage. After an uncertain reply, replay the exact body and expectedRevision: retained exact replay returns already-applied. A different stale request returns HTTP 412 revision.mismatch. A later conflict does not establish that an earlier attempt failed. There is no Idempotency-Key header and clients do not retry automatically. Unavailable or expired required-source coverage prevents new allocations without cancelling existing commitments. Input bounds and minimized impact projection match preview.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Header Parameters
Section titled “Header Parameters”Optional W3C trace context continued in the response.
Query Parameters
Section titled “Query Parameters”One explicit configured import profile; profiles are never combined.
Request Bodyrequired
Section titled “Request Bodyrequired”object
object
object
Responses
Section titled “Responses”Success
object
object
object
Example
{ "kind": "applied"}Headers
Section titled “Headers”Every answer is marked no-store, so a booking view is never served from a cache.
W3C trace context for the request and response.
Problem response: request.invalid
object
Example
{ "code": "request.invalid", "detail": "The request could not be read as a Scheduling request.", "status": 400, "title": "Request invalid", "type": "https://id.registrystack.org/problems/registry-scheduling/request/invalid"}Headers
Section titled “Headers”Every answer is marked no-store, so a booking view is never served from a cache.
W3C trace context for the request and response.
Problem response: authentication.refused
object
Example
{ "code": "authentication.refused", "detail": "The bearer credential is missing, invalid, or expired. Sign in again.", "status": 401, "title": "Authentication refused", "type": "https://id.registrystack.org/problems/registry-scheduling/authentication/refused"}Headers
Section titled “Headers”Bearer authentication challenge.
Every answer is marked no-store, so a booking view is never served from a cache.
W3C trace context for the request and response.
Problem response: profile.not-authorized
object
Example
{ "code": "profile.not-authorized", "detail": "The selected Scheduling profile does not authorize this request.", "status": 403, "title": "Profile not authorized", "type": "https://id.registrystack.org/problems/registry-scheduling/profile/not-authorized"}Headers
Section titled “Headers”Every answer is marked no-store, so a booking view is never served from a cache.
W3C trace context for the request and response.
Problem response: request.method-not-allowed
object
Example
{ "code": "request.method-not-allowed", "detail": "The route exists but not for this method.", "status": 405, "title": "Method not allowed", "type": "https://id.registrystack.org/problems/registry-scheduling/request/method-not-allowed"}Headers
Section titled “Headers”Every answer is marked no-store, so a booking view is never served from a cache.
W3C trace context for the request and response.
Problem response: resource.unavailable
object
Example
{ "code": "resource.unavailable", "detail": "Every capable member is unavailable for this interval.", "status": 409, "title": "Resource unavailable", "type": "https://id.registrystack.org/problems/registry-scheduling/resource/unavailable"}Headers
Section titled “Headers”Every answer is marked no-store, so a booking view is never served from a cache.
W3C trace context for the request and response.
Problem response: revision.mismatch, precondition.failed
object
object
Example
{ "code": "revision.mismatch", "detail": "The observed revision is no longer current.", "status": 412, "title": "Revision mismatch", "type": "https://id.registrystack.org/problems/registry-scheduling/revision/mismatch"}Headers
Section titled “Headers”Every answer is marked no-store, so a booking view is never served from a cache.
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 accepted size.", "status": 413, "title": "Payload too large", "type": "https://id.registrystack.org/problems/registry-scheduling/request/body-too-large"}Headers
Section titled “Headers”Every answer is marked no-store, so a booking view is never served from a cache.
W3C trace context for the request and response.
Problem response: request.unsupported-media-type
object
Example
{ "code": "request.unsupported-media-type", "detail": "The request body is not JSON.", "status": 415, "title": "Unsupported media type", "type": "https://id.registrystack.org/problems/registry-scheduling/request/unsupported-media-type"}Headers
Section titled “Headers”Every answer is marked no-store, so a booking view is never served from a cache.
W3C trace context for the request and response.
Problem response: request.unprocessable
object
Example
{ "code": "request.unprocessable", "detail": "The request body could not be processed.", "status": 422, "title": "Request unprocessable", "type": "https://id.registrystack.org/problems/registry-scheduling/request/unprocessable"}Headers
Section titled “Headers”Every answer is marked no-store, so a booking view is never served from a cache.
W3C trace context for the request and response.
Problem response: service.unavailable
object
Example
{ "code": "service.unavailable", "detail": "Scheduling storage is unavailable. Try again after the service recovers.", "status": 503, "title": "Scheduling service unavailable", "type": "https://id.registrystack.org/problems/registry-scheduling/service/unavailable"}Headers
Section titled “Headers”Seconds before retrying the unavailable dependency; the runtime answers 5.
Every answer is marked no-store, so a booking view is never served from a cache.
W3C trace context for the request and response.