---
title: "Wego API"
description: "What the Wego API is and how travelers and agents use it to search flights and hotels."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.wego.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Wego API

Wego is a travel company serving millions of travelers across the Middle East, Asia and beyond. This API exposes the building blocks wego.com itself runs on: resolve travel locations, search flights and hotels, compare fares and room rates, and continue on wego.com to book.

All `/v1` operations require an OAuth2 bearer token from the Wego auth server.

## Start here

- [Agent setup](/agent-setup): give your AI agent one line and it drives Wego.
- [Ways to use this API](/ways-to-use): the skill, the CLI, or direct HTTP.
- [Authentication](/authentication): get a token, two ways.
- [Quickstart](/quickstart): Dubai to London, end to end.
- [Wego CLI](/cli): the same funnels, one command per step.
- [API Reference](/api): every endpoint, request and response.

## The model

Both verticals follow the same funnel: create a search, read ranked results, open one result, then continue to wego.com. We return a URL where the traveler books; we never take a charge.

```text
flights: search -> results -> trip -> fare -> booking-link
hotels:  search -> results -> rooms -> booking-link
```

The [API Reference](/api) documents the machine contract in full: how async search settles, why ids expire, the fare and rate kinds, error codes, and rate limits.

Source: https://docs.wego.com/overview/index.mdx