This article outlines the current partners integrated with the iGo / Cab Exchange platform. It also explains the types of aggregator accounts, how to connect with them, and what to expect regarding payment handling, pricing, and booking configuration.
Overview.
The iGo platform connects your dispatch system with a range of third-party aggregators. These are split into two types based on how payment is processed:
- iGo Wallet Aggregators: Payment is handled automatically through your iGo Wallet.
- Invoiced (Cab Exchange) Aggregators: Payment is handled via direct invoicing between you and the aggregator.
Auto-Connected Aggregators.
The following aggregators are automatically connected when youβre added to the iGo marketplace. You do not need to contact them to receive work:
- Jyrney
- GETT (iGo Wallet version)
You may start receiving jobs from these aggregators immediately. Their accounts will appear in your system as:
iGo AggregatorName β AgentID (e.g. iGo Jyrney β 20094)
Aggregators Requiring Manual Connection.
For all other aggregators, you must initiate contact and provide your Vendor ID to arrange the connection from their end. This includes signing any required contracts or agreements.
iGo Wallet Aggregators (Payments via iGo Wallet)
Aggregator | Contact | Agent Set Price | Waiting Time + Extras | Agent ID |
Addison Lee | Duane Gangadeen - Network Manager π§ Duane.gangadeen@addisonlee.com |
20001 | ||
Abellio | Steve Hobbs - Operator Account Manager π§ steve.hobbs@abellio.com |
20093 | ||
Jyrney | Danielle Lewis - Supplier Success Manager π§ danielle.lewis@jyrney.com |
20094 | ||
GETT | Michael Smith - Partner Relationship Manager π§ michael.smith@gett.com |
β | β | 20050 |
I-GTM | Andrew Steven - Director π§ as@i-gtm.com |
20110 | ||
Arriva | π§ ukbusapssc@arriva.co.uk, smithle@arriva.co.uk | β | 20111 | |
GroundScope | Rose Smith π§ servicepartners@groundscope.co.uk |
20114 |
Invoiced Aggregators (Cab Exchange Accounts)
These aggregators do not pay into the iGo wallet. Instead, you must invoice them directly per their terms. Their accounts will be labelled as:
AggregatorName CABX β AgentID (e.g. Minicabit CABX β 20037)
Aggregator | Contact | Agent Set Price | Waiting Time + Extras | Agent ID |
CMAC | π Apply Here | β | β | 20027 |
First Rail | Chris Lee β Networking π§ Chris.j.lee@firsttravelsolutions.com |
β | 20008 | |
Minicabit | π§ info@minicabit.com | β | 20037 | |
Cabubble | Bernard Poon β Business Development Manager π§ bernard.poon@cabubble.co.uk |
β | 20015 | |
GETT (CABX) | Michael Smith - Partner Relationship Manager π§ michael.smith@gett.com |
β | β | 20070 |
Key Definitions.
- Agent Set Price: Aggregator sends a fixed price with the booking. This is required for the integration to function correctly.
- Waiting Time & Extras: If supported, this enables recalculations for delays or added costs during the trip. Otherwise, you must invoice separately.
- Agent ID: This is how the system maps bookings to aggregator accounts. You can find it in your account configuration under General > Agent ID.
Important Notes.
- Jyrney and GETT are the only aggregators that can dispatch jobs without needing to network your vendor ID manually. All other aggregators must be contacted directly.
- Invoiced Accounts require you to negotiate pricing, waiting time, and extras directly with the aggregator.
Useful Aggregator Resources.