Skip to main content
The Nash API is the gateway to our delivery orchestration platform. This page is the on-ramp: find the resource group you need, then learn how to authenticate, which environment to target, and the rate limits that apply.

​
Available APIs

Orders

Create orders, compare quotes, and dispatch deliveries programmatically.

Dispatch Strategies

Choose providers and configure how jobs (deliveries) get dispatched.

Notifications

Send notifications to your customers or internal systems.

Store Locations & Zones

Manage delivery origins and the geographic areas they serve.

Jobs

Track and update a job (delivery) once it has been dispatched.

Batch Jobs

Track and update jobs (deliveries) with multiple packages.

Providers

Get the providers available in your organization.

Routes

Create, update, and dispatch ordered multi-stop routes.

Shifts

Manage driver shifts.

Templates

Upsert reusable templates.

Store Catalog

Manage products and store inventory.

Feedback

Submit delivery feedback.

Shipping

Manifest and dispatch orders for shipping.

Fleet

The inbound surface a fleet uses to report delivery state to Nash.

Miscellaneous

Server health check.

​
Conventions

The API follows RESTful conventions and uses JSON for both requests and responses. Set the Content-Type header to application/json on requests that carry a payload. All requests are strictly HTTPS. Every Nash API response includes a request ID, whether the request succeeded or failed (see Errors). Include it when contacting support about a specific API call — it’s the fastest way for us to find your request.

​
Authentication

Nash APIs use API keys. Send your key as a Bearer token in the Authorization header. If your key has access to more than one Nash organization, also send the Nash-Org-Id header to indicate which org the request is for. 
curl --request GET \
  --url https://api.sandbox.usenash.com/v1/jobs \
  --header "Authorization: Bearer $NASH_API_KEY" \
  --header "Nash-Org-Id: $NASH_ORG_ID"
See Authentication for full details, including how to create an API key and find your organization ID.

​
Environments

Nash provides separate Production and Sandbox environments, each with US and AU endpoints. Sandbox is a free, fully-featured environment for testing your integration without dispatching to real drivers. For the full list of base URLs and Portal links, see Environments.

​
Rate limits

Each organization is limited to 20 requests per second across all Nash API endpoints. Requests beyond the limit receive an HTTP 429 response, so build in a backoff strategy. See Rate limits & throttling for guidance.

​
Using LLMs

If you’re integrating with the help of an LLM, Nash publishes documentation in LLM-friendly formats and a few best practices for sharing context safely. See Using LLMs with Nash API.

​
Next steps

Authentication

Create an API key and authenticate your requests.

Environments

Pick the right base URL for Sandbox or Production.

Orders

Start managing delivery operations with the Orders API.

Using LLMs with Nash API

Integrate faster with LLM-friendly documentation.