Skip to content
my-iris

Developers / API REST · JSON · EU edge

One REST call, one human reached

Post an alert. my-iris takes care of the rest: the push to the my-iris app, the voice call when a push goes unanswered, escalation down the list, and proof. No SDK required to start — just a key and a POST.

Talk to usHow escalation works
POST /api/v1/alertsEU · edge
curl -X POST https://api.my-iris.io/api/v1/alerts \
  -H "X-API-Key: $MY_IRIS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "phase": "Start",
    "alertMsg": "Freezer #3 is +2.1C over limit",
    "customer": "lab-oncall",
    "service": "APP1"
  }'

# customer = your receiver group KEY
# service = APP1 (push to the my-iris app, then a voice call) or IVR1 (voice call first)
# Same alertMsg while it is still active → 409, never a second escalation.
# Clear it:  {"phase": "Stop", "alertMsg": "Freezer #3 is +2.1C over limit"}
Example endpoint. Create your Alert API key in the console: Configuration → API keys.

Built for integration

Terse, predictable, EU-native

JSON in, JSON out. Honest defaults. The kind of API you wire up once and forget.

  • API-key auth

    X-API-Key header, one or more keys per workspace. Create and rotate them in the console under Configuration → API keys.

  • Idempotent ingestion

    Safe retries — repeating an alert that is still active (same alertMsg) answers 409 and never double-fires.

  • Low-latency EU edge

    Ingestion runs on Cloudflare’s EU edge for low-latency dispatch.

  • Acknowledge and skip, handled

    Acknowledge or skip in the my-iris app, or 1 or 2 on the voice call, is recorded against the alert and shown by the status endpoint, the console and the audit log.

Core endpoints

A small, stable surface — ingest alerts, check status, and configure your groups.

  • POST/api/v1/alertsIngest an alert and start the escalation.
  • GET/api/v1/alerts/:name/statusCheck an alert’s current escalation status.
  • GET / PUT/api/v1/config/*Manage groups, recipients, number mapping and languages.

No API call? Trigger by email

If your monitoring tool can only send an email, that's enough — no integration required.

  1. 1Create an email trigger for an alert group in the dashboard.
  2. 2my-iris issues a unique, secret address — e.g. alerts-lab@my-iris.io.
  3. 3Point your tool’s outbound email at that address. Any mail it sends starts an alert on the same escalation engine, with the same acknowledge and skip, end report and audit trail as the REST path.
inbound · alert trigger
To: alerts-lab@my-iris.io
From: monitoring@yourtool.example
Subject: Freezer #3 excursion
→ escalation started
Optional sender-IP allowlist, per-webhook rate limiting. Mail that doesn't match a live trigger address is silently ignored — never bounced, never forwarded.

Wire up your first alert

Talk to us to open your workspace. Then create an API key in the console and POST your first alert.

Talk to usYour first alert