RecordEngine uses Bearer token authentication for all REST API requests. Every call must include your API token in the request header — unauthenticated requests are rejected with a 401 Unauthorized response.
Getting Your API Token
- Log into RecordEngine as an Admin
- Go to Settings → API
- Copy the token displayed there
Your token looks like a long random string:
Treat your API token like a password. Anyone with this token can read all documents, upload files, and modify data in your RecordEngine instance. Do not share it publicly or commit it to a code repository.
Including the Token in Requests
Add the token to the Authorization header of every API request:
Examples
Using the Token in Swagger UI
To authenticate in the Swagger UI at /api/docs:
- Click the Authorize button (🔒) at the top right of the Swagger page
- In the dialog, enter:
Bearer YOUR_TOKEN_HERE
- Click Authorize
All subsequent requests made from the Swagger UI will include your token automatically.
Regenerating Your Token
If you suspect your token has been compromised, regenerate it immediately:
- Go to Settings → API
- Click Regenerate Token
- A new token is issued instantly — copy and save it
- The old token is immediately invalidated
After regenerating, update every integration, automation scenario, and script that uses your API token before they will work again.
Webhook Authentication
When RecordEngine sends an outbound webhook POST to your URL, it includes the same Bearer token in the request header:
Your webhook receiver should validate this header to confirm the request is genuine and originated from your RecordEngine instance — not from an external source.
Verifying a Webhook in Python
Verifying a Webhook in Node.js
Store your token in an environment variable (e.g. RE_TOKEN) rather than hardcoding it in your source code. This makes it easy to rotate the token without a code change.
Authentication Errors