Skip to main content
Decode the JSON response and use the status with the endpoint’s mutation contract to choose the recovery action.

Authentication

Authenticated routes return 401 for a missing or invalid bearer token. On the hosted API, the proxy derives the session from the token and replaces a body session_id.

Status families

Use the selected endpoint contract for its supported status codes.

Reads and writes

POST /api/v1/domains/{domain_id}/adapt/events, normal domain events, feedback, and State writes can mutate persistent or adaptive state. Use stable identifiers and inspect available state before replaying an ambiguous write. POST /api/v1/domains/{domain_id}/adapt/predict reads the current adaptive prediction without adding an observation.

Isolation

A bearer token maps to the hosted session identity. Use fresh domain_id values for independent Domain workflows and structured run_id metadata to correlate their records. Independent State scopes require separate authenticated identities. Run one writer per online adaptive Domain unless interleaving is intended.

Recovery sequence

classify response → back off if transient → inspect state if write was ambiguous → resume from checkpoint See Operate stateful and adaptive workflows for ordering, identifiers, and reset behavior.

Public API limits

A 413 response means the request exceeded its payload limit. For admission-capacity responses such as 429, honor Retry-After when present and use bounded exponential backoff. Batch store preserves items completed before a later failure. Reconcile a failed write from available state or returned item results before resubmitting it.