Assign carrier/tracking information to a load so FourKites can track its rail movement
domain: developer.fourkites.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain FourKites API user credentials issued for your carrier/shipper account.
Authenticate using HTTP Basic Authentication (Digest authentication is also supported).
Call the Tracking Information Assignment API, submitting the load and carrier identifiers needed to attach tracking.
Reference FourKites' public GitHub sample implementations (FourKites/Tracking-Information-Assignment-API) for request/response examples in your language.
Consult the TMS Tracking Assignment integration guide in FourKites' public knowledge base for field-level mapping guidance.
Known gotchas
Basic Auth over HTTPS means credential handling matters - treat FourKites API credentials like a password, not a disposable bearer token.
The public GitHub sample code is a reference implementation, not the full authoritative spec - cross-check current parameters against developer.fourkites.com.
Give your agent this knowledge — and 15,500+ 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?