Assemble dispute evidence

POST

/v1/actions/hospitality.action.assemble_dispute_evidence/apply

curl --request POST \
  --url https://api.aerandil.com/v1/actions/hospitality.action.assemble_dispute_evidence/apply \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "branch": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "params": {}, "return_modified": false, "target": { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "object_type": "hospitality.payment_dispute" } }'

• Production API

Build the evidence packet for a chargeback that is awaiting evidence, from what the kernel already holds: the folio, the cancellation terms frozen at booking, the stay record, the guest, and the payment’s 3DS outcome. Picks the argument from the dispute’s reason and what happened to the booking (fraud, no_show, cancellation, duplicate, service), and records every document against the source object’s id and version, plus the evidence it wanted and could not find. Never submits. A case can be submitted once and countering costs a fee, so that decision stays with a person; this writes a draft. (Move 13, 2026-10-22: a draft with no gaps still unsent 48 hours before the deadline is submitted by the night audit’s sweep, as system.) Re-running it supersedes the unsent packet and bumps packet_version — the way to pick up a late folio correction. Refuses: a dispute not awaiting evidence (needs_response or inquiry_needs_response), a deadline already past, and a case whose evidence has already gone to the issuer.

Effects: create hospitality.dispute_evidence_packet; modify hospitality.dispute_evidence_packet; link hospitality.link.evidence_packet_for_dispute.

Authorizations

• aerandil_oauth
  actions:apply
• aerandil_oauth
  actions:hospitality.action.assemble_dispute_evidence:apply

Request Body^required

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

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

Responses

200

Action applied. modified_objects and modified_links populated when return_modified: true was supplied.

Media typeapplication/json

ApplyActionResponse

Envelope returned by the Aerandil action engine. correlation_id ties every event emitted by this invocation; modified_objects and modified_links project the events the handler emitted (per the action’s declared effects); warnings carries any non-blocking soft-validator observations.

object

correlation_id

required

Per-invocation correlation id; matches events.correlation_id for every event this action appended.

string format: uuid

modified_links

required

Links established or removed by this invocation. Empty when the caller did not request return_modified.

Array<object>

object

from_id

required

string format: uuid

from_type

required

string

kind

required

Allowed values: linked

link_type

required

Allowed values: hospitality.link.evidence_packet_for_dispute

to_id

required

string format: uuid

to_type

required

string

modified_objects

required

Objects created, modified, or soft-deleted by this invocation. Empty when the caller did not request return_modified.

Array<object>

object

id

required

string format: uuid

kind

required

Allowed values: created modified

object_type

required

Allowed values: hospitality.dispute_evidence_packet

warnings

Non-blocking soft-validator observations emitted during this invocation (e.g. comp-authority over-limit, recipe pour-cost over sell-price). Absent when no warnings were emitted.

Array<object>

object

message

required

Human-readable summary, suitable for logging or operator-UI surfacing.

string

object_type

required

Object type the warning was raised against.

string

property

Property the warning anchors to, when a single field is the locus. Absent for multi-field rules.

string

rule

required

Stable kebab-case rule identifier (e.g. comp-authority-over-limit).

string

Example

{
  "modified_links": [
    {
      "kind": "linked",
      "link_type": "hospitality.link.evidence_packet_for_dispute"
    }
  ],
  "modified_objects": [
    {
      "kind": "created",
      "object_type": "hospitality.dispute_evidence_packet"
    }
  ]
}

409

Conflict — concurrent modification or unique constraint violation.

422

Validation error — parameter validation or business-rule violation.