Create a shipment record in project44 and poll for capacity and carrier assignment on a tendered FTL load
domain: project44.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate via OAuth 2.0 client credentials to obtain a Bearer token (see auth route).
POST to the project44 shipments endpoint with stop details (origin address, destination address, pickup date/time window), equipment type, and any attribute tags needed for routing.
Receive the shipment identifier in the response and store it; note the initial status field which will reflect the untendered or pending state.
Poll the GET shipment endpoint using the shipment ID at a reasonable interval to observe status transitions; project44 may also support event subscriptions via webhook — register a callback URL if available to receive push updates instead of polling.
When a carrier is assigned, the response will include carrier SCAC and PRO or tracking number; use these to initiate tracking.
Known gotchas
project44's data model distinguishes between shipment creation (a logistics intent) and visibility subscription (attaching tracking); some API plans require a separate call to activate tracking after shipment creation.
Stop sequence matters — project44 enforces strict ordering of stops; providing stops out of sequence or with overlapping time windows returns a validation error.
Polling intervals that are too aggressive against the shipments endpoint can exhaust rate limits; prefer webhook subscriptions for production workloads and fall back to polling only in sandbox testing.
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?