Conventions

One verb

Almost every endpoint is a POST with a JSON body (Content-Type: application/json). A few lookups use GET.

Response envelope

Every response is JSON with a status field:

{ "status": "success", "reason": "…", "data": { } }

| Field | Meaning | |---|---| | status | success or failed. | | reason | A readable message. Flight search uses message instead. | | data | The result. The key differs on some endpoints, for example transfer_data on transfer search. | | tracking_id | Identifies a search. Send it back when you price or book from that search. |

Paths

Paths are unversioned and use mixed naming (/flight/search, /tour-activity/search, /tour_package/search). The docs show each path exactly as the server accepts it. Copy the path from the endpoint page rather than guessing from a pattern.

Searches and tracking

Search endpoints can take a while because they ask several suppliers. Send a unique short_ref if you want to follow progress in the search logs.