Skip to main content
GET
List trip history
The first entry is the booking being recorded. Each following one is a change, with how it was learned: API when a read or an action of yours found it, WEBHOOK when the travel provider reported it, POLL when a periodic check did. The trip is brought up to date with the provider before the answer, so a change the provider already made shows up as a fresh entry. Empty while the trip is still being created. Visible to an organization admin and to the users the trip carries, like the trip itself.

Path Parameters

realmId
string<uuid>
required

ID of your realm.

Format: UUID

organizationId
string<uuid>
required

ID of the organization the trip belongs to.

Format: UUID

tripId
string
required

ID of the trip (24 hexadecimal characters).

Pattern: ^[0-9a-fA-F]{24}$

Response

Successful response

The history of a trip.

items
object[]
required

Changes in chronological order, the oldest first.