Skip to main content

Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a project44 location.
p44_api.png

project44

Create a project44 Destination​

  1. Click the + icon on the Nexset that will be sent to the project44 destination, and select the Send to Destination option from the menu.

  2. 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.

  3. In Nexla, project44 destinations can be created using pre-built endpoint templates, which expedite destination setup for common project44 endpoints. Each template is designed specifically for the corresponding project44 endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    project44 destinations can also be configured manually, allowing you to send data to project44 endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common project44 endpoints. Each template is designed specifically for the corresponding project44 endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, 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.

Configure Manually​

project44 destinations can be manually configured to send data to any valid project44 API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the project44 API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the project44 API from the Method pulldown menu. project44 API typically uses PUT method for upserting resources and POST method for creating resources.

Data Format​

  1. Select the format in which the Nexset data will be sent to the project44 API from the Content Format pulldown menu. project44 API expects JSON format for all requests.

API Endpoint URL​

  1. Enter the URL of the project44 API endpoint to which data will be sent in the URL field. This should be the complete URL including your API URL (from your credential), the API path (e.g., /api/v4/capacityproviders/ltl/shipments), and any required query parameters. Include any required path parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The project44 API endpoint URL should point to the endpoint where you want to create or update resources. The endpoint URL should include your API URL and the appropriate API path. You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the project44 API. The request body should contain the resource data formatted as JSON, with field names matching the project44 API's expected structure. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings.

The request body must be valid JSON and must match the project44 API's expected format for the specific endpoint you're using. project44 API uses specific structures for different endpoints (shipments, status updates, etc.). For detailed information about request body formats, available endpoints, and resource structures, see the project44 Developer documentation.

Save the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.