Retrieve car location message (CLM) history for one or more railcars up to 90 days back via RailSight Demand Trace
domain: public.railinc.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request Asset Tracking API access via the Railinc integration contact form.
Use the Event History Web Service to request events up to 90 days in the past for one or more railcars (XML response).
Use the Last Event Web Service to get just the most recent event, optionally filtered by load/empty status or a comma-separated list of 4-digit event codes.
Use Events in Date Range when you need a bounded window rather than the full 90-day history.
Parse the returned XML event codes against Railinc's published CLM event sighting code reference.
Known gotchas
Demand Trace responses are XML, unlike the JSON responses from the newer RailSight Movement/Fleet services - don't assume one response format across all RailSight APIs.
90 days is a hard lookback limit for Event History; older history requires a different Railinc product.
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?