Creating and managing API keys
Create keys for scripts and agents, choose what they can do, and revoke them when they're no longer needed.
An API key lets a script, agent or other system use AssetTrove without a person signing in. You manage keys on the API keys page; you need permission to manage API keys (Owners and Admins have it).
Create a key
- Select Create key and give it a clear name, for example Lansweeper sync or Inventory agent – Amsterdam.
- Choose its roles. For a discovery agent, the Integration role is enough: it can send discovery data and read assets.
- Copy the key. It's shown only once. AssetTrove stores only a fingerprint of it, so even we can't show it again.
A key looks like itam_live_<id>_<secret>. Use it as a bearer token:
Authorization: Bearer itam_live_<id>_<secret>
Rules for keys
- A key can't be more powerful than the person creating it, and can never be an Owner.
- Roles on keys always apply organisation-wide.
- An organisation can have up to 50 active keys.
- AssetTrove shows when each key was last used.
Revoke a key
Select Revoke next to the key. It stops working immediately, on the very next request.
When the person who created a key leaves
The key keeps working, because it belongs to the organisation and not to the person, so integrations don't break when someone leaves. AssetTrove marks it as creator inactive so you can review it. Your organisation can choose to revoke such keys automatically instead.
Tip Create one key per integration. Then you can revoke one without breaking the others, and the audit log shows exactly which integration did what.