Skip to content

Validate F&B outlet menu (dry-run)

POST
/v1/functions/hospitality.function.fnb_outlet_menu/validate
curl --request POST \
--url https://api.aerandil.com/v1/functions/hospitality.function.fnb_outlet_menu/validate \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{ "params": { "daypart": "breakfast", "order_kind": "dine_in" }, "target": { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "object_type": "hospitality.outlet" } }'

Dry-run of invoke_hospitality_function_fnb_outlet_menu’s parameter checks. No handler dispatch, no store reads — just parameter shape, target presence, target type, unknown-parameter rejection.

Media typeapplication/json
object
params
required
object
daypart
Meal period the menus and prices are for (absent = every active menu)
string
Allowed values: breakfast brunch lunch dinner late_night drinks dessert room_service all_day
order_kind
Order kind the prices are for (absent = rows naming no order kind)
string
Allowed values: dine_in takeaway room_service delivery
target
required
object
id
required
string format: uuid
object_type
required
Allowed value: hospitality.outlet

Validation outcome. result is valid or invalid; per-parameter diagnostics are always populated for every declared parameter.

Media typeapplication/json
object
errors

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

Array<string>
function
required
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"
}