> ## 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.

> ## Agent Instructions
> Nash exposes two MCP servers. The docs MCP server at https://docs.usenash.com/mcp searches this documentation and needs no credentials. The Nash MCP server at https://mcp.usenash.com/mcp operates an organization's deliveries and needs a Nash API key. See https://docs.usenash.com/reference/build-with-ai.
> Use the Sandbox environment (https://api.sandbox.usenash.com/v1) for anything that creates or dispatches deliveries during development.

# Authentication

> Authenticate Nash API requests with a Bearer API key and the Nash-Org-Id header.

Nash APIs use API keys for authentication and authorization. API keys are created in the Nash Portal; follow [this tutorial](/reference/generating-api-key-and-org-id) to create one and to find your Organization ID, which you will also need here.

To make an API request, you need to include your API key and optionally Organization ID in the request headers:

1. `Authorization: Bearer $NASH_API_KEY`: Set `NASH_API_KEY` to your API key. This header authenticates your request.
2. (Optional) `Nash-Org-Id: $NASH_ORG_ID`: Set `NASH_ORG_ID` to the ID of the organization you want to access. This header is required when your API key has access to multiple organizations.

If you followed the tutorial, you should already have your API key and Organization ID. With these two pieces of information, you can make a request like this:

```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"
```

<Warning>
  Your organization's API key can hold many privileges, so be sure to keep it secure. Be careful not to share the key unintentionally, since it enables direct access to the Nash API.
</Warning>

## Portal sign-in

API keys authenticate systems. People signing in to the Nash Portal are a separate matter: you can connect Portal sign-in to your own identity provider so your team uses the credentials they already have, and your MFA and offboarding policies apply. See [Single sign-on](/reference/single-sign-on). Turning it on changes nothing about your API keys.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.