trip

A directed journey from origin to destination — one direction of travel. A round-trip booking produces two trips (outbound + return). A single Uber ride is one trip. A connecting flight is one trip with multiple legs. Multi-stop Uber rides have multiple legs (one per waypoint pair).

Terminology alignment: Duffel/NDC “slice” = trip | “segment” = leg SerpAPI result = trip | flights[] element = leg Schema.org Trip > subTrip | Uber ride = trip (1+ legs) Train journey = trip | each train boarded = leg

Metadata	Value
Plural	`trips`
Subtitle field	`tripType`
Identity	`platform`, `id`

Fields

Field	Type
`tripType`	`string`
`status`	`string`
`departureTime`	`datetime`
`arrivalTime`	`datetime`
`duration`	`string`
`durationMinutes`	`integer`
`distance`	`string`
`vehicleType`	`string`
`cabinClass`	`string`
`fare`	`string`
`fareAmount`	`number`
`currency`	`string`
`rating`	`string`
`trackingUrl`	`url`
`isSurge`	`boolean`
`isScheduled`	`boolean`
`stops`	`integer`
`bookingToken`	`string`
`carbonEmissions`	`json`

Relations

Relation	Target
`origin`	`place`
`destination`	`place`
`legs`	`leg[]`
`carrier`	`organization`
`driver`	`person`
`order`	`order`

Prior art

External standards this shape draws from or aligns with. See Shape design principles for how prior art informs shape design.

schema.org/Trip + subTrip — Our origin/destination/departureTime/arrivalTime map exactly; legs[] ≈ subTrip or itinerary.
IATA NDC Slice (airline itineraries) — NDC slice = our trip; NDC segment = our leg. cabinClass, bookingToken come from NDC offer items.
Uber API — Trip resource — Practical source for ride trips. Our fare/fareAmount/ trackingUrl/isSurge/isScheduled lifted from Uber’s Trip model.

Skills that produce this shape

uber — list_trips, get_trip