Track a Nash delivery's status via webhooks and normalized delivery states
domain: docs.usenash.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Subscribe to Nash's webhooks to receive every status change (assignment, pickup, dropoff) as it happens, instead of polling the GET Order endpoint.
Expect Nash's normalized status progression for a delivery that completes successfully: CREATED, ASSIGNED_DRIVER, PICKUP_ENROUTE, PICKUP_ARRIVED, DROPOFF_ENROUTE, DROPOFF_ARRIVED, DROPOFF_COMPLETE.
Handle non-happy-path statuses (cancellations, failures) separately from the normalized happy-path sequence, since Nash unifies status reporting across multiple underlying delivery providers.
If you're also using Nash's orchestration to pick among providers, check quote.tags for autodispatch_preferred_quote when deciding which provider's quote to accept.
Use the GET Order endpoint as a fallback/reconciliation check for cases where a webhook might have been missed, rather than as your primary status source.
Ensure your webhook receiver responds quickly and idempotently, since Nash is relaying status changes that originate from several different underlying courier networks with their own timing quirks.
Known gotchas
Because Nash sits in front of multiple delivery providers, the normalized statuses are Nash's own abstraction — the timing and granularity of underlying provider events won't map 1:1 to the six-state happy path.
Nash's own docs steer real-time use cases toward webhooks rather than repeated polling — treat webhooks as primary and GET Order as a backstop, not the reverse.
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?