Webhook

Bid Created

​

Payload is identical in v1 and v2 — no migration needed for this event.

Augment POSTs this payload to your configured bid-created endpoint 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. Unlike tracking and stop-update callbacks, bid postbacks use a subscription-based delivery model — configuring the subscription and authentication is sufficient to start receiving bid data.

Each callback contains a single BidCreated payload representing one carrier interest or bid. offerAmount can be null.

Body·

required
application/json

Carrier interest or a carrier bid submitted for a load. Delivered via PUSH_BID_TO_TMS webhook subscription. This callback is sent when a carrier expresses interest, even if the carrier did not provide a dollar offer amount.

  • bidId
    Type: string
    required

    Unique identifier for the bid

  • carrier
    required

    Carrier that submitted the bid. At least one of id, mcNumber, or dotNumber must be present.

    Carrier that submitted the bid. At least one of id, mcNumber, or dotNumber must be present.

    • id
      Type: string | null
      required

      Carrier identifier

    • dotNumber
      Type: number | null

      Carrier DOT number

    • mcNumber
      Type: number | null

      Carrier MC number

  • channel
    required

    Communication channel used for the bid. At least one of phone or email must be present.

    Communication channel used for the bid. At least one of phone or email must be present.

    • phone
      Type: string | null
      required

      Phone number (present for call-based bids)

    • type
      Type: "call" or "email"enum
      required

      Type of communication channel

    • email
      Type: string | nullFormat: email

      Email address (present for email-based bids)

  • createdAt
    Type: stringFormat: date-time
    required

    UTC ISO 8601 timestamp ending in Z of when the bid was created.

  • internalLoadReference
    Type: string
    required

    Augment internal load reference

  • loadReference
    Type: string
    required

    Brokerage load reference number

  • truckEmpty
    Type: object
    required

    Truck empty location and availability

    Properties: 4
  • offerAmount
    Type: number | null

    Bid offer amount in dollars. This can be null when the carrier expressed interest but did not provide a dollar amount.

  • repId
    Type: string | null

    Augment representative ID who facilitated the bid

Responses

  • 200

    Bid received successfully

Request Example for postbidCreated
{
  "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"
}
No Body

Bid received successfully

Previous
Carrier Issue Updated
Next
Load Draft