# Introduction

The Highstar Travel API lets a travel agency, an OTA or an integrator sell four products from its own system: transfers, hotels, Universal Orlando tickets and Disney tickets. You search, quote, book and cancel over HTTPS. Every request and response is JSON, except for voucher PDFs.

All endpoints live under one base URL:

```text
https://highstartravel.com/api/v1
```

## Products

| Product | What you can do | Guide |
|---|---|---|
| Transfers | List the catalog, read a price and availability calendar, book, cancel, download the voucher | [Transfers](/developers/guides/transfers) |
| Hotels | Search availability, re-check a rate, book, cancel, read the booking and the hotel confirmation number, read hotel content | [Hotels](/developers/guides/hotels) |
| Universal | List the catalog, read prices per date, book, cancel, download the voucher | [Universal](/developers/guides/universal) |
| Disney | List the catalog by brand, read prices per date, book, cancel, download the voucher | [Disney](/developers/guides/disney) |

Your credential is enabled product by product. A call to a product your account does not have returns `403`.

## How a sale works

The four products differ in their fields, but the order of steps is the same:

1. Read the catalog or search, to get the identifier of what you want to sell.
2. Ask for the price on the date you need. Do this right before you confirm, because prices can change.
3. Confirm the booking. You send back the price you were shown, and the API rejects the request if the current price is different.
4. Keep the order identifier from the response. You need it to cancel and to download the voucher again.
5. Cancel if the customer cancels.

Two rules apply to every confirmation:

- Always send your own reference in `external_reference`. If a confirmation times out you can repeat it with the same reference and get the same order back. See [Conventions](/developers/guides/conventions#idempotency).
- Never repeat a confirmation with a new reference after a timeout. You could book twice.

## What is not available

- Webhooks. There is no push notification yet. Read the state of a booking by calling the API.
- A lookup of an order by your reference. Keep the order identifier that each confirmation returns.

## Reference and machine-readable files

The full list of fields, types and responses for each product is in the API reference:

- [Transfer reference](/developers/reference/v1/transfer)
- [Hotel reference](/developers/reference/v1/hotel)
- [Universal reference](/developers/reference/v1/universal)
- [Disney reference](/developers/reference/v1/disney)

The same contracts are available as OpenAPI files: [transfer](/developers/openapi/v1/transfer.json), [hotel](/developers/openapi/v1/hotel.json), [Universal](/developers/openapi/v1/universal.json) and [Disney](/developers/openapi/v1/disney.json).

If you use an AI assistant to write your integration, point it at [llms.txt](/developers/llms.txt). It lists every guide and spec. [llms-full.txt](/developers/llms-full.txt) has the text of all the guides in one file.

## Next

Start with the [Quickstart](/developers/guides/quickstart), then read [Authentication](/developers/guides/authentication) and [Conventions](/developers/guides/conventions). The [documentation home](/developers/) lists every guide.