API keys stop working either through manual user revocation or automatic system triggers. This guide covers how key deactivation works and how inactive keys are retained for audit purposes.
Manual deactivation
You can manually revoke active API keys at any time:
Go to API keys from your personal profile or workspace administration.
Locate the token under Active keys, open the action menu, and select Deactivate.
Confirm by clicking Deactivate on the pop-up window.
💬 Please note: Manual deactivation takes effect immediately and cannot be undone. The token is instantly moved to Inactive keys.
Automatic deactivation
LingoHub automatically revokes API keys when referenced resources or access levels change:
Expiration date reached: The key passes its designated valid-through date.
Project / Stack deletion: Stack-scoped keys are automatically revoked when the associated stack/project is deleted.
Member removal: Member/User-scoped keys are automatically revoked when the user is removed from the workspace.
Workspace deletion: All workspace-associated API keys are revoked if the workspace is deleted.
Self-managed setting disabled: Self-managed keys are revoked if an Admin turns off self-managed API key creation workspace-wide.
Learn more in our guide on how to enable or disable self-managed API keys.
Need more help?
Couldn't find what you were looking for? Reach out to our team at [email protected], and we will gladly assist you.