Universal PUSH Endpoint

The Universal PUSH endpoint is a carrier-facing API for pushing Full Truckload (FTL) telematics, events, and stop updates to project44.

This guide is for carrier integrators and telematics providers building against the endpoint. It walks through authentication, the request contract, and the common tracking scenarios you will send.

Who should use this endpoint

• Asset-based carriers that operate equipment and want to report position, events, or sensor state to shippers via project44.
• Telematics and IoT providers that aggregate data from carrier fleets and push to project44 on carriers' behalf.

How it works

Send a single POST per update to the tracking-updates endpoint for your tenant's region.

NA:

https://na12.api.project44.com/services/carrier-push/v1/tracking-updates

EU:

https://eu12.api.project44.com/services/carrier-push/v1/tracking-updates

The endpoint validates the payload synchronously and returns 202 Accepted with an ingestionId before handing the payload off to asynchronous processing (identifier resolution and shipment matching). A 202 means the payload passed validation and entered the pipeline — not that it has been matched to a shipment yet. Each request carries a JSON body with the FTL data nested under the truckload key.

Onboarding

Connections and credentials are provisioned during carrier onboarding in Movement. Contact your project44 integration representative to start onboarding.

Next steps

• Authentication — OAuth2 setup per connection.
• Send Tracking Updates — worked examples for the common FTL scenarios.
• Appendix — identifier reference, event types, limits, and error codes.