{"templateId":"markdown","sharedDataIds":{"sidebar":"sidebar-guides/carriers/visibility/universal-push/sidebars.yaml"},"props":{"codeGuideFiles":[],"dynamicMarkdocComponents":[],"metadata":{"type":"markdown"},"seo":{"title":"Universal PUSH Endpoint - project44 Developer Portal","description":"Integration guide & API reference for project44's Universal PUSH endpoint - a single carrier-facing API for pushing telematics, events, and stop-schedule updates."},"ast":{"$$mdtype":"Tag","name":"article","attributes":{},"children":[{"$$mdtype":"Tag","name":"Heading","attributes":{"level":1,"id":"universal-push-endpoint"},"children":["Universal PUSH Endpoint"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["The Universal PUSH endpoint is a carrier-facing API for pushing Full Truckload (FTL) telematics, events, and stop updates to project44."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["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."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":[{"$$mdtype":"Tag","name":"Admonition","attributes":{"type":"info"},"children":[" Currently, ",{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Full Truckload (FTL)"]}," is fully supported. This guide is focused on the Full Truckload contract. "]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"who-should-use-this-endpoint"},"children":["Who should use this endpoint"]},{"$$mdtype":"Tag","name":"ul","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":[{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Asset-based carriers"]}," that operate equipment and want to report position, events, or sensor state to shippers via project44."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":[{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Telematics and IoT providers"]}," that aggregate data from carrier fleets and push to project44 on carriers' behalf."]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"how-it-works"},"children":["How it works"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Send a single ",{"$$mdtype":"Tag","name":"code","attributes":{},"children":["POST"]}," per update to the ",{"$$mdtype":"Tag","name":"code","attributes":{},"children":["tracking-updates"]}," endpoint for your tenant's region."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":[{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["NA:"]}]},{"$$mdtype":"Tag","name":"CodeBlock","attributes":{"header":{"controls":{"copy":{}}},"source":"https://na12.api.project44.com/services/carrier-push/v1/tracking-updates\n"},"children":[]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":[{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["EU:"]}]},{"$$mdtype":"Tag","name":"CodeBlock","attributes":{"header":{"controls":{"copy":{}}},"source":"https://eu12.api.project44.com/services/carrier-push/v1/tracking-updates\n"},"children":[]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["The endpoint validates the payload ",{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["synchronously"]}," and returns ",{"$$mdtype":"Tag","name":"code","attributes":{},"children":["202 Accepted"]}," with an ",{"$$mdtype":"Tag","name":"code","attributes":{},"children":["ingestionId"]}," before handing the payload off to asynchronous processing (identifier resolution and shipment matching). A ",{"$$mdtype":"Tag","name":"code","attributes":{},"children":["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 ",{"$$mdtype":"Tag","name":"code","attributes":{},"children":["truckload"]}," key."]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"onboarding"},"children":["Onboarding"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Connections and credentials are provisioned during carrier onboarding in Movement. Contact your project44 integration representative to start onboarding."]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"next-steps"},"children":["Next steps"]},{"$$mdtype":"Tag","name":"ul","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":[{"$$mdtype":"Tag","name":"a","attributes":{"href":"/guides/carriers/visibility/universal-push/authentication"},"children":["Authentication"]}," — OAuth2 setup per connection."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":[{"$$mdtype":"Tag","name":"a","attributes":{"href":"/guides/carriers/visibility/universal-push/send-tracking-updates"},"children":["Send Tracking Updates"]}," — worked examples for the common FTL scenarios."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":[{"$$mdtype":"Tag","name":"a","attributes":{"href":"/guides/carriers/visibility/universal-push/appendix"},"children":["Appendix"]}," — identifier reference, event types, limits, and error codes."]}]}]},"headings":[{"value":"Universal PUSH Endpoint","id":"universal-push-endpoint","depth":1},{"value":"Who should use this endpoint","id":"who-should-use-this-endpoint","depth":2},{"value":"How it works","id":"how-it-works","depth":2},{"value":"Onboarding","id":"onboarding","depth":2},{"value":"Next steps","id":"next-steps","depth":2}],"frontmatter":{"seo":{"title":"Universal PUSH Endpoint - project44 Developer Portal","description":"Integration guide & API reference for project44's Universal PUSH endpoint - a single carrier-facing API for pushing telematics, events, and stop-schedule updates."}},"lastModified":"2026-08-03T11:48:22.000Z"},"slug":"/guides/carriers/visibility/universal-push","userData":{"isAuthenticated":false,"teams":["anonymous"]}}