Reference · built on requestConnectorShipping & logistics

project44

Multimodal shipment tracking, ETAs, exceptions, and LTL quotes and dispatch from project44, pushed by webhook.

Request accessPricing ↗

About

project44 is a supply chain visibility platform. Shippers and logistics providers register their shipments, and project44 gathers positions, events, ETAs, and exceptions from connected carriers across full truckload, LTL, parcel, ocean, air, and rail. The Movement application shows the result; the v4 API exposes it as tracking, position history, event history, orders, and loads, with webhooks that push each change.

Through Fibric, an operator reads the tracking payload as it arrives and proposes the next move: a check-in on a shipment that stopped, a new dock slot when an ETA slips, or a cancellation and re-dispatch for a failed LTL pickup. You approve in place. The connector calls project44 once and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from project44 and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Shipment tracking through GET /api/v4/shipments/{shipmentId}/tracking: identifiers, stops, route segments, states, exceptions, and the plan of expected modes
  • Position history and event history through /positionhistory and /eventhistory, each returned in ascending time order
  • Webhook pushes of the same tracking-history payload, narrowed by payloadFilter or changeFilter, with retries for up to 48 hours
  • Order and load visibility through Order Visibility and Shipment: Loads, plus the Inventory Order and Load Webhook Data payload
  • Temperature setpoints and product categories in a shipment's contents, and reefer condition for full truckload
  • LTL rate and transit-time quotes from /api/v4/ltl/quotes/rates/query and /transittimes/query across your capacity provider accounts
  • Dock appointments, slots, and capacity through the Appointments, Slots, and Capacity APIs

Proposed actions

  • Target capability: propose initializing tracking for a shipment through POST /api/v4/shipments/tracking with identifiers such as BILL_OF_LADING and CARRIER_SCAC
  • Target capability: propose replacing a shipment's tracking data through PUT /api/v4/shipments/tracking, or ending it through DELETE /api/v4/shipments/{shipmentId}/tracking
  • Target capability: propose dispatching an LTL pickup through POST /api/v4/ltl/dispatchedshipments, which returns the carrier's pickup confirmation number
  • Target capability: propose cancelling a dispatched LTL shipment through POST /api/v4/ltl/shipments/{id}/cancellations
  • Target capability: propose registering or updating a webhook configuration through PUT /api/v4/webhooks

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Catch a truckload that has stopped moving

    The webhook payload carries positions in time order. When the latest position has not advanced along the route segment for longer than the lane allows, the operator opens an exception and proposes a carrier check-in for a dispatcher to send.

    With Stalled Shipment

  • Re-time the dock when the ETA slips

    A late ETA on an inbound shipment triggers a look at the Slots and Appointments APIs. The operator proposes a new slot that fits the receiving schedule; the dock lead approves it.

    With Dock Schedule, Inbound Delay

  • Warn the customer before the delivery is late

    An exception, or a delivery state that misses the promised window, drafts a notice that includes the shipmentShareLink, so the customer can watch the same tracking page you do.

    With ETA Notice

  • Re-dispatch after a carrier exception

    When a dispatched LTL pickup fails, the operator pulls fresh rateQuotes for the lane, proposes a cancellation and a new dispatch with a different capacity provider, and records the pickup confirmation number it gets back.

    With Carrier Exception

Requirements

  • A project44 account with a user who can create client applications in Movement and assign them roles and access groups
  • A client ID and secret exchanged at POST /api/v4/oauth2/token on na12.api.project44.com or eu12.api.project44.com; na12.api.sandbox.p-44.com for testing
  • Carriers connected to your project44 network, identified by SCAC or another carrier identifier, so tracking requests resolve to a capacity provider
  • For LTL quotes and dispatch, a capacity provider account group holding the account used with each carrier's API
  • An HTTPS endpoint for webhooks that answers within a few seconds and accepts one of API_KEY, BASIC, OAUTH2, MTLS, or AD_OAUTH2_CERT
Authentication
OAuth 2.0 client credentials: a client application created in Movement exchanges its ID and secret at POST /api/v4/oauth2/token for a bearer token that lasts about 12 hours.

Limits

  • General endpoints allow 600 requests per minute per organization and per IP address; the token endpoint allows 5 per minute. Excess returns 429.
  • Tokens last about 12 hours and project44 says that may change; the connector refreshes before expiry rather than per call.
  • Webhook deliveries time out after 20 seconds; 408, 429, and 502 to 504 are retried for up to 48 hours, other 4xx are not.
  • Image retrieval has lower limits: 200 requests per minute per organization in the Americas and 60 in Europe.

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request project44 ↗

Questions and answers

How does project44 tell you a shipment changed?
Through a webhook you register with PUT /api/v4/webhooks. project44 posts the same JSON that GET /api/v4/shipments/{shipmentId}/tracking/history returns, within seconds of an update. Set payloadFilter or changeFilter to cut noise. Deliveries that time out or return 408, 429, or 502 to 504 are retried for up to 48 hours.
Which modes does one API cover?
The Shipment: Tracking API covers full truckload, LTL, parcel, ocean, air, and rail through one set of endpoints. Each mode has its own guide for required identifiers and stops. Orders and loads are separate resources with their own webhook payload.
Can the connector book freight, or only watch it?
It can propose LTL work: rate and transit-time quotes from /api/v4/ltl/quotes, a pickup dispatched through /api/v4/ltl/dispatchedshipments, and a cancellation. Multi-Modal Booking and Ocean Booking exist in the reference but sit outside this listing until a deployment needs them.
Ask about project44

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with project44 through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy