Skip to content
aerandil.com
GitHub

What-if Update automation (rollup delta)

POST
/v1/actions/hospitality.action.update_automation/whatif
curl --request POST \
  --url https://api.aerandil.com/v1/actions/hospitality.action.update_automation/whatif \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "branch": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "params": { "approval_policy_ref": "example", "cron_expression": "example", "description_text": "example", "display_name": "example", "effect_notification_template": "example", "effect_params_template": {}, "execution_mode": "per_object", "max_cascade_depth": 1, "modified_property_watch": "example", "object_set_filter": "example", "requires_approval": true }, "return_modified": false, "target": { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "object_type": "hospitality.automation" } }'

What-if projection of apply_hospitality_action_update_automation — previews the action (execute-and-roll-back) and folds its would-be events into rollup deltas, returning the contribution an apply would make to the daily_rooms fact (ADR / RevPAR / TRevPAR / Occupancy inputs) without persisting anything. Requires the same actions:hospitality.action.update_automation:apply scope as apply. An action that emits no rooms-fact events yields an empty daily_rooms.

Authorizations

Section titled “Authorizations”

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
object
branch

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).

string format: uuid
params
required
object
approval_policy_ref
New approval policy ref
string
cron_expression
New cron schedule
string
description_text
New description
string
display_name
New human-readable name
string
effect_notification_template
New notification template (JSON)
effect_params_template
New effect-input template (JSON)
object
key
additional properties
any
execution_mode
New execution mode
string
Allowed values: per_object batch
max_cascade_depth
New cascade-depth guard
integer
modified_property_watch
New modified-property watch (JSON array)
object_set_filter
New watched-set filter (JSON)
requires_approval
New approval-routing flag
boolean
return_modified

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.

boolean
target
required
object
id
required
string format: uuid
object_type
required
Allowed value: hospitality.automation

Responses

Section titled “Responses”

200

Section titled “200”

Rollup deltas the action would contribute, computed and rolled back.

Media typeapplication/json
object
daily_rooms
required

Per (property, business_date) additive contribution to the rooms rollup.

Array<object>
object
business_date
required
string format: date
currency

ISO 4217, when the fold observed one.

string
property_id
required
string format: uuid
rooms_revenue_net_delta
required

Decimal, net rooms revenue delta.

string
rooms_sold_delta
required
integer format: int64
total_revenue_net_delta
required

Decimal, net total revenue delta.

string
Examplegenerated
{
  "daily_rooms": [
    {
      "business_date": "2026-04-15",
      "currency": "example",
      "property_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
      "rooms_revenue_net_delta": "example",
      "rooms_sold_delta": 1,
      "total_revenue_net_delta": "example"
    }
  ]
}

Headers

Section titled “Headers”
Cache-Control
string
Allowed value: no-store

Always no-store — derived, uncommitted data.

422

Section titled “422”

Validation error — the apply would be rejected.