Read No-show posting rule as of a watermark
const url = 'https://api.aerandil.com/v1/object-types/hospitality.no_show_posting_rule/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/as-of?at=example';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://api.aerandil.com/v1/object-types/hospitality.no_show_posting_rule/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/as-of?at=example' \ --header 'Authorization: Bearer <token>'Time-travel read: the instance as it stood at the at watermark, reconstructed by folding its structural events. Property values that were marking-redacted or truncated in the event log surface as sentinel objects, not values.
One property’s no-show posting rule for one reservation guarantee (OPERA’s Post Revenue To No Shows): when the night audit marks a booking of that guarantee a no-show, it posts all_nights (every booked night’s rate, as booked), first_night (the first night of every room), deposit_only (forfeits the deposit the house holds, nothing when it holds none) or none. Postings land on the booking’s own account through the posting verbs, attributed to the rule’s outlet_id; a deposit already on that account offsets them. A rule with no guarantee is the house default for every guarantee without a rule of its own; a house with no rule posts nothing. A booking a rule covers is posted by the rule alone — the frozen cancellation-policy fee step (post_no_show_fees) skips it, so one no-show is posted once.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Object id (UUID v7, server-generated at create time).
Query Parameters
Section titled “Query Parameters”The watermark: an event seq (integer, canonical — the /v1/events cursor namespace) or an RFC3339 timestamp (resolved to the latest seq at or before it in the tenant’s stream).
Responses
Section titled “Responses”The reconstructed as-of state.
object
Log-shaped folded bag: each entry is a typed {kind, value} object, a {redacted: [markings]} sentinel, or a {truncated_bytes: n} sentinel.
object
Example
{ "object_type": "hospitality.no_show_posting_rule"}Object did not exist at the watermark (not yet created, or already deleted).
Malformed at, or the object’s history predates structural event images and cannot back a faithful reconstruction.