Managing API Keys
API keys provide secure, token-based authentication for external integrations (such as MaintenanceSystemIntegration) to communicate with the OT Backup API. This page explains how to create, extend, revoke, and delete API keys from the Configuration page.
flowchart LR A[Configuration: API Keys] --> B[Create New API Key] A --> C[Extend Expiration] A --> D[Revoke API Key] A --> E[Delete API Key] B --> F[Copy Secret Key] F --> G[Configure Integration]
Before you start
- You need the matching permission for the action you want to perform.
- To configure external integrations, you must have access to the physical server or deployment environment to update their
appsettings.jsonfiles.
Actions you do not have access to are hidden from the API Keys table, row menus, and dialogs. If a button or menu item described here is missing, ask an administrator to grant the corresponding claim.
| Action | Policy | Required claim |
|---|---|---|
| Open the API Keys tab and view existing keys | EditConfiguration |
edit.configuration |
| Create a new API Key | EditConfiguration |
edit.configuration |
| Extend key expiration dates | EditConfiguration |
edit.configuration |
| Revoke an active API Key | EditConfiguration |
edit.configuration |
| Delete an API Key from the system | EditConfiguration |
edit.configuration |
Create an API Key
Open Configuration from the navigation menu and navigate to the API Keys tab.

Select Add API Key in the top-right corner of the table.

The Create New API Key dialog opens. Fill in the required fields:
| Field | Purpose |
|---|---|
| Display Name | The identifier for the key (e.g., integration.service or Maximo-Integration). This is used for audit logs and identity claims. |
| Note | Optional description of what this key is used for or who requested it. |
| Expiration Date | The date the key will stop working. Leave empty to make the key permanent (if allowed by system policy). |
- Select Create Key. OT Backup will generate the key and display a success dialog containing the Secret API Key.
CRITICAL WARNING: Copy the secret key immediately and store it securely. For security reasons (hash-based storage), OT Backup cannot show you this secret key again after you close the dialog. If you lose it, you must delete the key and create a new one.

Configure Integrations (Manual Setup)
Once you have copied the new secret API key, you must configure your external systems to use it.
- Locate the configuration file (e.g.,
appsettings.jsonorappsettings.Production.json) for your integration service (MaintenanceSystemIntegration). - Open the file in a text editor.
- Locate or add the
ApiKeyAuthenticationOptionssection and paste your copied secret key:
{
"AppSettings": {
"ApiKey": "<PASTE_YOUR_SECRET_KEY_HERE>"
}
}
- Save the file and restart the integration service. The service will now securely authenticate with OT Backup.
Extend API Key Expiration
API Keys might expire based on system policies. You can extend an active key's lifespan without needing to generate a new secret key.
On the API Keys tab, open the row's More options menu (the ⋮ icon) or click the Extend button for the respective key.
The Extend API Key dialog opens.

Choose a new date from the calendar.
Select Save Changes.
Maximum Expiration Policies
Depending on your system's security configuration (AppSettings:ApiKeyMaxExpiration), OT Backup may enforce a maximum lifespan for API keys (e.g., 1 year, 6 months, 30 days).
If a limit is configured, the calendar will prevent you from selecting dates beyond the allowed maximum, and you will see a warning indicating the maximum allowed date.
The option to make a key "Permanent" will be hidden if strict expiration policies are active.
Revoke an API Key
If you suspect an API key has been compromised, but you want to keep its historical record for audit purposes, you should Revoke it.
On the API Keys tab, open the row's More options menu and choose Revoke.

Confirm the prompt:
Are you sure you want to revoke the API key ''? This action cannot be undone and any integration using this key will immediately lose access.
Choose Revoke. The key's status will change to Revoked and all authentication attempts using this key will immediately return a
401 Unauthorizederror.
Note: A revoked key cannot be reactivated. You must create a new key to restore integration access.
Delete an API Key
Deleting an API key removes it entirely from the OT Backup database. Use this for keys created by mistake or old revoked keys that are no longer needed for auditing.
On the API Keys tab, open the row's More options menu and choose Delete.

Confirm the prompt:
Are you sure you want to delete the API key ''?
OT Backup shows API Key deleted and removes the row from the table.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Integration gets 401 Unauthorized | Key is invalid, expired, or revoked. | Check the API Keys table. If the key is expired, extend it. If revoked or deleted, create a new key and update the integration's appsettings.json. |
| Cannot select a date beyond a certain month | System enforces a maximum expiration policy. | This is expected behavior. Keys must be rotated/extended periodically according to the ApiKeyMaxExpiration configuration. (Note: If this configuration is not set, permanent keys are allowed). |
| Cannot see the secret key for an existing record | Secret keys are never stored in plain text. | If you lost the original secret key, delete the current record and create a new API Key. |
| Add API Key or Action buttons are missing | Your account lacks the needed permission. | Ask your administrator to grant the edit.configuration permission. |