Skip to content
aerandil.com
GitHub

Record lost & found item

POST
/v1/actions/hospitality.action.record_lost_found_item/apply
curl --request POST \
  --url https://api.aerandil.com/v1/actions/hospitality.action.record_lost_found_item/apply \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "branch": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "params": { "category": "clothing", "description": "example", "found_at": "2026-04-15T12:00:00Z", "found_location": "example", "item_id": "example", "room_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "storage_location": "example" }, "return_modified": false, "target": { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "object_type": "hospitality.property" } }'

Record something found at the target property: what it is (never whose), where — room_id for a room of this property, or found_location for anywhere else — and when (found_at, defaulting to now). The staff member behind the principal (the handset’s attendant or runner) is linked as the finder. The item is found, or stored at once when storage_location is given (the desk putting a handed-in phone straight in the safe). Its tag is the id: LF- and the last eight hex digits of the item’s object id, upper-case. A caller may mint that object id itself (item_id, a v4 or v7 UUID) — a handset recording offline then knows the item, and the tag for the bag, before the record lands, and can hang the photo off it once it has; the same find under the same item_id again is a no-op, a different one is refused as a duplicate. Emits lost_found_item.recorded.

Effects: create hospitality.lost_found_item; link hospitality.link.lost_found_item_in_room; link hospitality.link.lost_found_item_found_by.

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
category
What kind of thing it is
string
Allowed values: clothing electronics jewellery documents keys money toiletries other
description
required
What it is — colour, make, distinguishing marks; not whose
string
found_at
When it was found (defaults to now)
string format: date-time
found_location
Where it was found, when not in a room
string
item_id
The item's object id, when the caller mints it (a v4 or v7 UUID) — replay-safe: the same find again is a no-op
string
room_id
The room it was found in
string format: uuid
storage_location
Where it is kept, when it is put away at once
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
target
required
object
id
required
string format: uuid
object_type
required
Allowed value: hospitality.property

Responses

Section titled “Responses”

200

Section titled “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.lost_found_item_in_room hospitality.link.lost_found_item_found_by
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
object_type
required
Allowed values: hospitality.lost_found_item
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.lost_found_item_in_room"
    }
  ],
  "modified_objects": [
    {
      "kind": "created",
      "object_type": "hospitality.lost_found_item"
    }
  ]
}

409

Section titled “409”

Conflict — concurrent modification or unique constraint violation.

422

Section titled “422”

Validation error — parameter validation or business-rule violation.