VTO API
v1 · operational API Reference →
VTO API · est. 2000

One endpoint to every corner of your travel data.

A clean, mostly read-only REST API over 25 years of VTO data — branches, clients, consultants, groups, trips and reports. Send one token, read predictable JSON.

Open the API Reference → See a request
6
Resources
16
Endpoints
25 yrs
Of data
KEY · read before plotting

The legend: four rules behind every request.

Learn these symbols once and the whole API behaves the way you'd expect.

Symbol 01

One token, by office

Send an X-Api-Token header on every request. Each token is scoped to one office's data.

Symbol 02

Fair use limits

5 req/sec burst and 200/day per token. Cross the line, get a clean 429.

Symbol 03

Predictable JSON

Every response carries success and a timestamp. Lists add a pagination block.

Symbol 04

Mostly read-only

Browse with GET. A few client sub-resources take POST with clients.write; other verbs return 405.

INDEX · six destinations

Every resource, with a list and a by-ID endpoint.

The full gazetteer. Each entry links through to its schema in the reference.

01 Branches Office branches, filterable by country, state and tax code. GET/v1/branches 02 Clients Individual & corporate clients with full contact details. GET/v1/clients 03 Consultants Travel consultants by branch and active status. GET/v1/consultants 04 Groups Client groups with optional nested trip summaries. GET/v1/groups 05 Trips Trips with sectors, financials and air/aux itineraries. GET/v1/trips 06 Reports Run predefined SQL reports with flexible filters. GET/v1/reports/list
PLOT · the first call

One header. One request. Clean data.

No SDK, no handshake. Add your token, hit a resource, read the JSON. Here's a list of clients, start to finish.

  • AUTHYour office token in the X-Api-Token header.
  • SHAPEdata holds records; pagination tracks the rest.
  • NEXTSwap /clients for any resource in the index.
~ vto-api · curl 
$ curl https://api.vto.cloud/v1/clients \
    -H "X-Api-Token: ••••••••••••"

{
  "success": true,
  "data": [
    {
      "id": 4821,
      "first_name": "Poh",
      "last_name": "Tan",
      "is_corporate": false
    }
  ],
  "pagination": { "total": 137, "page": 1 }
}
Access on request

Chart your route on VTO.

Talk to your VTO account manager and we'll issue a token scoped to your office — usually the same day.

Request a token → Read the docs first No public sign-up · invitation only