Version 4.0.0 of project44's API
Version 4.0.0 of project44's API
API used for registering and managing OAuth 2.0 client applications. See the "Authentication" section above for more information. To authorize API requests to project44 for an API integration, first your client application must be registered with project44, which will issue your application a client id and secret. These credentials can then be used to generate bearer tokens, which can be included on all other API requests to authorize your client application. The client application is authorized through the project44 user management UI as a machine user with username "app-{client_id}@client-applications.project44.com".
An admin user (with VOC user role "Customer Admin") must use HTTP Basic Authentication with this API to manage client applications. Basic Authentication is deprecated for all other APIs, besides token generation, in favor of passing the access token generated via OAuth 2.0.
API for OAuth 2.0 token generation. See the "Authentication" section above for more information. Once your client application is registered, you can use the token generation endpoint to authenticate with your application's client id and secret in exchange for a bearer token to be included on all other API requests to authenticate as that client application. The client application is authorized through the project44 user management UI as a machine user with username "app-{client_id}@client-applications.project44.com".
To generate an access token, you may authenticate your client application by providing its client id and secret either in the body of the request or in the form of HTTP Basic Authentication (but you may not use both ways in the same request).
rateQuoteQuery
List of accessorial services to be quoted for this shipment.
Contains fields used to configure the rate quote API.
The requested capacity provider account group containing the account used for authentication with the capacity provider's API.
A date and time range, local to the applicable location, representing a window of availability.
An override of direction for all capacity provider accounts used by this request that have 'Enable API override of direction' set as 'true' in the project44 Self-Service Portal.This functionality is typically used in situations where both inbound and outbound shipments are common for a given capacity provider and account number.
A more granular representation of a line item. Required if no lineItems. Allows for order level tracking, more accurate rates, and more detailed BOLs. Currently not supported by all vendors. An enhancedHandlingUnit consists of one or more handling units, e.g. a pallet or a drum, one or more packages (the container on the handling unit e.g. a box), and package contents. NMFC codes and freight classes can be assigned at the handling unit and package level, while package contents can be associated with a DELIVERY_NUMBER, SKU_NUMBER, or PURCHASE_ORDER_NUMBER. Passing in both this field and lineItems is accepted, but at least one is required.
Length measurement unit for all length values in this rate quote query. (default: 'IN')
The line items composing the shipment to be quoted. A line item consists of one or more packages, all of the same package type and with the same dimensions, freight class, and NMFC code. Each package, however, may have a different number of pieces and a different weight. Note that each capacity provider has a different maximum number of line items that they can quote. NOTE: This field is similar to, but not the same as, the enhancedHandlingUnits field. The handling units fields can contain more detailed information for use by both the carrier and the shipper. Passing in both this field and enhancedHandlingUnit is accepted, but at least one is required.
An override of payment terms for all capacity provider accounts used by this request that have 'Enable API override of payment terms' set as 'true' in the project44 Self-Service Portal. This functionality is typically used in situations where both inbound and outbound shipments are common for a given capacity provider and account number.
A date and time range, local to the applicable location, representing a window of availability.
The currency that you would like the rate quote to be returned in. If the currency is supported by the carrier, it will be returned in both the default currency and preferred currency fields. If the carrier does not support the requested currency, we will convert it on behalf of the carrier using the current exchange rate. The preferred currency will be returned in the “preferred currency” fields within the response. The carrier’s original currency will be returned in the default currency fields within the response. Exchange rate information will also be returned in the response for audit purposes.
The preferred system of measurement for all values with a unit in this rate quote. The default behavior is to return the unit of measurement specified by the carrier in the response.
The total linear feet that the shipment being quoted will take up in a trailer. Required only for volume LTL shipments. Customers who have enabled our Volume Visualizer product may submit rate requests without providing a value for totalLinearFeet. Linear footage will be automatically calculated, based on line item details, and submitted with your rate request. If a value is provided for totalLinearFeet, it will be submitted with the request and no calculation will be performed.
curl -i -X POST \ https://developers.project44.com/_mock/api-reference/api-docs/api/v4/vltl/quotes/rates/query \ -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \ -H 'Content-Type: application/json' \ -d '{ "accessorialServices": [ { "code": "string" } ], "apiConfiguration": { "accessorialServiceConfiguration": { "allowUnacceptedAccessorials": true, "fetchAllGuaranteed": true, "fetchAllInsideDelivery": true, "fetchAllServiceLevels": true }, "enableUnitConversion": true, "fallBackToDefaultAccountGroup": true, "timeout": 0 }, "capacityProviderAccountGroup": { "code": "string", "accounts": [ { "code": "string" } ] }, "deliveryWindow": { "date": "2019-08-24", "startTime": "15:00", "endTime": "17:00" }, "destinationAddress": { "postalCode": "string", "addressLines": [ "str" ], "city": "string", "state": "string", "country": "US" }, "directionOverride": "SHIPPER", "enhancedHandlingUnits": [ { "commodityType": "string", "contact": { "companyName": "string", "contactName": "string", "phoneNumber": "string", "phoneNumberCountryCode": "string", "phoneNumber2": "string", "phoneNumber2CountryCode": "string", "email": "string", "faxNumber": "string", "faxNumberCountryCode": "string" }, "deliveryStopNumber": 0, "description": "string", "freightClasses": [ "50" ], "handlingUnitDimensions": { "length": 0, "width": 0, "height": 0 }, "handlingUnitQuantity": 0, "handlingUnitType": "BAG", "harmonizedCode": "string", "nmfcCodes": [ { "code": "string" } ], "packages": [ { "contact": { "companyName": "string", "contactName": "string", "phoneNumber": "string", "phoneNumberCountryCode": "string", "phoneNumber2": "string", "phoneNumber2CountryCode": "string", "email": "string", "faxNumber": "string", "faxNumberCountryCode": "string" }, "description": "string", "freightClass": "50", "involvedParties": [ { "partyIdentifiers": [ null ] } ], "nmfcCodes": [ { "code": "string" } ], "packageContainerType": "BAG", "packageContents": [ { "countryOfManufacture": "US", "description": "string", "hazmatDetails": [ null ], "packageContentIdentifiers": [ null ], "packageContentQuantity": 0 } ], "packageDimensions": { "length": 0, "width": 0, "height": 0 }, "packageQuantity": 0, "weightPerPackage": 0 } ], "pickupStopNumber": 0, "stackable": true, "totalValue": { "currency": "USD", "amount": 0 }, "weightPerHandlingUnit": 0 } ], "lengthUnit": "IN", "lineItems": [ { "id": 0, "totalWeight": 1, "packageDimensions": { "length": 0, "width": 0, "height": 0 }, "freightClass": "50,55,60,65,70,77.5,85,92.5,100,110,125,150,175,200,250,300,400,500", "packageType": "BAG", "totalPackages": 1, "totalPieces": 1, "description": "string", "stackable": true, "nmfcItemCode": "string", "nmfcSubCode": "string", "hazmatDetail": { "identificationNumber": "string", "properShippingName": "string", "hazardClass": "string", "packingGroup": "I" }, "commodityType": "string", "harmonizedCode": "string", "countryOfManufacture": "US", "totalValue": 0 } ], "originAddress": { "postalCode": "string", "addressLines": [ "str" ], "city": "string", "state": "string", "country": "US" }, "paymentTermsOverride": "PREPAID", "pickupWindow": { "date": "2019-08-24", "startTime": "15:00", "endTime": "17:00" }, "preferredCurrency": "USD", "preferredSystemOfMeasurement": "METRIC", "totalLinearFeet": 0, "weightUnit": "LB" }'
{ "rateQuotes": [ { … } ] }
project44's Truckload Tracking endpoints give you or your customers visibility into your truckload shipments, including such features as predictive ETAs and temperature tracking. Use these endpoints to initialize (POST), track (GET), update (PUT), cancel (POST) or delete(DELETE) truckload shipments. You can return shipment information by either unique system ID or by identifier.
Manage capacity provider account groups. Groups are used to sort capacity provider accounts on a per customer or location basis.
For example, you can add multiple capacity providers to a group if they all share lanes to the same origin/destination location.
Another example, if certain customers receive different rates for a capacity provider, it may be reasonable to use separate groups for each customer's capacity provider accounts.
Use these APIs to create (POST), retrieve (GET) or delete (DELETE) capacity provider account groups.
Manage capacity provider accounts where a capacity provider is typically used to represent a carrier.
Capacity providers have capacity provider account definitions also known as capacity provider account types. Capacity provider accounts are arranged in sets where each set contains one or more accounts for the same capacity provider. Each capacity provider's service is compatible with one and only one of these capacity provider accounts. Because most capacity providers have only one capacity provider account definition, most sets will contain only one capacity provider account. For capacity providers with more then one account definition, the set of accounts may consist of one account per account definition.
For example, FedEx has a standard account to be used with LTL rating, LTL and Volume LTL dispatch, tracking, and imaging and a separate account for Volume LTL rating. A set of FedEx capacity provider accounts may have a single standard account, a single volume LTL rating account, or both. Providing the capacity provider account set code in the request resolves which capacity provider account to use.
Capacity provider specific credential information is available in the portal.
Use these APIs to create (POST), retrieve (GET), update (POST) or delete (DELETE) capacity provider accounts.
Manage locations. Locations combine physical addresses with contact details and are used in configuring Capacity Provider Accounts and Stop Locations, for example to identify the Bill To party.
Use these APIs to create (POST), update (PUT) or retrieve (GET) locations.
These operations are also all available under the /locations endpoint for backward compatibility.
Track parcel shipments. Before parcel shipments can be tracked, they must first be initialized with a shipment identifier. Shipments cannot be modified once initialized and tracking has begun. To stop tracking a shipment, delete it.
Use these APIs to initialize (POST), track (GET), or delete (DELETE) parcel shipments.