Skip to main content

Carrier Comment in Load Request Webhooks

The load_request webhook payload now carries a carrier_comment field. Carriers can attach a short note when sending or updating a load request, so you can weigh it before accepting the bid.

data.carrier_comment is a string limited to 160 characters.

{
"action": "load_request.created",
"order_guid": "823b7436-40d6-4039-bfe6-c7d90bd8c14d",
"action_date": "2020-01-20T09:33:21.266+0000",
"data": {
"guid": "u789102t-f59k-j893-bfe6-c7d90bd8790f",
"carrier_guid": "9b9fd584-800c-445d-81cb-c951daaeebcf",
"requested_price": "12",
"pickup_date": "2020-11-20T10:33:29.112+0000",
"delivery_date": "2020-11-20T10:33:29.112+0000",
"carrier_comment": "Can pick up a day earlier if the vehicle is ready."
}
}

What To Expect

  • The field is delivered with all four load request actions: load_request.created, load_request.updated, load_request.canceled_by_carrier, and load_request.declined_by_shipper.
  • carrier_comment is always present in the payload. When the carrier left no comment it is null, the same as the other data.carrier_* fields.
  • This is an additive change: carrier_comment is a new key, and no existing field or value changes. If your integration validates payloads against a strict schema, allow the new key before the change ships.
  • The comment belongs to the load request, not to the resulting order. It is not added to order.* webhook actions, and it does not appear on order responses after a request is accepted.

No other action is required. Existing integrations continue to work and can ignore the field.

See the Webhooks documentation for the full load request payload reference.