Manage API keys
Choose which monitors a key can send data for and replace keys safely.
On this page
What you need
Permission to manage keys in your workspace and a safe place to store a new key.
How to do it
- Open Keys, create a key and choose its monitors or the entire workspace.
- Save the full key immediately in your integration's protected file or secret store. It is displayed only once.
- To replace it, choose Rotate and update every sender using it. Revoke a key that should no longer work.
Good to know
Rotation stops the old key immediately. A workspace-wide key also covers future monitors in that workspace; the sender must identify its target monitor.
Device keys (mbk_) send readings. Machine credentials (mbm_) manage resources according to their permissions. Remote MCP uses a separate access token.
If something goes wrong
If requests return 401 after rotation, check whether the sender still reads the old key. Never put keys in URLs, public repositories or logs.
Related guides
- CLI keys and numeric data
Manage device keys and send a numerical value with the CLI.
- Send your own monitoring data
Send your own readings over HTTPS using the IDs and keys of your monitor.
- Local and remote MCP access
Connect a compatible AI client to your monitoring with limited access.