Obtain OAuth 2.0 client credentials from the project44 developer portal and POST to the token endpoint for your region (Americas: na12, EU: eu12) to get a bearer token
Create a shipment record by POST to the project44 shipments API with identifiers (PRO number, BOL, or tracking number), carrier SCAC code, origin, and destination
Subscribe to tracking updates by configuring a webhook in project44 or by polling GET /api/v4/shipments/{shipmentId}/tracking for latest position and ETA data
Parse the predictiveEta field from the tracking response and surface it in your TMS or customer-facing interface
For ocean shipments, use GET /api/v4/shipments/{shipmentId}/positionhistory and /eventhistory endpoints to retrieve vessel positions and port event milestones
Handle regional endpoint differences: use na12-based URLs for Americas shipments and eu12-based URLs for European shipments to comply with data residency requirements
Known gotchas
project44 is a B2B enterprise platform; API access requires a contracted account — there is no self-service sandbox open to the public, and attempting to register without a contract will not yield credentials
Carrier data coverage varies significantly by mode and region; a shipment created with a valid carrier SCAC may return no tracking events if that carrier has not connected to the project44 network
Predictive ETAs are machine-learning estimates that can change significantly with weather or port congestion events; downstream systems should treat the ETA as advisory and display a confidence range rather than an exact time
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp