Delivered

Integration · Nash

Nash delivery API integration for restaurant groups

Send your own delivery orders to courier networks through one API: quotes, dispatch rules, live tracking and proof of delivery. We built and tested a Nash integration for a restaurant group with 16 brands, and we run it after launch.

Takes two minutes. An engineer reads it, and Max replies within 1 business day.

API
REST, webhooks via Svix
Access
Self-serve keys, free sandbox
Limit
20 requests a second per org
Regions
US and Australia

DeliveredDeliverect and Nash connectors for a 16-brand restaurant group in four countries (launching), built, tested and working.

In short

A Nash API integration connects your ordering app or order management system to courier networks through one last mile delivery API. Your system sends the order and pickup details, Nash returns quotes, dispatches a driver by your rules and pushes status, courier location and proof of delivery back by webhook. Keys are self-serve and the sandbox is free; Nash support turns on production. Nash estimates two to four weeks for a full integration. dev.family built and tested one for a 16-brand restaurant group.

What data moves

What a Nash integration moves

Read means we can get it from Nash. Write means we can send it to Nash.

ObjectReadWriteWhat the API supports
Delivery quotesYesYesQuotes from several providers for one order; dispatch strategies pick the winner
Delivery jobsYesYesCreate, update and track jobs, batch jobs and multi-stop routes
Status and courier locationYesNoWebhooks for every status change; courier location every one to two minutes, or every 20 seconds in immediate mode
Proof of deliveryYesNoDelivered by webhook with the final status
Stores and zonesYesYesStore locations, delivery zones, store catalog and inventory
Menus, POS orders, paymentsNoNoNot part of the Nash API: they go through your POS or ordering integration

Common setups

Where Nash sits in a restaurant stack

  • Own app, many couriers

    Your appNashDoorDash Drive

    Your app sends the order once; Nash picks a courier network and reports back.

  • Orders through middleware

    DeliverectYour order systemNash

    Orders reach the kitchen through Deliverect or the POS; delivery jobs go to Nash.

  • Fallback across networks

    NashUber EatsOwn drivers

    If one network can't find a driver, the job moves to the next one by your rules.

API access

How Nash API access works

Nash access is self-serve. You generate API keys and an organization ID in the Nash portal and build against a sandbox that simulates fleets, including fast and failing ones, at no cost. Nash support enables production, and production deliveries are billed.

For a restaurant group, the Nash organization and the courier contracts stay yours. We build the connector under your organization and test it on the sandbox before any real driver is booked.

Docs docs.usenash.com · weekly release notes, latest October 26, 2026 · checked November 9, 2026

What we need from you

  • Your Nash organization and API keys
  • Pickup locations and delivery zones per store
  • Your dispatch rules: price, time, fallback
  • Who signs off on go-live

Getting access:

keys right away; production after Nash support switches it on.

Not sure what your contract allows? Send us the systems and the data you need. We'll tell you which access route fits and what the connector involves.

Get a scope estimate

Platform limits

Where Nash integrations break

  • Rate limits per organization. Nash allows 20 requests a second per organization, 10 for the catalog and 3 a second for custom events on one order. Bulk updates across many stores need queuing and backoff.

  • Webhooks retry, then stop. Nash retries a webhook eight times over about 27.5 hours, then you replay it from the portal. A long outage on your side leaves stale statuses in your app.

  • Two regions only. The API runs in US and Australian regions. Markets outside them need a different courier setup.

  • Delivery only. Menus, POS orders and payments live elsewhere, so the order ID has to match across your app, POS and Nash.

  • Weekly releases. Nash ships changes weekly and has no published deprecation policy, so someone has to read the release notes.

Run

Who fixes it when the platform changes its API

  • Monitoring

    We check the connector against the live API every day and log every failed call.

  • Versions

    We track the platform's changelog and move the connector to a new version before the old one is retired.

  • Alerts

    Lost or stuck orders page the on-call engineer, who fixes them under the SLA.

  • App
  • Website
One ordering backend for every brand16 brands in four countries
  • Deliverect → kitchen
  • Nash → courier

Experience · a 16-brand restaurant group in four countries (launching)

Nash and Deliverect for a 16-brand restaurant group

The group is launching its own ordering and delivery across its brands in Saudi Arabia, Kuwait, the UK and the US. We built the app and website, the back office for all brands and the Nash and Deliverect connectors. Both connectors are built, tested and working. The full case study comes after launch.

Questions

Didn't find your answer? Ask on the call.

  • Nash is a delivery orchestration platform, now at nash.ai. Its REST API takes an order from your app, gets quotes from courier networks, dispatches a driver by your rules and sends status, courier location and proof of delivery back by webhook.

  • A last mile delivery API lets your ordering system book a courier for the trip from store to guest and get status back. DoorDash Drive and Uber Direct each offer one for their own couriers. Nash sits one level up: a single integration gets quotes from the providers connected to your Nash organization and dispatches each job by your rules, so you don't build a separate connection for every network.

  • Create API keys in the Nash portal and build against the free sandbox, which simulates fleets. Nash support switches on production when you're ready, and production deliveries are billed.

  • Nash estimates two to four weeks for a full integration: a day or two of setup and planning, one to three weeks of build and testing, and a day or two to go live. Your order flow, store setup and dispatch rules decide where in that range you land.

  • No. Nash moves deliveries, not menus or payments. Orders still reach the kitchen through your POS integration or a middleware such as Deliverect, and Nash takes over when the order needs a driver.

  • Nash runs its API in US and Australian regions. Check courier coverage for each market before you plan a launch outside them.

  • Integrate one courier network directly if one is enough. Use Nash when you want several networks, fallback when a driver isn't found, or dispatch rules per store and brand, without building each courier connection yourself.

Get a scope estimate for your Nash integration

Tell us where orders come from, which stores deliver and which courier networks you use. An engineer will reply with what's possible and how long it takes.

DeliveredNash and Deliverect connectors for a 16-brand restaurant group in four countries (launching)

a call with an engineer, then a fixed-price Integration Build. If the connector is part of a bigger change across brands, we start with a 2–3 week Assessment. How we work

Software vendor?We build connectors for food-tech products too, under your brand or ours. Restaurant API for software vendors

Max will reply within 1 business day with what's possible, what access we need and a rough timeline.

Who are you