Skip to content

Search Guest conversation

POST
/v1/object-types/hospitality.guest_conversation/search
curl --request POST \
--url https://api.aerandil.com/v1/object-types/hospitality.guest_conversation/search \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{ "branch": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "cursor": "example", "filters": [ { "property": "id", "type": "eq", "value": "example" } ], "limit": 1, "order": "asc", "property_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "scope": { "level": "tenant" }, "sort_by": "created_at" }'

Search for instances. Filters eq, contains, gte and lte AND-compose; or / not are additive follow-ups. Pages with an opaque cursor; the +1 fetch returns has_more without a second round-trip. Ordered by sort_by (default created_at) in order (default ascending), id breaking ties; rows with no value for a property key sort last.

Per-guest cross-channel conversation container. Two-level model per the 2026 vendor convergence: this object is the per-guest anchor; per-reservation segmentation is the optional anchor_reservation_ref plus the temporal guest_conversation_anchored_to_reservation link. Channel lives on guest_message, not here. Lifecycle state tracks the outermost outcome so operator UIs route on it; opt-out scope is the in-thread TCPA / WhatsApp / GDPR signal accumulator that the outbound-action validators honour.

Media typeapplication/json
object
branch

Optional open-branch id. Search composes that branch’s copy-on-first-write overlay instead of main, so a preview reads its own hypothetical writes. Omit to read main.

string format: uuid
cursor

Opaque cursor from a prior response’s next_cursor. Pass back verbatim; do not introspect.

string
filters

Conjunctive list of predicates. Empty or omitted matches every row in scope, capped by limit.

Array
One of:
object
property
required
Allowed value: id
type
required
Allowed value: eq
value
required
string
limit

Page size. Server defaults to 50, silently clamps at 500 (AIP-158 §3).

integer
>= 1 <= 500
order

Direction of sort_by: asc (oldest / smallest first) or desc. A cursor is bound to the sort_by and order it was minted under; another pair is refused (422).

string
default: asc
Allowed values: asc desc
property_id

The house a desk stands in: keeps this property’s rows (property- or venue-scoped there) and every row scoped to no property (tenant, brand, portfolio), and drops a sibling house’s — the meaning property_id has on the event tail.

string format: uuid
scope
One of: discriminator: level
object
level
required
string
Allowed value: tenant
Allowed values: tenant
sort_by

What the page is ordered by: the row’s created_at or updated_at, or a property whose type orders — strings, enums and dates as text, ints, decimals and durations as numbers, datetimes as instants. Rows with no value sort last in either direction. A property the caller is not cleared to read is refused (403).

string
default: created_at
Allowed values: created_at updated_at id opened_at last_message_at last_message_at_computed_at state state_reason language message_count inbound_count triage_count escalation_count message_count_computed_at

Search results, ordered by (sort_by, id) in the requested order (ascending by default).

Media typeapplication/json
object
data
required
Array<object>
object
created_at
required
string format: date-time
id
required
string format: uuid
object_type
required
Allowed value: hospitality.guest_conversation
properties
required
object
anchor_reservation_ref
Optional reservation anchor (pre-arrival / in-house / departing)
string format: uuid
escalation_count
Count of triages that escalated (denormalised; §B.1)
integer
id
required
Conversation id
string
inbound_count
Count of inbound messages (denormalised; §B.1)
integer
language
BCP-47 tag of the guest's most recently detected reply language
string
last_message_at
required
Most recent message timestamp (denormalised, §B.1)
string format: date-time
last_message_at_computed_at
Refresh-discipline pair for `last_message_at`
string format: date-time
message_count
Count of messages in this conversation (denormalised; §B.1)
integer
message_count_computed_at
Refresh pair for the four counters (§B.1 discipline)
string format: date-time
opened_at
required
When the conversation opened (first message timestamp)
string format: date-time
opt_out_scope
required
Opt-out signals received in-thread (TCPA / WhatsApp / GDPR)
Array<string>
Allowed values: sms_marketing sms_all whatsapp_marketing email_marketing voice_all gdpr_erasure_requested
person_ref
The guest (person) this conversation belongs to
string format: uuid
redactions_applied
required
Aggregated redaction-kind set across the conversation
Array<string>
Allowed values: pan cvv government_id health_disclosure child_safeguarding other_pii
sentiment_trajectory
Rolling sentiment scores [-1.0, 1.0] per message (bounded length)
Array<string>
state
required
Lifecycle state
string
Allowed values: open awaiting_guest awaiting_staff closed_resolved closed_unresolved escalated
state_reason
Optional short reason on terminal state transitions
string
triage_count
Count of triages issued in this conversation (denormalised; §B.1)
integer
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
has_more
required
boolean
next_cursor

Cursor for the next page; omitted when the result set is exhausted.

string
Example
{
"data": [
{
"object_type": "hospitality.guest_conversation",
"properties": {
"opt_out_scope": [
"sms_marketing"
],
"redactions_applied": [
"pan"
],
"state": "open"
},
"scope": {
"level": "tenant"
}
}
]
}

Validation error — unknown property or filter type mismatch.