> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usenash.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Nash API

> The Nash API is the gateway to the delivery orchestration platform. Find the right resource group, learn how to authenticate, pick an environment, and get started.

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

<CardGroup cols={2}>
  <Card title="Orders" icon="box-open" href="/api-reference/order/order">
    Create orders, compare quotes, and dispatch deliveries programmatically.
  </Card>

  <Card title="Dispatch Strategies" icon="truck-fast" href="/api-reference/dispatch-strategies/dispatch-strategy">
    Choose providers and configure how jobs (deliveries) get dispatched.
  </Card>

  <Card title="Notifications" icon="comment-dots" href="/api-reference/notifications/notifications">
    Send notifications to your customers or internal systems.
  </Card>

  <Card title="Store Locations & Zones" icon="store" href="/api-reference/store-locations/get-store-locations">
    Manage delivery origins and the geographic areas they serve.
  </Card>

  <Card title="Jobs" icon="box" href="/api-reference/job/jobs">
    Track and update a job (delivery) once it has been dispatched.
  </Card>

  <Card title="Batch Jobs" icon="boxes-stacked" href="/api-reference/batch-job/create-batch-job">
    Track and update jobs (deliveries) with multiple packages.
  </Card>

  <Card title="Providers" icon="truck" href="/api-reference/provider/get-providers">
    Get the providers available in your organization.
  </Card>

  <Card title="Routes" icon="route" href="/api-reference/route/get-route">
    Create, update, and dispatch ordered multi-stop routes.
  </Card>

  <Card title="Shifts" icon="business-time" href="/api-reference/shifts/get-all-shifts">
    Manage driver shifts.
  </Card>

  <Card title="Templates" icon="file-lines" href="/api-reference/templates/upsert-multiple-templates">
    Upsert reusable templates.
  </Card>

  <Card title="Store Catalog" icon="basket-shopping" href="/api-reference/store-catalog/pick-and-pack">
    Manage products and store inventory.
  </Card>

  <Card title="Feedback" icon="star" href="/api-reference/feedback/add-delivery-feedback">
    Submit delivery feedback.
  </Card>

  <Card title="Shipping" icon="boxes-packing" href="/api-reference/shipping/manifest-orders">
    Manifest and dispatch orders for shipping.
  </Card>

  <Card title="Fleet" icon="truck-ramp-box" href="/fleet/overview">
    The inbound surface a fleet uses to report delivery state to Nash.
  </Card>

  <Card title="Miscellaneous" icon="table-cells" href="/api-reference/miscellaneous/server-health-check">
    Server health check.
  </Card>
</CardGroup>

## 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](/reference/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.

```sh theme={"dark"}
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](/reference/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](/reference/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](/reference/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](/api-reference/using-llms-with-nash-api).

## Next steps

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/reference/authentication">
    Create an API key and authenticate your requests.
  </Card>

  <Card title="Environments" icon="server" href="/reference/environments">
    Pick the right base URL for Sandbox or Production.
  </Card>

  <Card title="Orders" icon="box-open" href="/api-reference/order/order">
    Start managing delivery operations with the Orders API.
  </Card>

  <Card title="Using LLMs with Nash API" icon="robot" href="/api-reference/using-llms-with-nash-api">
    Integrate faster with LLM-friendly documentation.
  </Card>
</CardGroup>