What's new 
One of our internal apps suddenly stopped working, and it looks like the Hexnode API key it was using may have changed. Is there a way to check who generated a new API key or revoked the old one?
92 Views
Replies (3)
Marked SolutionPending Review
Hexnode Expert
1 month ago
Sep 09, 2026
Marked SolutionPending Review
Yes. You can verify API key-related changes from the Audit History in the Hexnode UEM portal.
Go to Reports > Built-in Reports > Audit > Integration events > Hexnode API. Look for audit events such as:
- API Key Generated
- Api Key Revoked
These entries include the technician associated with the action, so you can identify who generated or revoked the API key.
If the API key was reset, integrations or applications using the previous key will stop authenticating until they are updated with the current API key. Accidental use of the Reset option can therefore cause connected systems to fail if the stored key is not updated afterward.
Regards,
Simon Scott
Hexnode UEM
Marked SolutionPending Review
Participant
1 month ago
Sep 09, 2026
Marked SolutionPending Review
Could pressing Reset have created the new key even if the technician didn’t think of it as “generating” one?
Marked SolutionPending Review
Hexnode Expert
1 month ago
Sep 09, 2026
Marked SolutionPending Review
Yes. Using Reset regenerates the API key. From an audit and integration perspective, that effectively creates a new key and invalidates the old one.
To prevent accidental disruption, it is a good idea to review technician permissions and limit access to the Admin tab only to users who need it, as that is where the API key is managed. Any external application using the API should also be updated immediately after a reset with the newly generated key.
Save