project44

project44 is a leading supply chain visibility platform that provides real-time tracking and analytics for shipments, helping logistics companies and shippers optimize their supply chain operations with comprehensive visibility and predictive insights.

Power end-to-end data operations for your project44 API with Nexla. Our bi-directional project44 connector is purpose-built for project44, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to project44 or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your project44 workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a project44 credential, you need to obtain your project44 username and password, and identify your API environment URL from your project44 account. project44 uses Basic Authentication for all API requests, with the username and password sent in the Authorization header.

To obtain your project44 API credentials, follow these steps:

1. Sign in to your project44 account using your administrator credentials.

2. Navigate to your project44 account settings or API management section in the project44 interface.

3. Look for the API or API Credentials section in your account settings.

4. Your project44 username is typically your project44 account username or the username assigned to your project44 API account.

5. Your project44 password is the password associated with your project44 API account. This password is used for Basic Authentication.

6. Identify your project44 API environment URL:

   • Production API Server: https://cloud.p-44.com (for production environments)
   • Test API Server: https://test.p-44.com (for testing environments)

7. Store all credentials securely, as you will need them to configure your Nexla credential. The username and password are sensitive information and should be kept confidential.

The username and password are sent in the Authorization header using Basic Authentication (Base64-encoded) for all API requests to the project44 API. The API environment URL determines which project44 API server (production or test) your API requests will be sent to. If your credentials are compromised, you should immediately change your password in your project44 account settings. For detailed information about project44 authentication, API access, and available endpoints, refer to the project44 Developer documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Username	Yes	No	Your project44 API Username.
Password	Yes	Yes	Your project44 API password.
API Environment / URL	Yes	No	Select the project44 API environment you wish to access. Each environment maps to the corresponding project44 API server. Allowed values: Production API Server (Access API Server: https://cloud.p-44.com); Test API Server (Access API Server: https://test.p-44.com)

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – project44

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your project44 username in the Username field. This is the username associated with your project44 API account. The username is used for Basic Authentication.

4. Enter your project44 password in the Password field. This is the password associated with your project44 API account. The password is sent in the Authorization header using Base64 encoding for all API requests to the project44 API. The password is sensitive information and must be kept confidential.

5. Select your project44 API environment from the API Environment / URL pulldown menu. Select Production API Server (https://cloud.p-44.com) for production environments, or Test API Server (https://test.p-44.com) for testing environments. The API environment determines which project44 API server your API requests will be sent to.

   Your project44 API credentials can be found in your project44 account settings under the API or API Credentials section. The username and password are sent in the Authorization header using Basic Authentication (Base64-encoded) for all API requests to the project44 API. The API environment should match your project44 environment (production or test).

   If your credentials are compromised, you should immediately change your password in your project44 account settings. The username and password provide access to your project44 account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.

   For detailed information about project44 authentication, API access, and available endpoints, see the project44 Developer documentation.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.

Use as a destination

Click the + icon on the Nexset that will be sent to the project44 destination, and select the Send to Destination option from the menu. Select the project44 connector from the list of available destination connectors, then select the credential that will be used to connect to your project44 account, and click Next; or, create a new project44 credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common project44 endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Upsert Shipment Details

This endpoint template creates or updates initial details about a shipment to initialize shipment tracking in project44. Use this template when you need to create new shipments or update existing shipment information in your project44 account. You must ensure you include all required fields in every record even if only one field includes a new piece of information.

• This endpoint automatically creates or updates shipments from your data. No additional configuration is required beyond selecting this endpoint template. The request body should contain the shipment data in JSON format matching the project44 API structure.

This endpoint sends data as JSON in the request body to create or update shipment details in your project44 account. Each record from your Nexset will be sent as a separate API request to upsert a shipment in project44. The request body should contain all required shipment fields in the format required by the project44 API, even if only one field includes new information.

The shipment structure must match the project44 API's expected format. For detailed information about shipment creation and updates, request body formats, available shipment properties, and required fields, see the project44 Developer documentation.

Create status updates for a shipment

This endpoint template pushes tracking status updates for a shipment while the shipment is in transit. Use this template when you need to update the tracking status of shipments in your project44 account with real-time status information.

• This endpoint automatically creates status updates from your data. No additional configuration is required beyond selecting this endpoint template. The request body should contain the status update data in JSON format matching the project44 API structure.

This endpoint sends data as JSON in the request body to create status updates for shipments in your project44 account. Each record from your Nexset will be sent as a separate API request to create a status update for a shipment in project44. The request body should contain the status update data in the format required by the project44 API.

The status update structure must match the project44 API's expected format. For detailed information about status update creation, request body formats, available status update properties, and shipment tracking, see the project44 Developer documentation.

Manual configuration

project44 destinations can also be manually configured to send data to any valid project44 API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

project44 API typically uses the PUT method for upserting resources (such as shipments) and the POST method for creating resources (such as status updates), and expects JSON for all request bodies. The endpoint URL should include your API URL (from your credential) plus the API path, for example /api/v4/capacityproviders/ltl/shipments. For detailed information about request body formats and available endpoints, see the project44 Developer documentation.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured project44 endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the project44 endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.