Send an alert by email or one API call and it reaches a person. Hard daily spend cap, verified destinations only, and every refusal written down as a row you can read.
curl -X POST https://tunnelnet.io/v1/alerts \
-H "Authorization: Bearer $TNAL_KEY" \
-H "Content-Type: application/json" \
-d '{"body":"disk full on db1"}'
The Alerting API is authenticated with an API key in the Authorization header:
Authorization: Bearer tnal_xxxxxxxxxxxx
Keys start with tnal_ and belong to a verified sender. Create, rotate and revoke them in
the Alerting section — you must have a verified destination first, because a key texts or emails
exactly one destination, yours, and nothing else.
| Method & path | What it does |
|---|---|
POST /v1/alerts | Submit one alert (body). Reaches your verified destination. |
Managing destinations, the email-in address and the alert log from the dashboard is being built; for now destinations are set up during onboarding. Key management is live in the Alerting section.
| Status | Meaning |
|---|---|
401 | Missing or unknown API key. |
402 | TunnelNet Alerting is not active on this account. |
409 | No verified destination yet — add one before creating a key. |