Push tracking events and telematics readings.
Beta. This endpoint is in active development; the contract and behavior are subject to change before general availability.
Ingest one shipment tracking event, one set of telematics readings, and/or one or more stop updates for the shipment(s) resolved by the supplied identifiers. Send the Full Truckload data under the truckload key. All timestamps are ISO 8601 date-times (for example 2026-06-01T08:30:00Z). shipmentEvent.dateTime and readings.dateTime report something that has already happened, and are dropped if more than 5 minutes in the future. Stop times are forward-looking and are not subject to that limit: stops[].carrierEstimatedArrivalDateTime must carry a UTC offset or the Z designator, and the times in stops[].carrierAppointmentWindow are local to the stop, where an offset is optional.
<h4><b>Required Fields</b></h4><ul><li><b>truckload: </b></li><ul><li><b>identifiers: </b> at least one of billOfLadingNumber or orderNumber</li><li>at least one of shipmentEvent, readings or stops</li><li><b>shipmentEvent: </b> (if sent)</li><ul><li>type</li><li>dateTime</li></ul><li><b>readings: </b> (if sent)</li><ul><li>dateTime</li><li>at least one of position or sensor</li><li><b>position: </b> (if sent)</li><ul><li>latitude</li><li>longitude</li></ul></ul><li><b>stops: </b> (if sent), each entry</li><ul><li>one of stopNumber, stopReferenceId or stopId</li><li>at least one value to set: carrierEstimatedArrivalDateTime or carrierAppointmentWindow</li><li><b>carrierAppointmentWindow: </b> (if sent)</li><ul><li>startDateTime</li><li>endDateTime</li></ul></ul></ul></ul>Request
- Base URLhttps://na12.api.project44.com
- AuthOAuth 2Client credentialsToken URL/api/v4/oauth2/token
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Request body
Response
Accepted. The payload passed synchronous validation and was queued for asynchronous processing.
Changes
No recorded changes to this operation across all 1 revision of this API.