All /v1 operations require an OAuth2 bearer token (see Authentication).
This reference is written to double as an agent tool contract: every operationId is a stable tool name, and every error is machine branchable.
Read these first
These rules govern every endpoint:
- How search works: searches are asynchronous; read results until they settle.
- IDs expire: every id is opaque and expires; a 404 means search again.
- Fares, rates and partners: which results are bookable on Wego.
- Conventions: query casing, default sort, entity reads.
- Errors: the RFC 9457 Problem envelope; branch on
code. - Rate limits: quota headers and
Retry-After.
Endpoints
- Places: resolve free text to typed travel locations, and find the airports near one.
- Countries: public holidays in a market, and where a passport travels without a visa.
- Flights: create a search, read ranked results, open a trip, read its per-leg experience signals, list fare options, get the booking link. Plus two reads that need no search: the published timetable for a route, and a durable wego.com search link.
- Hotels: create a search, read ranked results, open a hotel, read its guest reviews, list rates, get the checkout link. Plus a durable wego.com search link.
- User: the authenticated caller behind the bearer token.
- Feedback: send feedback about the Wego CLI and API.
Four of these need no search at all – holidays, visa-free destinations, flight schedules and nearby airports – so an agent can answer a reference question without starting a funnel.