Keys and credentials
Every credential is shown exactly once, at the moment it’s created or rotated. InfraInbox stores only its hash; if you lose one, rotate it rather than trying to recover it.
Credential forms
Section titled “Credential forms”| Prefix | What it is | Where it goes |
|---|---|---|
iik_src_… |
A source’s ingest key: creates events for that one source only. | Authorization: Bearer iik_src_… header, on POST /v1/events and on a tool’s own webhook path. |
iik_hb_… |
A heartbeat or ping check’s ping-only token. | Either Authorization: Bearer iik_hb_…, or the token itself as the path segment of a cron-friendly ping URL. |
whsec_… |
A webhook destination’s signing secret (Standard Webhooks–compatible). | Not sent by you — InfraInbox uses it to sign the webhook-signature header of what it sends to your endpoint. |
A Gotify-style token (A and 14 more characters) |
A Gotify-compatible source’s alias token, for tools that only speak Gotify’s legacy format. | X-Gotify-Key header, Authorization: Bearer <token>, or ?token= on the query string if the source allows it. |
| An opaque token (no prefix) | A signed-in session or a paired device’s access/refresh token. You never type these in — the dashboard and the app hold them for you. | A Set-Cookie session cookie (web), or Authorization: Bearer <token> (a paired app). |
Where they live in the dashboard
Section titled “Where they live in the dashboard”- Settings › Workspace › API keys (owner/admin) — every source’s keys in one table: Source, Key, Status, Created, Last used (“never” for a key nothing has sent with). Each source links to its Connect tab and has its own New key; Revoke is the red action at the row’s end. After rotating a Proxmox source’s key, the dialog showing the new key also says where to paste it.
- A source’s own page, Connect tab — the same list, scoped to that one source.
- A destination’s panel — a webhook destination’s signing secret is created when you save and shown once then, in a dialog; a Telegram/Slack/Discord destination’s bot token or webhook URL is never shown again once saved, not even its last characters.
Shown once
Section titled “Shown once”A key or secret is displayed in full exactly once: right after you mint or rotate it. After that, only a hint (its last few characters) is shown. Copy it somewhere safe immediately — there’s no “reveal” button later.
Rotate
Section titled “Rotate”Rotating a source’s key issues a new one immediately and keeps the old one working for 24 hours, so you have time to update the sender (Proxmox, a script, a crontab entry) before the old key stops working. Use this if a key may have leaked, or you’re not sure whether it did.
Revoke
Section titled “Revoke”Revoking a key stops it working immediately, with no grace period. Use this once you’re certain a key is compromised, or a source no longer exists.
URL forms that carry a secret
Section titled “URL forms that carry a secret”As a rule, InfraInbox avoids putting secrets in URLs — they end up in browser history, shell history and access logs. There are three deliberate exceptions:
- The heartbeat ping URL,
https://infrainbox.example.com/v1/heartbeats/iik_hb_…— built specifically so acurlline in a crontab needs nothing but the URL. The server logs only the route pattern, never the actual path, so the token doesn’t end up in its own logs. - The Gotify-compatible
?token=form, only when a source explicitly enables it, for senders that only support Gotify’s query-parameter style. - A source key in a hook’s path,
https://infrainbox.example.com/hooks/generic/iik_src_…, only when a source explicitly enables it, for senders that can’t set a header. Dozzle, NetAlertX and Checkmate sources are created with it on (/hooks/netalertx/iik_src_…,/hooks/checkmate/iik_src_…).
Every other credential goes in a header.