Skip to main content

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 APIs use API keys for authentication and authorization. API keys can be created in Nash’s portal, follow this tutorial to learn how. Also follow the part on how to get the Organization ID, this will be important here.
If your API key has access to multiple Nash Organizations, you must include the Nash-Org-Id header in your request to indicate which Org the request is accessing
To make an API request, you need to include your API Key and optionally Organization ID in the request headers:
  1. Authorization: Bearer <API KEY>: Replace <API KEY> with your actual API key. This header authenticates your request.
  2. (OPTIONAL) Nash-Org-Id: <ORG ID>: Replace <ORG ID> with the ID of the organization you want to access. This header is required because API keys can be scoped 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:

​
API Key Authentication

curl --request GET \
  --url https://api.sandbox.usenash.com/v1/jobs \
  --header 'Authorization: Bearer <API KEY>' \
  --header 'Nash-Org-Id: <ORG ID>' \
  # ... request body, etc
🔒 Secure your API Key! Your organization’s API key can hold many privileges so be sure to keep it secure. Be careful to not share the key unintentionally, since it enables direct access to the Nash API.