--- title: "TMS 7.11 Project44 Carrier Aggregator" slug: "tms-711-project44-carrier-aggregator" tags: ["7.11", "Project44", "Project44 - Load Tracking", "Compiled from User Guide", "Admin"] updated: 2024-06-28T20:25:14Z published: 2024-06-28T20:25:14Z canonical: "documents.revenova.com/tms-711-project44-carrier-aggregator" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revenova.com/llms.txt > Use this file to discover all available pages before exploring further. # TMS 7.11 Project44 Carrier Aggregator ## **Overview** Project44 provides a direct pass-through to Carrier APIs for LTL quoting, tendering, and document retrieval. For Project44 tracking see the [Project44 tracking](/previous-releases/docs/project44-tracking) API article. Project44 provides users the ability to: - Get LTL Carrier Quotes. - Tender to LTL Carriers. - Load Tracking Visibility. - Document Retrieval. - Support for Hazardous Materials quoting and tendering. Project44 provides “push” status updates to the TMS via a sites-based web service. Inbound LTL load status packets are inserted in the Queued Transaction table and processed by the **QueuedTransactionJob.** Starting or stopping Project44 Unified load tracking sends outbound packets that are also processed by the **QueuedTransactionJob.** ## **Setup** ### **Enter Credentials** Enable the Project44 integration by: 1. Navigating to **TMS Admin**, 2. Select **Credentials**. 3. Select the **Global Services** tab, 4. Find Project44 in the list and open the card. 5. Check the **Enabled** and **Receive Updates** boxes. 6. Enter the **User ID** and **Password 1** into the text fields. 7. Click the **Save** button when finished. Valid credentials are required from a Project44 subscription. See examples in the table below. | User ID | Password 1 | Password 2 | Customer Number | | --- | --- | --- | --- | | Email address format | Required | | | **Inbound Packet IP Ranges**: Any post-backs from Project44 that do not originate from this IP mask are rejected as a security feature. Any changes to this range are provided by Revenova. ### **Remote Site Settings** Upgrading from previous versions of the TMS may have outdated information. Check that the Remote Site Settings for the Project44 integration URL are up to date. > [!NOTE] > There are TWO remote site settings required. One for the API and one for the BOL document URL. 1. Click the **Setup** gear icon in the top right corner. 2. From the drop-down, click **Setup**. 3. In the Quick Find Toolbar type *Remote Site Settings* and click the link. 4. From the list of remote sites find *Project44* and click the **Edit** link. 5. Update the Remote Site URL to match the *Service URL* below: 1. Service URL: https://na12.api.project44.com 2. Test Service URL: https://na12.api.sandbox.p-44.com 6. Request from Project44 what customer-specific URL documents are available from and add it as a Remote Site Setting. 1. It is in a format such as: https://prod-44742-images.s3.amazonaws.com. ### **Partner Community Setup** Project44 relies on a “push” approach to event processing, and requires a webhook to send information to the TMS. Create an API Site to accept inbound API traffic. 1. Create a Salesforce Site for API Guest User Access. 2. Set the public access for the Site. 3. Activate and Publish the Site. 4. Enter the API URL into the field for **Inbound API Community URL** under TMS Admin, in the Configuration section. 5. Add the following extension to the end of the URL to match the example below: /services/apexrest/rtms/tmslistener?org=00D180000008oA9EAI&source=Project44&pwd=4wGFDgnT950Ovg1 6. Send the post-back URL, the customer company name and contact info to support.americas@project44.com. **{API Community URL}** /services/apexrest/rtms/tmslistener?org= {18-character org id}&source=Project44&pwd= {credentials code field} **Example:** https://revenova.my.site.com/api/services/apexrest/rtms/tmslistener?org=00D180000008oA9EAI&source=Project44&pwd=4wGFDgnT950Ovg1 ### **Project44 Setup** Navigate to the [Project44 website](https://movement.project44.com/login) and log in. 1. Enter the Carrier credentials for each Carrier to quote/tender. > [!WARNING] > To properly tender, track, and manage documents with Carriers, the following information must be configured correctly. > > 1. All Carrier credentials are present and ***correct***. Billing information for the Carrier must also be correct. > 2. Account login groups are configured correctly. Blank values are acceptable when not using login groups. > 3. The SCAC fields in the Project44 portal should match the SCAC fields on the Carrier Transportation Profile. > > The following error displays if a Carrier is not enabled correctly in the Project44 website: > > ![Carrier Quotes Error P44(3)](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Carrier%20Quotes%20%20Error%20P44(3).png) 2. For customer-specific pricing: 1. Create a Login Group for each customer. 2. Populate the customer-specific credentials for each Login Group. 3. Copy the Carrier API Login Group field from Project44 into the **customer Transportation Profile** (in the TMS, on the Rates tab) with the Login Group Key. 4. Project44 supports a " **login group cascade**" concept. This allows for defining two login groups and setting the **Carrier API Login Group** field at both the **customer** and **default Transportation Profile** levels. When quotes are retrieved from Project44, two queries are made - one with each login group. Any quotes received from the first query are masked out of the second query. 5. Configure Carrier Pickup Notes on the Project44 website to prevent tenders from failing. (Note could be too long). 3. Multiple contracts for a given capacity provider can be set up by providing unique names in the Project44 portal. 4. See the Project44 Tracking article for additional tracking setup in the Project44 website (Reference Data Keys). ### **Other Setup** 1. A **Bill of Lading Number** is NOT generated by Project44. The BOL # is generated and passed from the TMS during the tender operation. 2. A **Bill of Lading Number** must be present to use the Truckload load tracking API. 3. Load status API calls may return **signed BOL** and **POD images**. > [!NOTE] > - The default **Tracking Provider** for a Carrier is selected on the Carrier's Transportation Profile on the *Settings* tab. > - Only tracking integrations with credentials display as possible options in the Tracking Provider picklist. > - Select Project44 as the default Tracking Provider for tracking LTL Mode loads. ### **TMS Admin** **Carrier Services** The following settings under TMS Admin, Carrier Services control when a **PRO Number** is generated. **Pickup Only**: Check the **Pickup Only** box on Project44 Carrier Services to not immediately generate a **PRO Number**. If the PRO Number changes later in the load lifecycle the tracking data will be invalid. ### **SMC3 Quoting + Project44 Tender/Track/Images** You may set up hybrid API carrier services that use SMC3 for quoting and Project44 for tendering, tracking, and image retrieval. These Carrier Services should be set up with the **SMC3 RateWare** Credentials Id.