Query historical temperature sensor events for a cold-chain shipment from an EPCIS 2.0 repository
domain: gs1.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the EPC (electronic product/logistics unit identifier) or business step you want temperature history for
Call the repository's GET /events query endpoint with filters such as EPC, event time range, or eventType, per the GS1 EPCIS 2.0 REST bindings
Parse returned events for their sensorElementList, pulling sensorReport.value/type/uom from each reading
Aggregate sensorReport values across the returned events to reconstruct a temperature time series for the shipment
Cross-reference bizStep/disposition on each event to correlate temperature readings with specific handoffs, e.g., loading, in-transit, receiving
Known gotchas
Query capabilities and available filters can differ between EPCIS repository implementations - test against your actual repository (e.g., OpenEPCIS) rather than assuming full spec coverage
Large sensor-heavy event histories can be expensive to query - use time-bounded and EPC-scoped queries rather than open-ended pulls
Repositories may paginate large result sets differently - confirm your vendor's pagination mechanism before assuming one response contains everything
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?