Skip to main content
Databunker Pro stores its license key in the database (the config table, under the licensekey key). You can replace it at any time on a running instance — there is no need to restart the service or redeploy. A new license is typically applied when you:
  • Move from Trial mode to a paid license.
  • Renew a license that is about to expire.
  • Increase the maximum number of records (maxrecords) your plan allows.
Only the main tenant administrator (root token, tenant id 1) can set the license key. The new key is validated before it is saved — an invalid or expired key is rejected and the existing license stays in place.

​
Before you start

To complete this guide, you’ll need:

​
Update via the API

Send the new key to the SystemSetLicenseKey endpoint. All Databunker Pro API calls use POST /v2/<Method> and authenticate with the X-Bunker-Token header. 
curl -X POST http://localhost:3000/v2/SystemSetLicenseKey \
  -H "X-Bunker-Token: YOUR-ROOT-TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"licensekey": "YOUR-NEW-LICENSE-KEY"}'
A successful response looks like this: 
{ "status": "ok", "result": "done" }
If the key is invalid or expired, the call returns an error and the current license is left unchanged: 
{ "status": "error", "message": "License key is invalid" }
You can pre-load a license at first start with the DATABUNKER_LICENSEKEY environment variable. This is only used during the initial setup; once a key is stored in the database, update it using the API call above.