CLI keys and numeric data
Manage device keys and send a numerical value with the CLI.
On this page
What you need
A configured identity with keys:write and access to the monitor.
How to do it
- Create a key with key claim for your monitor. Export it to a private file only when a separate sender needs it.
- Use metric send with the monitor, series name, value and actual measurement time.
- Use key rotate --yes to replace the key or key revoke --yes to stop it. Update external senders after rotation.
Good to know
The CLI keeps keys in private files rather than printing their full values in status output. A device key sends data; it does not manage your account. Replace demo timestamps in the example with the current measurement time.
metribeacon key claim --monitor-id MONITOR_UUID --json
metribeacon key export --monitor-id MONITOR_UUID --output "$HOME/device.key"
metribeacon metric send --monitor-id MONITOR_UUID --name temperature \
--value 21.5 --at 2026-09-30T12:00:00Z --idempotency-key POINT_UUID --jsonIf something goes wrong
If a sender stops after rotation, check its exported key file. Retry the same prepared key operation after a lost response rather than generating another key.
Related guides
- Manage API keys
Choose which monitors a key can send data for and replace keys safely.
- Send your own monitoring data
Send your own readings over HTTPS using the IDs and keys of your monitor.
- Complete command reference
Find the right command and use structured output for automation.