For online travel agencies
Airport transfers, one API call away.
An OTA is an agency account with API keys. Quote, book and follow status from your systems; the traveller pays by card, or in cash in the vehicle where we offer it, and you earn the commission set on your account.
{ "airport": { "code": "IST", "side": "from" }, "origin": { "slug": "…" }, "destination": { "query": "…" }, "pickup": { "date": "YYYY-MM-DD", "time": "HH:MM" }, "passengers": { "count": 2, "bags": 2 }, "flightNo": "…", "trip": "one_way"}
{ "id": "…", "currency": "EUR", "expiresAt": "…", "offers": [ { "snapshotId": "…", "vehicle": { "class": "…" }, "pricing": { "totalPriceCents": … } } ]}
What the API gives you
The calls your product needs.
Every line below works today; none of it is on a roadmap.
- 01
Quote, book, follow
Create a quote, book one of its offers, read the booking and cancel it: the four operations a checkout needs, described as OpenAPI 3.1 at /developers.
Served live from /api/v1/openapi.json.
- 02
Keys scoped to what you do
We issue keys for your account, each limited to the scopes your integration uses, such as quotes, bookings, cancellation and webhooks, under a request quota set for your client.
One environment; a key works against this deployment only.
- 03
Safe to retry
Booking and webhook creation require an Idempotency-Key. Replaying the same key with the same body returns the original response; the same key with a different body is refused.
A timeout never books twice.
- 04
Status pushed to you
Subscribe an HTTPS endpoint to quote created, booking created, booking cancelled, booking completed and pickup amended. You manage subscriptions, signing secrets, test deliveries and replays in your portal.
Deliveries and their attempts are listed in the portal.
- 05
Commission on one account
The API client belongs to your agency account and earns it the commission set there. What you sell through the API and what you book in the portal count towards the same commission.
Commission fixed per booking; shown in your portal.
Where the boundary is
Where the API stops.
- Payment through the API
- A caller selects the traveller's card online, where the booking waits for a card checkout, or cash paid to the driver in the vehicle, which needs its own scope and is accepted only while we offer cash. Nothing is charged to your account.
- Environments
- One. A key is issued for this deployment and there is no separate test environment; tell us before you run test bookings.
- Inventory
- Airport routes, with an airport at one end of every transfer. Prices come per route and vehicle class, as the quote returns them.
- Limits
- Each endpoint has a per-minute limit and each client a daily and monthly quota, counted in UTC. A request over a limit is refused with a Retry-After header.
- What you need
- Company registration, the licence or registry number the form asks for, and a developer who can consume a JSON API and receive webhooks over HTTPS. We do not state a review time.
- Not offered
- An embeddable booking widget, your own domain, your own colours or selling on credit. No account books on credit, through the API or the portal.
How to go live
From application to first live booking.
- 01
Apply
Apply as an OTA. A person reviews the company and its documents and opens your agency account.
- 02
Get your keys
We issue keys for your account with the scopes you need; read the reference at /developers meanwhile.
- 03
Integrate
Build quote, book and status into your product, and subscribe webhooks if you want status pushed to you.
- 04
Go live
The same keys serve your first live booking; there is no second environment to switch to.
Questions
Before you integrate.
Is there a test environment?
No. There is one environment, and a key issued for it works nowhere else. Tell us before you run test bookings so they are handled as such.
What happens on a duplicate request?
Booking and webhook creation carry an Idempotency-Key. The same key with the same body returns the original response, marked as replayed; the same key with a different body is refused.
Which payment methods can the API select?
The traveller's card online, where the booking waits for a card checkout, or cash in the vehicle, which needs the extra bookings:cash scope and is refused while cash payment is switched off. Neither is charged to your account.
How is my commission paid?
At the rate set on your account, fixed when each booking is made. It is earned when the transfer is completed; you invoice us from the portal and ClickToGoo pays that invoice. The portal shows what is earned and not yet paid out, API bookings included.
Where is the full reference?
At /developers, with the OpenAPI 3.1 document served live from /api/v1/openapi.json.
Read the reference, then apply.
The reference is public. Apply once you know which calls your product needs; one of our team reviews it and opens your account.