Last updated

Authentication

Beta. The Universal PUSH endpoint is in active development; documentation and behavior are subject to change before general availability.

Universal PUSH uses project44's standard OAuth2 authentication. Obtain an access token with your project44 client credentials and pass it as a Bearer token on every request. See the Authentication guide for creating a client application, assigning roles and access groups, generating a token, and rotating credentials.

Authorization: Bearer <your-access-token>

Pushing for Another Carrier

Your access token identifies you as the carrier making the call. When you push for a different carrier — for example as a telematics provider, transportation management system (TMS), or third-party logistics provider (3PL) — name that carrier with one of the carrier-identifier keys scac, dotNumber, or mcNumber in the identifiers object.

These keys determine which carrier the tracking data is attributed to, so they are not optional in that scenario. See Pushing for Another Carrier for the full reference.

project44 must authorize you to report for each carrier before you start. Contact your project44 integration representative to set this up.