> ## Documentation Index
> Fetch the complete documentation index at: https://developers.ttool.travel/llms.txt
> Use this file to discover all available pages before exploring further.

# Testing with Postman

> Run the whole flow end to end against staging.

The collection covers the full flow and authenticates itself. Ask your account manager for these files:

* `Hub-Flight-API.postman_collection.json`
* `Hub-Flight-API.staging.postman_environment.json`
* `Hub-Flight-API.production.postman_environment.json`

**1. Import**

Import the collection and the staging environment, then select the environment.

**2. Configure**

Set `username` and `password`. Check that `baseUrl` is `https://api.staging.ttool.travel/hub`.

**3. Search**

Send **Search – one way** or **Search – round trip**. The collection fetches a token, stores it, and puts the first offer's `offerId` into `offerId`. It also detects split round trips and sets `bookMode`.

**4. Offer calls**

Send **Flight details**, **Fare brands** and **Change options** in order. Any that don't apply to the selected offer skip themselves and explain why in the console.

**5. Create order**

Fill the `pax*` and `contact*` variables and send **Create order**. The `orderId` is stored. Nothing is booked yet.

**6. Issue**

Send **Issue** to book the seats and ticket. This charges the staging wallet, so send it deliberately.

For the hold flow, send **Create order – on hold** instead of **Create order**, then **Order status** (shows `hold.expiresAt`), then either **Issue** or **Cancel hold**.

You can also run the whole collection in the Collection Runner as an end-to-end regression check. Its tests assert status codes, the error envelope and the correlation-id echo.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.