Autocab integration.
Keep Autocab dispatching. Put a modern booking, WhatsApp and corporate-account layer in front of it.
- Booking create, amend and cancel through the Autocab API
- Live status callbacks — allocated, en route, POB, completed
- Account client, cost centre and PO reference mapping
- Rate-card and vehicle-class alignment across both systems
- Network (Ghost / iGo) work left untouched
- Full historical import from Autocab CSV exports
- Parallel-run mode if you later move dispatch across
What the connector covers
Every booking channel we provide — website booking engine, branded passenger app, WhatsApp bot, phone-agent screen and corporate portal — writes into Autocab with the right vehicle class, rate and account reference. Status callbacks come back to Limozoft in real time, so tracking links, driver-assigned notifications and WhatsApp confirmations all reflect what Autocab is actually doing.
Invoicing can run on either side. Most operators let Limozoft consolidate account invoicing because cost centres, PO references and per-client rate cards are richer here.
Pricing and contract notes
From Limozoft: the connector is included in the flat per-vehicle monthly price, no per-trip clip. UK figures are on the pricing page.
From Autocab: pricing is quote-only, typically a per-vehicle monthly licence with onboarding, hardware and support, on a fixed-term agreement. Two things to confirm before you plan work — whether API access is included at your tier, and your notice period and renewal date. Fixed terms are the single most common reason a migration slips.
Considering replacement instead? The straight comparison is on our Autocab alternative page.
Setup timeline
Day 1: API credentials and sandbox. Day 2: rate cards, vehicle classes and account clients mapped. Day 3: end-to-end test bookings including amendments and cancellations. Day 4–5: live parallel run. Typically complete within five working days.
Frequently asked questions
Does Limozoft integrate with Autocab?+
Yes. We connect to Autocab through its booking API and status callbacks so jobs created in Limozoft — website, passenger app, WhatsApp or corporate account portal — are dispatched by your existing Autocab system, with live status flowing back to the passenger.
Will the integration affect my Ghost / iGo network work?+
No. Network jobs continue to be handled by Autocab exactly as they are today. Limozoft sits in front as a booking and account layer; it does not intercept inbound network work.
What do I need from Autocab to enable it?+
API credentials for your operator account and confirmation that API access is enabled under your agreement. Autocab quotes per fleet, so check whether API usage carries an additional line item.
Can Limozoft import my Autocab history?+
Yes. Request a CSV export of customers, accounts, saved addresses, rate cards and booking history. We map and import all of it, so nothing is retyped — this also applies if you later move dispatch across entirely.
Is there a per-booking fee for the Autocab connector?+
Not from us. The connector is included in the flat per-vehicle Limozoft subscription. Any per-booking or licence charges on your Autocab agreement are unaffected.