Unfortunately, this feature is not supported on mobile devices. For the best experience, please use a computer.

project44 REST API (4.0.0)

Version 4.0.0 of project44's API

Download OpenAPI description
Languages
Servers
Mock server
https://developers.project44.com/_mock/guides/shippers/visibility/ltl/api/
API endpoint for project44 tenants created in NA region
https://na12.api.project44.com/
API endpoint for project44 tenants created in EU region
https://eu12.api.project44.com/
API endpoint for project44 tenants created in the Sandbox environment
https://na12.api.sandbox.p-44.com/

Manage Client Applications

Operations

Generate Tokens

Operations

Grant access token.

Request

Authenticate with your client application's credentials (id and secret) to generate a new project44 access token. The resulting access token can be used as a bearer token to access your project44 account and data via project44's other APIs, while acting as that client application.

You may authenticate your client application either by passing the id and secret via HTTP Basic Authentication (via the "Authorization" HTTP header) or via the client_id and client_secret fields in the POST request body with no "Authorization" header included. You may not use both approaches to authenticate the same request.

The POST request body must contain the request fields as URL-encoded parameters (a URL-encoded form) and must have the "Content-Type" HTTP header set to "application/x-www-form-urlencoded".

(Note: The endpoint "/api/v4/oauth/token" is deprecated. Please use this endpoint instead: "/api/v4/oauth2/token".)

Required Fields

  • client_id
  • client_secret
  • grant_type
Bodyapplication/x-www-form-urlencoded
client_idstring

The id of the client application, generated and assigned by project44 via the OAuth 2.0 client applications APIs.

client_secretstring

The secret part of the client application's credentials, generated and assigned by project44 via the OAuth 2.0 client applications APIs.

grant_typestring

The OAuth 2.0 authorization grant type, or flow, to be used by the client application. project44 supports only the "client_credentials" grant type and does not currently support grant types involving end user consent.

Value"client_credentials"
curl -i -X POST \
  -u <username>:<password> \
  https://developers.project44.com/_mock/guides/shippers/visibility/ltl/api/api/v4/oauth2/token \
  -H 'Content-Type: application/x-www-form-urlencoded' \
  -d client_id=string \
  -d client_secret=string \
  -d grant_type=client_credentials

Responses

OK

Bodyapplication/json
access_tokenstring

The project44 access token, which can be passed as a bearer token to all other project44 endpoints to have your client application's requests authorized. Pass the "Authorization" HTTP header to other endpoints in this form: "Authorization: Bearer {access_token}". Your client application can be granted roles and permissions via the project44 user management UI under user "app-{client_id}@client-applications.project44.com".

expires_ininteger(int64)

The time in seconds for which the access token will be valid before expiring. Tokens currently last approximately 12 hours, but this is subject to change by project44 in the future. Tokens should be reused by your application to the fullest extent possible for performance and security reasons by storing the token in a secure cache. Instead of using this expiration time to know when to generate a new access token, simply make requests with the token until project44 responds with a "401 Unauthorized" HTTP status code, at which point your application should generate and cache a new one.

token_typestring

The type of access token returned. This will always be type "BEARER".

Value"BEARER"
Response
application/json
{ "access_token": "string", "expires_in": 0, "token_type": "BEARER" }

Unified Shipment Tracking

Operations

Deprecated LTL Modal Tracking

Operations

Shipment Attributes

Operations

Webhook

Operations