Authorization
Find your API key and companyId, and authenticate requests to the NextSign API.
Authorization
NextSign API requests use your API key as a bearer token and your companyId as part of the request URL.
1. Create an API Key
Create API keys from the NextSign dashboard:
- Open Dashboard → Config → API Keys
- Click Create API Key
- Enter a name such as
Backend ServiceorTest Integration - Click Generate
- Copy the key and store it securely
Your API key is shown only once. If you lose it, create a new one and revoke the old key.
2. Use the API Key as Bearer Token
Send the API key in the Authorization header:
Authorization: Bearer YOUR_API_KEYExample:
curl --location 'https://www.nextsign.dk/api/v2/{company}/cases/get' \
-H 'Authorization: Bearer YOUR_API_KEY'3. Find Your companyId
Your companyId is the company identifier used in API paths such as:
https://www.nextsign.dk/api/v2/{company}/cases/getThe easiest places to find it:
- At the top of Dashboard → Config → API Keys
- In many dashboard URLs, where it appears as the
/user/{companyId}/...path segment - In existing API requests or integration config where the company identifier is already stored
Recommended approach:
- Open Dashboard → Config → API Keys
- Copy the
companyIdshown at the top of the page - Use the URL only as a fallback if needed
Example dashboard-style URL:
https://www.nextsign.dk/user/6576e19662ec13c4faa7de7b/settingsIn this example, 6576e19662ec13c4faa7de7b is the companyId.
4. Recommended Environment Variables
NEXTSIGN_API_KEY=your_api_key_here
NEXTSIGN_COMPANY_ID=your_company_id_here
NEXTSIGN_API_URL=https://www.nextsign.dk/api5. First Authenticated Request
curl --location "https://www.nextsign.dk/api/v2/${NEXTSIGN_COMPANY_ID}/cases/get" \
-H "Authorization: Bearer ${NEXTSIGN_API_KEY}"Typical Error Responses
Missing bearer token:
{
"errors": [
{
"code": 401,
"message": "Unauthorized",
"description": "Bearer token not found"
}
]
}Invalid company id:
{
"code": 400,
"message": "Bad Request",
"description": "Invalid company id"
}Some older v2 endpoints return validation or authorization problems inside a 200 OK response with an errors array. In integrations, validate both the HTTP status code and the response body.