Connect
Your booking system creates orders directly.
An API is a promise: what you send arrives, and what you ask is answered. Here it says honestly what it can do today and what will follow.
The problem
- A hotel or a booking site sends trips by email. Somebody types them in.
- Two systems, two truths about the same order.
- You want to query the state of an order without calling.
How it works
- 01
Key per partner
Every partner gets their own key. Only a hash is stored; no app user can read keys.
- 02
Create an order
One call with pickup, destination, time and the partner's reference. The same reference sent twice returns the same order, not two. With the test flag the order reaches no driver.
- 03
Query the state
One call returns state, counters, places and price of the order. Dispatch to the driver runs as with a call.
What it does not do
- Cancellations, price information and cancellation deadlines via the API will follow.
- Signed webhooks with retries are planned; today the partner queries the state.
- Keys are set up by us today, management in the interface will follow.
Questions
Who is the API for?
For hotels, booking platforms, dispatch systems and accounting that want to create or query orders.
Is there documentation?
Yes, you get it with the key. Two calls: create order, query order.
Can I query trips and positions?
Orders today. Trips and positions are on the list, talk to us.
Let us show you on your own cars.
Half an hour, no obligation. You see the app with real data and get a quote for your fleet.