Skip to content
aerandil.com
GitHub

Validate Update service philosophy (dry-run)

POST
/v1/actions/hospitality.action.update_service_philosophy/validate
curl --request POST \
  --url https://api.aerandil.com/v1/actions/hospitality.action.update_service_philosophy/validate \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "branch": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "params": { "address_form_default": "mr_ms", "anticipatory_responsive": "extremely_anticipatory", "audit_target": "forbes", "empowered_scripted": "fully_empowered", "ex_cx_priority": "employees_first", "hospitality_service_emphasis": "hospitality_first", "personality_presentation": "muted", "philosophy_statement_text": "example", "privacy_visibility_default": "extremely_private_invisible_attention", "recognition_depth": "minimal", "recovery_culture_intent": "example", "surface_register_default": "formal_warm" }, "return_modified": false, "target": { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "object_type": "hospitality.property" } }'

Dry-run of apply_hospitality_action_update_service_philosophy’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.

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
address_form_default
required
Address form default
string
Allowed values: mr_ms first_name no_name
anticipatory_responsive
required
Anticipatory ↔ responsive
string
Allowed values: extremely_anticipatory anticipatory balanced responsive purely_responsive
audit_target
required
Audit target
string
Allowed values: forbes aaa_diamond lqa internal_only none
empowered_scripted
required
Empowered ↔ scripted
string
Allowed values: fully_empowered empowered_with_guidance balanced mostly_scripted fully_scripted
ex_cx_priority
required
EX → CX priority
string
Allowed values: employees_first employees_above_guests employees_equal_guests guests_first investors_first
hospitality_service_emphasis
required
Hospitality ↔ service emphasis
string
Allowed values: hospitality_first balanced_warm professional_warmth service_efficient transactional
personality_presentation
required
Personality presentation
string
Allowed values: muted forward as_product
philosophy_statement_text
required
Narrative statement
string
privacy_visibility_default
required
Privacy ↔ visibility default
string
Allowed values: extremely_private_invisible_attention private balanced visible_attention extremely_visible
recognition_depth
required
Recognition depth
string
Allowed values: minimal name_recognition preference_recognition relationship_recognition deep_recognition
recovery_culture_intent
Recovery culture intent (self-declared)
string
surface_register_default
required
Surface register default
string
Allowed values: formal_warm crafted_theatre quick_warm discreet_professional focused_coaching other
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.property

Responses

Section titled “Responses”

200

Section titled “200”

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"
}