iCabbi integration.
Two-way booking, customer and job-status sync between Limozoft and your existing iCabbi tenant.
- Booking create, amend and cancel via iCabbi REST API
- Live job status webhooks — allocated, POB, completed, no-show
- Passenger and account-client record sync
- Saved address and rate-card mapping
- Driver and vehicle roster sync
- Historical trip export for invoicing and reporting
- Parallel-run mode for staged migration
What the connector covers
Limozoft speaks to iCabbi over its documented REST API plus outbound webhooks. Bookings taken on your Limozoft site, passenger app or WhatsApp bot are created directly in iCabbi with the correct vehicle class, rate card and account reference. Status events flow back in real time so the passenger sees the same tracking whichever system dispatched the job.
Corporate account work is the most common reason operators keep both. Limozoft handles the account portal, booker permissions, cost centres, PO references and consolidated invoicing; iCabbi keeps allocating cars.
Pricing and contract notes
The connector is included in your Limozoft subscription — flat per-vehicle monthly, no per-booking fee for API traffic on our side. See pricing for current UK figures.
On the iCabbi side, pricing is quoted per fleet and typically billed per active driver. API access is not always enabled by default and some agreements meter it. Before you plan an integration, confirm three things in writing: whether API access is included at your tier, whether call volume is capped or charged, and your notice period and renewal date if a full migration is on the table.
If you are weighing replacement rather than integration, the honest comparison is on our iCabbi alternative page.
Setup timeline
Day 1: credentials issued and sandbox connected. Day 2: rate cards, vehicle classes and account clients mapped. Day 3: test bookings end to end, including cancellations and no-shows. Day 4–5: parallel run with live work. Most fleets are fully cut over inside a working week.
Frequently asked questions
Does Limozoft integrate with iCabbi?+
Yes. We connect to iCabbi through its REST API and webhooks to push and pull bookings, customer records, account clients, driver and vehicle data, and job status events. Typical use cases are running Limozoft as the customer-facing booking and account layer while iCabbi keeps dispatching, or migrating off iCabbi in stages.
What data can be synced with iCabbi?+
Bookings (create, amend, cancel), quotes and fares, passenger and account-client records, saved addresses, driver and vehicle lists, live job status and completion events, and historical trip data for reporting and invoicing.
Do I need anything from iCabbi to enable the integration?+
You need API credentials for your iCabbi tenant and, in most cases, written confirmation from your account manager that API access is included in your plan. Some operators are charged separately for API volume — check before you switch it on.
Does the iCabbi integration cost extra with Limozoft?+
No. API connectors are included in the standard Limozoft per-vehicle monthly price. If iCabbi bills you for API calls on their side, that cost stays with them.
Can I run iCabbi and Limozoft in parallel during a migration?+
Yes, and we recommend it. A typical cutover runs both systems side by side for five to seven days, with bookings mirrored across, so dispatchers keep a familiar screen while the new flow is proven.