Authenticate against the project44 OAuth 2.0 token endpoint using your client credentials to obtain a bearer token; regional base URLs differ (e.g., na12.api.project44.com for North America, eu12.api.project44.com for Europe).
Register your webhook callback URL by POST-ing to /api/v4/webhooks with your endpoint URL and the event types you wish to receive; store the returned webhook configuration ID.
Create or import a shipment via the appropriate mode-specific endpoint (Parcel, LTL, Truckload, Ocean) supplying carrier SCAC or carrier ID, PRO/tracking number, and origin/destination data.
project44 begins pushing status updates to your registered webhook as events occur; each push uses the same payload format as GET /api/v4/shipments/{shipmentId}/tracking/history.
Note the tenant limit of 50 push configurations — if you need more, either use broad filter criteria per webhook or contact project44 to discuss limit increases.
For parcel mode, use the dedicated parcel webhook endpoint at /api/v4/parcel/webhook/endpoint for registration, which has a slightly different configuration schema than the general webhook endpoint.
Known gotchas
project44 routes webhooks to regional endpoints — a webhook registered on the NA endpoint will not receive events for shipments tracked on the EU endpoint; match webhook registration to the regional base URL used for shipment creation.
The 50-push-configuration-per-tenant cap is a hard limit; exceeding it silently drops new registrations — audit and prune stale webhook configs regularly.
project44's carrier coverage varies by mode and region; always check the carrier capability matrix for the specific SCAC and service type before committing to a tracking integration, as unsupported carriers return no events rather than an error.
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