Skip to content
aerandil.com
GitHub

Read Lost & found item

GET
/v1/object-types/hospitality.lost_found_item/objects/{id}
curl --request GET \
  --url https://api.aerandil.com/v1/object-types/hospitality.lost_found_item/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \
  --header 'Authorization: Bearer <token>'

Read an existing instance.

Something left behind and found at the house. found where it was found — a room (lost_found_item_in_room) or a named place (found_location) — and by whom (lost_found_item_found_by, the staff member behind the handset); stored with where it is kept; claimed once a guest asks for it (lost_found_item_claimed_by); returned to the person it went to (lost_found_item_returned_to, returned_at); or disposed — donated, destroyed, handed to the police or released to the finder — with when and why. returned and disposed are terminal. The description says what the thing is, never whose: the owner is a link. The id is the tag written on the bag.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
id
required
string format: uuid

Object id (UUID v7, server-generated at create time).

Query Parameters

Section titled “Query Parameters”
branch
string format: uuid

Read through an open branch’s copy-on-first-write overlay view instead of the canonical (main) plane. Does not compose with as_of (422). The branch must exist under the caller’s tenant.

Responses

Section titled “Responses”

200

Section titled “200”

Object found.

Media typeapplication/json
object
created_at
required
string format: date-time
id
required
string format: uuid
object_type
required
Allowed value: hospitality.lost_found_item
properties
required
object
category
What kind of thing it is (what a claim is matched on, and how it is kept)
string
Allowed values: clothing electronics jewellery documents keys money toiletries other
claimed_at
When a guest asked for it
string format: date-time
description
required
What it is — colour, make, distinguishing marks; not whose
string
disposal_method
Donated, destroyed, handed to the police, released to the finder, or other
string
Allowed values: donated destroyed handed_to_police released_to_finder other
disposal_reason
Why it was not kept any longer ("unclaimed past the 90-day hold")
string
disposed_at
When the house stopped keeping it
string format: date-time
found_at
required
When it was found
string format: date-time
found_location
Where it was found, when not in a room ("lobby bar", "pool deck")
string
id
required
Item tag (written on the bag)
string
returned_at
When it was handed back or sent
string format: date-time
status
required
Found, stored, claimed, returned or disposed
string
Allowed values: found stored claimed returned disposed
storage_location
Where it is kept ("HK office shelf 3", "front-office safe")
string
provenance

Per-property source attribution and pins. An entry under properties means the property’s current value came from that source (on the source’s own clock, source_updated_at); an entry under pins is a human override protecting the property from sourced writes.

object
pins
object
key
additional properties
object
pinned_at
string format: date-time
pinned_by
object
reason
required
string
properties
object
key
additional properties
object
external_id
string
recorded_at
required
string format: date-time
source
required
string
source_updated_at
string format: date-time
stream
string
scope
required
One of: discriminator: level
object
level
required
string
Allowed value: tenant
Allowed values: tenant
tenant_id
required
string format: uuid
updated_at
required
string format: date-time
version
required
integer
>= 1
Example
{
  "object_type": "hospitality.lost_found_item",
  "properties": {
    "category": "clothing",
    "disposal_method": "donated",
    "status": "found"
  },
  "scope": {
    "level": "tenant"
  }
}

Headers

Section titled “Headers”
ETag
string
/^"\d+"$/

Quoted strong validator (RFC 7232 §2.3) carrying the object’s monotonic version. Informational on the read path — object mutation goes through typed actions on /v1/actions/{action}/apply, not raw CRUD.

404

Section titled “404”

No object with that id (or soft-deleted).