Capacity Sourcing

Bid Created

v1 equivalent: bidCreated (flat payload — the data fields below are sent at the top level, without the envelope).

Sent when a carrier expresses interest in a load, including when the carrier did not provide a dollar amount. Clients must configure a PUSH_BID_TO_TMS webhook subscription to receive these callbacks. offerAmount can be null. workflow is CARRIER_SELECTION.

post/BID_CREATED

Request

Request body

idstring required

Unique event identifier (ULID)

workflow'TRACK_AND_TRACE' | 'CARRIER_SUPPORT' | 'POD_COLLECTION' | 'LOAD_BUILDING' | 'CARRIER_SELECTION' | 'SCHEDULING' | 'CUSTOMER_SUPPORT' | 'null' nullable required

The Augment workflow that produced this event, or null when no single workflow can be attributed. New values may be added over time, so treat this as an open set rather than a fixed list.

occurredAtstring date-time required

When the underlying activity occurred (ISO 8601)

loadNumberstring nullable required

Your load reference number

customerLoadInternalIdstring nullable required

Your internal load ID, if provided during load creation

eventType'BID_CREATED' required

Event name for a carrier bid.

Example request

{
  "data": {
    "bidId": "bid-abc-123",
    "createdAt": "2026-02-19T14:30:00.000Z",
    "loadReference": "LOAD-456",
    "internalLoadReference": "INT-789",
    "carrier": {
      "id": "carrier-001",
      "mcNumber": 123456,
      "dotNumber": 7890123
    },
    "offerAmount": 2500,
    "channel": {
      "type": "call",
      "phone": "+15551234567"
    },
    "truckEmpty": {
      "city": "Dallas",
      "stateOrProvince": "TX",
      "country": "US",
      "dateTime": "2026-02-20T08:00:00.000Z"
    },
    "repId": "rep-456"
  }
}

Response

Bid received successfully

Changes

No recorded changes to this operation across all 1 revision of this API.