Skip to main content
For Suppliers

Your booking API, every vendor's fulfilment lane.

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.

Distribution + fulfilment

Reach the whole driver network through one adapter.

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.

  • Adapter pattern

    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.

  • Lazy sync, not mass polling

    Open and assigned jobs pull from your API on demand — 5-minute per-route trigger, 30-minute staleness threshold. No rate-limit storms.

  • Cross-vendor pool exposure

    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.

How it works

Three integration touchpoints.

A working adapter ships with three contracts: jobs in, status out, drivers mapped. Everything else is configuration.

  1. Step 01

    Jobs in

    We poll your jobs endpoint per connected vendor + route + staleness rule. Mapped through a typed transformer to the Fusion Link Job shape.

  2. Step 02

    Status out

    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.

  3. Step 03

    Drivers mapped

    Fusion Link drivers can be linked to your driver records, so a job dispatched here assigns the right driver ID in your system.

Two-way trust

Configured per supplier connection.

Pricing, assignment mode, currency, and driver mapping all map to your system per connection — without changing the source-of-truth in your database.

  • Status updates flow back

    Driver progress flows to your API the moment it happens. Your end customer sees the same milestone the driver just hit.

  • Per-supplier config

    Assignment-mode default, currency, pricing — all configured per supplier connection, not hard-coded.

  • Driver mirror

    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.

  • Self-healing sync

    Bad fetchSource values or missing assignedTo on legacy supplier jobs get repaired in-place inside the status transition — no manual cleanup.

Amendments & disputes

An evidence trail your support team can actually use.

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.

  • Per-field diff log

    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.

  • Evidence ZIP

    Photo + GPS + audit trail available per job as a ZIP. Dispute resolution between supplier ↔ vendor ↔ driver has hard evidence on every side.

  • Tracking link

    Auto-issued at en_route and surfaced to the booking customer — your end customer doesn't have to ping the driver.

Quality network effect

The drivers who fulfil your jobs are vetted by the network.

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.

Discipline cards

  • Yellow / red card system for pool-quality enforcement
  • Yellows expire after 6 clean months
  • Three active yellows auto-escalate to red
  • Banned drivers don't appear in your vendor's pool feed

Plausibility-flagged GPS

  • Server-side checks for impossible speeds, clock drift, low accuracy
  • Flagged events never silently dropped — full audit trail kept
  • Trust score is real, not lifted from device-side telemetry alone
  • Vendors see snapped-to-road trails, dispute analysis still has the raw flags

Flight tracking

  • Dual provider (FlightRadar24 + AeroDataBox Ultra)
  • EWMA percentile stats on delay distributions
  • Vendor-toggleable per source: supplier / website / individual / corporate
  • Live today in SG, MY, HK, TH
Reach

One adapter, multi-country distribution.

  • Multi-country

    Fusion Link is multi-currency and multi-timezone by design. One supplier connection reaches operators in every country we serve.

  • Airport-heavy

    Flight tracking, OTS+N stand-down timers, and airport-proximity surcharge rules in the storefront — built for the trip types most suppliers care about.

  • Cross-vendor reach

    Every operator is part of the same driver pool. Your booking has more potential cover than any single fleet could provide.

Plug in once. Distribute everywhere.

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.