Nash

# Nash ## Docs - [How Nash works](https://docs.usenash.com/reference/how-nash-works.md): A complete overview of the Nash delivery orchestration platform — the delivery lifecycle, the provider network, and the core building blocks you integrate with. - [Plan your integration](https://docs.usenash.com/reference/plan-your-integration.md): How to plan a Nash API integration: timeline, account setup, dispatch strategies, notifications, and go-live. - [API key and Org ID](https://docs.usenash.com/reference/generating-api-key-and-org-id.md): Create an API key in the Nash Portal and find the Organization ID to send with your requests. - [Authentication](https://docs.usenash.com/reference/authentication.md): Authenticate Nash API requests with a Bearer API key and the Nash-Org-Id header. - [Environments](https://docs.usenash.com/reference/environments.md): Base URLs and Portal links for the Nash Production and Sandbox environments, and how Sandbox differs from Production. - [Production testing](https://docs.usenash.com/guides/production-testing.md): How to schedule an integration testing call with Nash and get production API keys enabled. - [Orders, jobs & dispatch](https://docs.usenash.com/reference/nash-api-overview.md): The key concepts behind the Nash API: orders, jobs, quoting, and dispatch. - [Dispatch strategies](https://docs.usenash.com/reference/dispatch-strategies.md): How dispatch strategies control which providers can fulfill a job, how Nash selects one, what it can cost, when it dispatches, and how it recovers. - [Delivery status](https://docs.usenash.com/reference/delivery-status.md): The normalized delivery statuses Nash reports across all providers, including terminal statuses and the guaranteed status order. - [Delivery windows](https://docs.usenash.com/reference/delivery-windows.md): A delivery window is a bookable time slot, tied to a store location and bounded by capacity, that an order can be scheduled into. - [Routes](https://docs.usenash.com/reference/routes.md): A route is a planned, ordered sequence of stops for a vehicle or driver. Learn how to create, update, and dispatch routes — and how routes relate to route optimization. - [Zones](https://docs.usenash.com/reference/zones.md): A zone is a geographic delivery area defined by a polygon boundary or a list of cities, zip codes, states, or countries. Learn how zones model coverage, how to look up which zones cover a location, and how zones relate to store locations. - [Store locations](https://docs.usenash.com/reference/store-locations.md): A store location is a physical origin — a restaurant, warehouse, or store — that deliveries depart from. Learn how to model store locations, upsert them by your own identifier, and look up which stores cover a location. - [Store catalog](https://docs.usenash.com/reference/store-catalog.md): The store catalog combines a master product catalog and per-store inventory to power item-level fulfillment. Learn how products and inventory fit together, how Pick and Pack works, and what item-level details an order can carry. - [Webhooks](https://docs.usenash.com/reference/webhooks.md): Set up and consume Nash webhooks: event types, payload shape, signature verification, and retries. - [Shift dispatched event](https://docs.usenash.com/reference/shift-dispatched-event.md): The shift.dispatched webhook fires when orders from a delivery window (shift) are dispatched in bulk to delivery jobs. Payload structure, scenarios, and error reference. - [Workflows](https://docs.usenash.com/reference/workflows.md): Nash workflows are an automation engine that responds to delivery events with filters and actions — applying dispatch strategies, modifying orders, sending notifications, and more. - [Notifications](https://docs.usenash.com/reference/notifications.md): Nash's built-in notifications platform alerts customers and internal teams on delivery events across SMS, email, WhatsApp, Slack, and webhook — with reusable audiences, fine-grained targe […gekürzt]