Plug your supplier API into Fusion Link and your jobs flow into every connected vendor's dispatch board. Status updates flow back to you in real time. When a vendor can't cover, the cross-vendor pool keeps your booking on the road.
Connect once via the adapter pattern. Your jobs appear inside every vendor dashboard you're connected to — and the pool becomes overflow capacity when a vendor's own roster can't cover.
Fusion Link reads jobs from your API and exposes them inside every connected vendor's dashboard. Koi Technologies live today; the adapter interface is built to plug in more.
Open and assigned jobs pull from your API on demand — 5-minute per-route trigger, 30-minute staleness threshold. No rate-limit storms.
When the receiving vendor can't cover, the job posts to Fusion Link's network-wide driver pool. Your booking still gets done; your vendor still keeps the relationship.
A working adapter ships with three contracts: jobs in, status out, drivers mapped. Everything else is configuration.
We poll your jobs endpoint per connected vendor + route + staleness rule. Mapped through a typed transformer to the Fusion Link Job shape.
As a driver progresses (assigned → in-progress → completed), we POST a status update back to your API. End customers see the same milestone the driver just hit.
Fusion Link drivers can be linked to your driver records, so a job dispatched here assigns the right driver ID in your system.
Pricing, assignment mode, currency, and driver mapping all map to your system per connection — without changing the source-of-truth in your database.
Driver progress flows to your API the moment it happens. Your end customer sees the same milestone the driver just hit.
Assignment-mode default, currency, pricing — all configured per supplier connection, not hard-coded.
Fusion Link drivers can be linked to your driver records, so a job dispatched in Fusion Link assigns the right driver ID in your system.
Bad fetchSource values or missing assignedTo on legacy supplier jobs get repaired in-place inside the status transition — no manual cleanup.
When a vendor edits a supplier-synced job, we record the diff. When a dispute lands, the photo + GPS + audit trail comes back as a ZIP — for both sides.
Vendor amendments on supplier-synced jobs are tracked with a full per-field before/after diff in the audit log — see exactly what was changed locally without touching your source record.
Photo + GPS + audit trail available per job as a ZIP. Dispute resolution between supplier ↔ vendor ↔ driver has hard evidence on every side.
Auto-issued at en_route and surfaced to the booking customer — your end customer doesn't have to ping the driver.
Plug into the network and you inherit its quality machinery — the discipline system, the plausibility checks on GPS, and the flight tracking that keeps airport jobs honest.
Fusion Link is multi-currency and multi-timezone by design. One supplier connection reaches operators in every country we serve.
Flight tracking, OTS+N stand-down timers, and airport-proximity surcharge rules in the storefront — built for the trip types most suppliers care about.
Every operator is part of the same driver pool. Your booking has more potential cover than any single fleet could provide.
Talk to our integrations team about adding your supplier API. We'll walk you through the adapter interface and the typed transformer we use to map your jobs.