NextSign API
Getting Started

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:

  1. Open Dashboard → Config → API Keys
  2. Click Create API Key
  3. Enter a name such as Backend Service or Test Integration
  4. Click Generate
  5. 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_KEY

Example:

cURL
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/get

The 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:

  1. Open Dashboard → Config → API Keys
  2. Copy the companyId shown at the top of the page
  3. Use the URL only as a fallback if needed

Example dashboard-style URL:

https://www.nextsign.dk/user/6576e19662ec13c4faa7de7b/settings

In this example, 6576e19662ec13c4faa7de7b is the companyId.

.env
NEXTSIGN_API_KEY=your_api_key_here
NEXTSIGN_COMPANY_ID=your_company_id_here
NEXTSIGN_API_URL=https://www.nextsign.dk/api

5. First Authenticated Request

cURL
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:

Unauthorized
{
  "errors": [
    {
      "code": 401,
      "message": "Unauthorized",
      "description": "Bearer token not found"
    }
  ]
}

Invalid company id:

Bad Request
{
  "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.