All NAMETS REST API endpoints are protected by theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/Muhammadbugaje/NAMETS_Website/llms.txt
Use this file to discover all available pages before exploring further.
N8NAuthentication scheme. Every request must include a valid X-N8N-Token header, whose value must match the N8N_API_TOKEN environment variable configured on the server. Requests that omit the header or supply an incorrect token are rejected immediately — no request body or query parameters are processed.
How the token is validated
The server-side authentication class reads theX-N8N-Token header from each incoming request and performs a direct string comparison against settings.N8N_API_TOKEN. If the token is missing or does not match, a 403 Forbidden response is returned before any view logic executes.
return (None, None) means authentication succeeds without attaching a Django user object to the request. The API authenticates the caller (your integration or automation tool) rather than an individual user account.
Sending the header
IncludeX-N8N-Token in every API call:
your_api_token with the value of the N8N_API_TOKEN environment variable set on your server.
Setting the environment variable
On your server (e.g., Render), add the following environment variable:| Variable | Description |
|---|---|
N8N_API_TOKEN | The shared secret token that authenticates API requests |
Generating a secure token
Use Python’ssecrets module to generate a cryptographically strong token:
Run the following command to generate a secure 256-bit hex token suitable for production use:Copy the output and set it as
N8N_API_TOKEN in your server’s environment. Store it in a secrets manager — never commit it to version control.