HaulMatch
Documentation menu
Preview

Connect your driver fleet

Configure carrier teams, submit quotes, choose payout ownership and allocate operating drivers.

By HaulMatch · Updated

Integrations are in preview. Setup access depends on rollout and provider configuration. If your settings show integrations are not enabled, contact HaulMatch for availability. Contact us.

On this page

Before you start

Sign in to the Company portal and select your carrier organization. Owners and dispatch staff can use COMPANY accounts without a vehicle profile or driver onboarding. The organization owner configures teams, payout choices and connection credentials. Admins manage operations; submanagers are limited to assigned teams. Member drivers continue using their own assigned-job flows.

1. Organize your teams

  1. Open People and choose Company staff or Operating driver when inviting a member. Assign Administrator / dispatcher for organization operations, Team manager for assigned-team operations, or Member for read-only staff access.
  2. In Fleet, create a team, select it, and assign organization members. Mark a dispatcher as a team submanager when they should manage that team.
  3. In Connections, create a scoped key. Select a team first when the connection should be limited to that team. A key’s fixed team restriction takes precedence over teamId in a request.

2. Choose who receives payment

The owner chooses which payout modes are available to the fleet. For company pay, submit company verification in Company wallet and complete company payout onboarding. Staff review the company and GST evidence; an ABN checksum alone does not approve the company. Stripe transfer and payout capabilities must also be ready before a company-pay quote is awarded.

Payout modeCommercial provider and payment recipient
DRIVERThe quote names a current member driver. Their personal wallet receives payment; the named driver remains attached during delivery.
COMPANYThe fleet is the commercial provider and payee. Its company wallet receives payment. Assign an operating driver separately before transit.
Changing the operating driver on a company-pay job does not change the agreed commercial provider or payment wallet.

3. Find work and submit quotes

Use GET /loads to browse available marketplace loads. POST /quotes requires an explicit payoutMode and a data object containing jobId and amount. DRIVER mode also requires the member driverId. Quote amounts are AUD excluding GST, with at most two decimal places.

Use quotes:write for quote creation, updates and withdrawal. Use stable idempotency keys, and store the returned quote ID against your external reference. Pending quotes can be updated or withdrawn through the documented endpoints.

Driver-pay quote request body (JSON)
{
  "externalRef": "TMS-QUOTE-1001",
  "payoutMode": "DRIVER",
  "driverId": "REPLACE_WITH_MEMBER_DRIVER_ID",
  "data": {
    "jobId": "REPLACE_WITH_HAULMATCH_JOB_ID",
    "amount": 450,
    "message": "Available tomorrow with a flatbed"
  }
}

4. Allocate a driver and update delivery

  1. For a company-pay job, allocate a verified current member driver in the assigned team using POST /jobs/{jobId}/driver or the operating-driver control on the company Jobs page.
  2. Before transit, confirm that the driver is eligible and the payment is held in escrow.
  3. Start transit with IN_TRANSIT, then report COMPLETED after delivery. Updates remain subject to organization, team and job lifecycle permissions.

5. Manage company payouts

The owner manages the company balance and bank accounts in Company wallet. Withdrawal confirmation requires the owner’s email code, tied to the chosen amount and bank account. Codes expire after ten minutes and allow five attempts.

Inspect payout status before retrying an uncertain result. Integration keys cannot initiate withdrawals or other company money movements. Driver-pay jobs continue paying the named driver’s personal wallet.