Skip to main content
FleetWorks automatically syncs carrier bids to your TMS when carriers submit bids on loads. The integration includes bid details and carrier information.

​
Supported TMS Integrations

If you’re using one of the following TMS platforms, bid sync is automatically enabled when you connect your TMS to FleetWorks:
  • McLeod - Bids are logged as carrier notes with pricing details
  • Revenova - Bids are pushed via Revenova API with full carrier information
  • Aljex - Carrier bids are created directly in Aljex shipments
No additional configuration needed for supported TMS platforms. Bids sync automatically.

​
Custom TMS Integration (Webhook-Based)

If you’re using a custom TMS or a TMS not listed above, FleetWorks can send bid events to your system via webhooks.
Webhook configuration is only needed for customers on custom TMS. If you’re using McLeod, Revenova, or Aljex, bids sync automatically via direct API integration.

​
Setting Up Webhooks

To enable webhook-based bid notifications for your custom TMS: Contact Support: support@fleetworks.ai What we’ll need:
  • Your webhook endpoint URL (HTTPS required)
  • A Bearer token that we’ll use to authenticate requests to your endpoint
  • Any custom headers required by your system (optional)
  • IP allowlist requirements (if applicable)
Setup process:
  1. Share your technical requirements with our team (endpoint URL, Bearer token, etc.)
  2. We’ll configure and test the integration in staging
  3. Verify you’re receiving test webhook events correctly
  4. We’ll enable the integration in production
  5. Ongoing monitoring and support included

​
Webhook Payload

​
event
string
required
Event type: bid_created.
​
loadId
string
required
Load identifier
​
amount
number
required
Bid amount
​
notes
string
Additional bid details
​
url
string
Link to bid on FleetWorks platform
​
source
object
required
Source of the bid
​
carrier
object
Carrier details
​
metadata
object
Additional metadata as key-value pairs
{
  "event": "bid_created",
  "loadId": "LOAD-12345",
  "amount": 2500.00,
  "notes": "Can pickup tomorrow morning, have reefer available",
  "url": "https://app.fleetworks.ai/conversations/98765",
  "source": {
    "sourceType": "call",
    "id": "call_abc123",
    "direction": "inbound",
    "fromParty": {
      "partyType": "carrier",
      "phone": {
        "e164Number": "+14155551234"
      },
      "name": "John Smith"
    },
    "toParty": {
      "partyType": "broker",
      "phone": {
        "e164Number": "+14155559876"
      }
    }
  },
  "carrier": {
    "mcNumber": "123456",
    "dotNumber": "987654",
    "companyName": "ABC Trucking LLC",
    "phone": {
      "e164Number": "+14155551234"
    },
    "email": "dispatch@abctrucking.com",
    "compliance": {
      "hwConnectionStatus": "CONNECTED",
      "hwRulesAssessment": "APPROVED"
    }
  },
  "metadata": {}
}

​
Webhook Security

Webhooks are authenticated using Bearer token authentication. You’ll provide us with your secret token during setup, and we’ll include it in the Authorization header of each webhook request: 
Authorization: Bearer your-secret-token
This allows you to verify that webhook requests are coming from FleetWorks.