Skip to content

Validate Register outlet (dry-run)

POST
/v1/actions/hospitality.action.register_outlet/validate
curl --request POST \
--url https://api.aerandil.com/v1/actions/hospitality.action.register_outlet/validate \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{ "branch": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "params": { "code": "example", "kind": "rooms", "name": "example", "property_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "usali_department": "rooms", "usali_revenue_center_label": "example" }, "return_modified": false }'

Dry-run of apply_hospitality_action_register_outlet’s parameter checks. No side effects, no idempotency reservation, no handler dispatch — just the schema pass plus action-level shape (target presence, target type, unknown-parameter rejection). return_modified is meaningless here and ignored.

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
code
required
The outlet's code (trimmed; the tenant-unique business key)
string
kind
required
The outlet's operational kind
string
Allowed values: rooms restaurant bar lounge room_service banquet catering spa salon wellness_program gym pool golf parking minibar retail activity tour rental business_center laundry telecom package_aggregator other
name
required
The outlet's name
string
property_id
required
The property the outlet belongs to
string format: uuid
usali_department
required
The USALI department the outlet's revenue reports under
string
Allowed values: rooms food_beverage health_club_spa golf parking minibar other_operated minor_operated miscellaneous_income it_services retail
usali_revenue_center_label
The revenue-centre label a report groups the outlet under (the name when absent)
string
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

Validation outcome. result is valid or invalid; per-parameter diagnostics are always populated for every declared parameter so a UI can render the action’s full surface.

Media typeapplication/json
object
action
required
string
errors

Action-level errors not tied to a single parameter (missing target, target type mismatch, unknown parameter names). Absent when empty.

Array<string>
parameters
required

Per-parameter diagnostics keyed by api_name.

object
key
additional properties
object
errors
Array<string>
result
required
Allowed values: valid invalid
value
required

The serialised value the server interpreted, or null if the parameter was not supplied.

result
required
Allowed values: valid invalid
Example
{
"parameters": {
"additionalProperty": {
"result": "valid"
}
},
"result": "valid"
}