Register a client application with project44 via the portal; the platform issues a client ID and client secret used for OAuth 2.0 Client Credentials authentication.
POST to the project44 token endpoint with your client ID and secret to receive a bearer access token; include it as Authorization: Bearer YOUR_TOKEN on all API requests.
Create an ocean shipment tracking record by POSTing container numbers, bill of lading numbers, or booking references to the Ocean Tracking API endpoint; specify the carrier SCAC to resolve data sources.
Retrieve the current list of shipment events by GET request on the tracking record; events follow the project44 event schema including milestone type, actual vs estimated flag, location, and timestamp.
Configure a webhook subscription on the project44 platform to receive push notifications for new milestone events; project44 delivers POSTs to your registered callback URL.
Enrich shipment data by enabling Extended Ocean mode where available; this adds predicted ETA, port congestion risk scores, and vessel AIS position data beyond standard carrier milestones.
Known gotchas
project44 uses OAuth 2.0 Client Credentials, not API keys; the token must be refreshed before expiry — build token lifecycle management into your integration layer.
Container tracking accuracy depends on carrier data feed quality; for carriers without direct API feeds, project44 falls back to web scraping or AIS data, which may lag official carrier systems by hours.
Ocean shipments with transshipment legs may show gaps between port events; do not infer cargo is lost or delayed based solely on absence of events during an expected transshipment window.
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