Skip to content
aerandil.com
GitHub

Validate Start workflow run (dry-run)

POST
/v1/actions/hospitality.action.start_workflow_run/validate
curl --request POST \
  --url https://api.aerandil.com/v1/actions/hospitality.action.start_workflow_run/validate \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "branch": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "params": { "expires_at": "2026-04-15T12:00:00Z", "initiating_agent_installation_id": "example", "input": "example", "run_key": "example", "target_refs": "example", "trigger_kind": "manual" }, "return_modified": false, "target": { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "object_type": "hospitality.workflow_definition" } }'

Dry-run of apply_hospitality_action_start_workflow_run’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
expires_at
Run timeout
string format: date-time
initiating_agent_installation_id
Set when an installed agent initiated the run
string
input
required
Frozen, redacted start input
run_key
required
Host-supplied business / dedupe key
string
target_refs
Optional `[{object_type, object_id}, ...]` for graph wiring
trigger_kind
Defaults from the definition
string
Allowed values: manual event schedule webhook agent_requested api
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.workflow_definition

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