Obtain prices, product IDs, and all the information for products that are available at the origin point.
ImportantYou must call this endpoint before creating a Journey. The response provides the
product.id
that should be passed to the journey creation endpoint.For reserved journeys, pass the same
start_atused here to the journey creation request
to guarantee consistent product availability and pricing.We recommend estimating no more than 5 minutes before creating the journey.
Response
The response contains an array of available products, each with:
product.id— pass asproduct_idwhen creating a journey- Estimated price and currency
- ETA (estimated time of arrival)
- Vehicle category information
Hub Information
When the origin is within a large venue (airport, train station, etc.), each estimation object may include a hub field containing:
- Hub metadata (uid, title, location_id)
- A list of meeting points — designated pick-up locations with coordinates, images, and localized instructions
The hub field is resolved on a best-effort basis in parallel with pricing. It may be null if hub resolution does not complete in time or no hub exists at the origin.
Using Hub DataWhen a hub is present, present the meeting points to the user for selection and include the chosen one in the journey creation request via the
meeting_pointfield in the origin stop.
Alternatively, useGET /api/v4/hubto look up hub data independently.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
