Skip to content

Transition the fulfillment state

Hospitality module

POST/fulfillments/{id}/transitionsfulfillments.transition

Moves the fulfillment lifecycle to another state through its transition RPC, which writes the transition ledger. Uses compare-and-set on `expected_state`; a disallowed transition returns a 422 refusal. Requires `Idempotency-Key`; a replay returns the original response. A rule that refuses the request returns 422 with `refusal` and `reason`.

  • Requires the capability hospitality.fulfillment.write.
  • OAuth scopes: hospitality.
  • Send an Idempotency-Key header. A replay with the same key returns the original response.
  • Error statuses: 400, 401, 404, 409, 422, 429. Errors are RFC 9457 problem details.

Path and query parameters

fulfillments.transition: Path and query parameters
FieldTypeRequiredDescription
idstring (uuid)YesIdentifier of the fulfillment.

Request body: FulfillmentTransitionRequest

fulfillments.transition: FulfillmentTransitionRequest
FieldTypeRequiredDescription
expected_statestringYesThe state the caller believes the row is in (compare-and-set).Constraints: pattern ^[A-Z][A-Za-z]*( [A-Z][A-Za-z]*)*$
to_statestringYesTarget state.Constraints: pattern ^[A-Z][A-Za-z]*( [A-Z][A-Za-z]*)*$
reasonstringNoReason, required by some transitions.Constraints: length 1 to any
{
  "expected_state": "Proposed",
  "to_state": "Active",
  "reason": "Client approved the revised scope."
}

Response 200: Fulfillment

fulfillments.transition: Fulfillment
FieldTypeRequiredDescription
idstring (uuid)YesIdentifier of the fulfillment.
org_idstring (uuid)YesIdentifier of the owning organization, derived from the parent row and never accepted from the caller.
created_atstring (date-time)YesWhen the row was created.
created_bystring (uuid) | nullYesIdentifier of the person who created the row; null when a seed, platform or system process created it.
updated_atstring (date-time)YesWhen the row was last updated.
updated_bystring (uuid) | nullYesIdentifier of the person who last updated the row; null when a seed, platform or system process updated it.
project_idstring (uuid)YesIdentifier of the project.
fulfillment_kindFulfillmentKindYesHospitality fulfillment kind.Constraints: one of "Lodging", "Catering", "Travel", "Amenity"
titlestringYesFulfillment title.Constraints: length 1 to 300
fulfillment_state"Proposed" | "Active" | "Blocked" | "Complete" | "Canceled"YesFulfillment state.
starts_atstring (date-time) | nullYesService start.
ends_atstring (date-time) | nullYesService end.
counterparty_idstring (uuid) | nullYesIdentifier of the supplier, such as the hotel or caterer.
fulfillment_numberintegerYesNumber within the project; the display key is {project_key}-{fulfillment_number}.Constraints: range 1 to any
{
  "id": "0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f",
  "org_id": "0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f",
  "created_at": "2026-10-08T14:30:00Z",
  "created_by": "0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f",
  "updated_at": "2026-10-08T14:30:00Z",
  "updated_by": "0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f",
  "project_id": "0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f",
  "fulfillment_kind": "Lodging",
  "title": "Headliner Hotel Block",
  "fulfillment_state": "Proposed",
  "starts_at": "2026-10-08T14:30:00Z",
  "ends_at": "2026-10-08T14:30:00Z",
  "counterparty_id": "0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f",
  "fulfillment_number": 3
}

Code samples

curl -X POST "$XOS_BASE_URL/fulfillments/0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f/transitions" \
  -H "Authorization: Bearer $XOS_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"expected_state":"Proposed","to_state":"Active","reason":"Client approved the revised scope."}'
const { data } = await xos.fulfillments.transition("0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f", {
    "expected_state": "Proposed",
    "to_state": "Active",
    "reason": "Client approved the revised scope."
  });
response = xos.fulfillments.transition("0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f", {"expected_state": "Proposed", "to_state": "Active", "reason": "Client approved the revised scope."})
xos fulfillments transition 0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f --data '{"expected_state":"Proposed","to_state":"Active","reason":"Client approved the revised scope."}'