TunnelNet Alerting — API docs

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.

On this page

Quickstart

  1. Subscribe to TunnelNet Alerting from your dashboard (Alerting section). The current price, and whether new orders are open, are on the pricing page.
  2. Verify a destination (a phone number, by voice call, and/or an email) during onboarding.
  3. Create an API key in the Alerting section and send:
curl -X POST https://tunnelnet.io/v1/alerts \
  -H "Authorization: Bearer $TNAL_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"disk full on db1"}'

Authentication

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.

SMS is pending 10DLC registration. US carriers require a registered campaign; ours is in review. SMS alerts queue and send the moment it clears. Email and API alerts work today.

Endpoints

Method & pathWhat it does
POST /v1/alertsSubmit 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.

Limits

Errors

StatusMeaning
401Missing or unknown API key.
402TunnelNet Alerting is not active on this account.
409No verified destination yet — add one before creating a key.

All docs · Dashboard · Mail · Alerting · Support: support@tunnelnet.com