Universal PUSH Endpoint [Beta]

Beta. The Universal PUSH endpoint is in active development. Documentation and behavior are subject to change before general availability. Contact your project44 integration representative before you build against it.

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

This guide is for carrier integrators and telematics providers. It describes how to authenticate, how to structure a request, and how to send the tracking updates your mutual customer expects.

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

Each request carries a JSON body with the FTL data nested under the truckload key.

The endpoint validates the payload synchronously and returns 202 Accepted with an ingestionId. Identifier resolution and shipment matching then happen asynchronously, so a 202 confirms that the payload passed validation and entered the pipeline — not that it has been matched to a shipment.

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, the mapping from the Truckload status-update endpoint, limits, and error codes.