🗣️ Roles: Admin, Partner Admin

Overview

The P44 integration with Alvys streamlines load tracking by automatically submitting location information in a standardized format at specific time intervals. This collaboration simplifies the process of managing transportation operations and provides customers with an efficient approach to tracking their shipments.

Before You Begin

P44 must create a dedicated integration user per carrier, not a normal portal user. The integration user is scoped by region like North America or Europe and by P44 carrier profile. Carriers with multiple SCACs may need multiple integration users if tied to separate profiles.

The shipper must enable Carrier Push Tracking for the carrier in the P44 portal, or no data will flow. After you create an OAuth client for this user, you must add the permission Carrier Push Tracking API.

💡 Fill out the TMS self-serve form or contact P44 directly to obtain a dedicated integration user for your carrier. P44 will ask for an email address you manage and the name of at least one customer you want this integration activated for.

Set Up Integration with P44 in Alvys

In Alvys, select the integration type Visibility and choose Project 44. Use the credentials for the P44-created integration user that was provided by P44. Do not reuse a standard portal login.

Save the integration and proceed to validate tracking using the validation checklist below.

Configure P44 Portal Permissions

Sign in with or manage the P44-created integration user and navigate to User Management in the P44 portal. Locate the OAuth client associated with this user, often labeled with Alvys.

Add the permission Carrier Push Tracking API, which is required for API calls. Ask the shipper to enable Carrier Push Tracking for this carrier in the P44 portal if not already enabled.

Customize P44 Preferences

Easily customize P44 settings to suit your preferences directly within the Customer Profile. Here, you can fine-tune event settings for sending location information and manage event sources.

Manage Automatic Location Updates

Once initial conditions are met for a load, Alvys activates the automatic location update indicator for P44 in Load Details. You can disable updates per load or at the Customer level by adjusting preferences through the Customizing P44 Preferences workflow above.

Validate Your Setup

Use this checklist to confirm your P44 integration is working correctly. The integration should authenticate without 401 errors. Carrier Push Tracking API permission must be enabled on the integration user's OAuth client. The shipper must have enabled Carrier Push Tracking for this carrier in P44. A test shipment's updates should appear in P44 under the correct Shipment ID.

Troubleshoot Common Issues

401 errors typically indicate wrong user (not the P44 integration user), wrong region or profile, missing Carrier Push Tracking API permission, or shipper feed not enabled.

If the carrier also sends telematics like Samsara with a different Shipment ID, P44 prioritizes ELD. Align Shipment IDs or pause telematics as needed.

Cross-region cases, such as an EU carrier with an NA shipper, may require P44 to mirror accounts. Request this from P44 support if needed.

FAQs

Q: Can I use my regular P44 portal login for this integration?

A: No, you must use a dedicated integration user created by P44 specifically for API access.

Q: Why am I getting 401 authentication errors?

A: Check that you're using the correct integration user, the Carrier Push Tracking API permission is enabled, and the shipper has enabled the feed for your carrier.

Q: What if I operate in multiple regions?

A: You may need multiple integration users scoped to different regions, or P44 can mirror your account across regions.