Move room (in-house)
const url = 'https://api.aerandil.com/v1/actions/hospitality.action.move_room/apply';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"branch":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","params":{"allow_dirty_room":true,"new_room_id":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","old_room_status":"dirty","override_nightly_rate":{"amount":"example","currency":"example"},"override_reason":"example","pricing_policy":"keep_rate","reason":"example","reservation_room_id":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0"},"return_modified":false,"target":{"id":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","object_type":"hospitality.reservation"}}'};
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://api.aerandil.com/v1/actions/hospitality.action.move_room/apply \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "branch": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "params": { "allow_dirty_room": true, "new_room_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "old_room_status": "dirty", "override_nightly_rate": { "amount": "example", "currency": "example" }, "override_reason": "example", "pricing_policy": "keep_rate", "reason": "example", "reservation_room_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" }, "return_modified": false, "target": { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "object_type": "hospitality.reservation" } }'Move an in-house guest to another room in one atomic verb (pre-check-in moves are assign_room_for_reservation_room). The target room must be vacant, in the same property, and not out-of-order for the remaining stay; a dirty or pickup room needs an explicit allow_dirty_room acknowledgment. On a cross-type move the remaining (unslept) nights settle the availability ledger atomically — a sold-out night refuses the whole move, naming the night — and the required pricing_policy decides the money: keep_rate pins reservation_room_charged_as_room_type (the comp upgrade — the guest sleeps in the new type, keeps paying the old one); requote re-prices remaining nights from the new type’s published grid; override takes the supplied rate with its reason. The old room is vacated into a declared housekeeping status (old_room_status, default dirty), the new room becomes occupied, and the emitted event is the permanent move history.
Effects: modify hospitality.room; modify hospitality.availability_day; modify hospitality.reservation_night; modify hospitality.room_discrepancy; link hospitality.link.stay_in_room; unlink hospitality.link.stay_in_room; link hospitality.link.reservation_room_assigned_to; unlink hospitality.link.reservation_room_assigned_to; link hospitality.link.reservation_room_for_room_type; unlink hospitality.link.reservation_room_for_room_type; link hospitality.link.reservation_room_charged_as_room_type; unlink hospitality.link.reservation_room_charged_as_room_type.
Step-up when pricing_policy is override: a person (a User principal) needs a fresh desk step-up proof — Pricing nights at a typed-in rate overrides the house’s published price — or the call is refused 403 step_up_required before anything runs. Re-enter the passcode at POST /v1/desk/sessions/{id}/passcode and retry. Machine principals are not gated.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”object
Apply against an open branch’s overlay view instead of the canonical (main) plane. The action’s writes land in the branch’s copy-on-first-write overlay, its events in the branch’s own stream, and the invocation is journaled for merge-by-replay. Branch writes are action-only, so this is the write-side entry point to a branch (POST /v1/branches forks one).
object
object
When true, the response carries modified_objects and modified_links projections — the engine reads the event log inside the same transaction so the projection observes the handler’s own writes.
object
Responses
Section titled “Responses”Action applied. modified_objects and modified_links populated when return_modified: true was supplied.
Envelope returned by the Aerandil action engine. correlation_id ties every event emitted by this invocation; modified_objects and modified_links project the events the handler emitted (per the action’s declared effects); warnings carries any non-blocking soft-validator observations.
object
Per-invocation correlation id; matches events.correlation_id for every event this action appended.
Links established or removed by this invocation. Empty when the caller did not request return_modified.
object
Objects created, modified, or soft-deleted by this invocation. Empty when the caller did not request return_modified.
object
Non-blocking soft-validator observations emitted during this invocation (e.g. comp-authority over-limit, recipe pour-cost over sell-price). Absent when no warnings were emitted.
object
Human-readable summary, suitable for logging or operator-UI surfacing.
Object type the warning was raised against.
Property the warning anchors to, when a single field is the locus. Absent for multi-field rules.
Stable kebab-case rule identifier (e.g. comp-authority-over-limit).
Example
{ "modified_links": [ { "kind": "linked", "link_type": "hospitality.link.stay_in_room" } ], "modified_objects": [ { "kind": "modified", "object_type": "hospitality.room" } ]}step_up_required — a person applied this without a fresh desk step-up proof; nothing ran.
Conflict — concurrent modification or unique constraint violation.
Validation error — parameter validation or business-rule violation.