Get trip candidates for a booking

Return the trips whose stages overlap this booking's place and date window, using the same matching rules as automatic trip assignment: a stage is the booking's place when one of its bookings lies within 60 km of the booking's coordinates, else when the city names match (case-insensitive); the date windows must overlap or be ≤24h apart. destination is the matched stage's location and is null for a stage that has no name yet.

Flow calls this in the post-confirmation flow. When length > 1 it shows a disambiguation picker and calls POST /v1/trips/{tripId}/bookings with the traveler's selection. When length ≤ 1 no picker is shown and the existing reconciler result stands.

Returns an empty list [] when no trips match — not 404. Returns 404 only when the booking ID is unknown or belongs to a different traveler. Travelers without a persisted profile receive an empty list without creating one.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required
Responses

404

Booking not found or not owned by the traveler

503

Database unavailable

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json