Alerts

Device alerts are e-bon's real-time signal that a fiscal device needs attention. They tell you when a printer is out of paper, when a cover is open, when a Z report is overdue, when fiscal memory is filling up, and when a device has dropped offline for too long.

Alerts are derived deterministically from device state on every read. They are not stored as individual records, and they have no separate lifecycle in the database — every time the Portal or the API computes alerts, it reads the current device status flags, the most recent successful Z report, the device's lastSeen timestamp, and its live WebSocket connection state, and produces the list from scratch. As soon as the underlying condition clears (paper reloaded, cover closed, Z report submitted, device reconnects), the alert simply stops appearing on the next read.

The five alert types

There are exactly five alert types — no more, no less. Each one carries one of three severities: warning, error or info.

Paper low — paper_low

• Severity: warning
• Trigger: the device reports either paperEnd or paperNearEnd in its status flags.
• Message: Paper is running low
• What to do: load a new paper roll on the AMEF before it runs out mid-receipt.

Cover open — cover_open

• Severity: error
• Trigger: the device reports coverOpen in its status flags.
• Message: Cover is open
• What to do: close the printer cover. The device cannot print receipts while the cover is open.

Fiscal memory almost full — fiscal_memory_almost_full

• Severity: warning
• Trigger: the device reports fiscalMemoryAlmostFull in its status flags.
• Message: Fiscal memory is almost full
• What to do: plan an authorised service intervention to swap the fiscal memory module before it fills completely. Once full, the AMEF will refuse to issue new receipts until serviced.

Z report overdue — z_report_overdue

• Severity: warning
• Trigger: more than 24 hours have passed since the last successful Z report — or no Z report has ever been submitted from this device.
• Message: Z report not submitted in over 24 hours
• What to do: submit a Z report for the device — from the e-bon app on the device, or from the Portal's fiscal operations flow.

Disconnected — disconnected

• Severity: error
• Trigger: the device has been offline for more than 1 hour — no live connection to the e-bon backend and no recent activity.
• Message: Device disconnected for over 1 hour
• What to do: check power, network and the on-site Android controller running the e-bon app. The alert clears automatically once the device reconnects.

Where you see alerts in the Portal

Who gets notified

Alerts that fire on a device also drive email notifications to the recipients you have configured for your organisation. Recipients subscribe per category (alerts, reports, billing, events) and receive only the categories they have opted into. The recipient list and category subscriptions are managed on the dedicated Notifications page — that page is the single source of truth for who gets what.

The API

Programmatic access to alerts is exposed through a single batch endpoint scoped to the organisation.

GET /api/v1/devices/alerts

Returns derived alerts for every device in the calling organisation, keyed by device id.

• Auth: API key with the devices:read scope (or a Portal JWT).
• Query parameters:
  • severity (optional) — one of warning, error, info. When provided, only alerts of that severity are returned, and devices with no matching alerts are omitted from the response.

Request

curl -H "Authorization: Bearer $EBON_API_KEY" \
  "https://api.e-bon.ro/api/v1/devices/alerts?severity=error"

Response shape

{
  "alerts": {
    "device-abc123": [
      {
        "type": "cover_open",
        "severity": "error",
        "message": "Cover is open",
        "deviceId": "device-abc123",
        "deviceName": "POS-01 — Bucharest",
        "detectedAt": "2026-04-25T08:42:11.503Z"
      }
    ],
    "device-xyz789": [
      {
        "type": "disconnected",
        "severity": "error",
        "message": "Device disconnected for over 1 hour",
        "deviceId": "device-xyz789",
        "deviceName": "POS-02 — Cluj",
        "detectedAt": "2026-04-25T08:42:11.503Z"
      }
    ]
  }
}

The full enum values for type are paper_low, cover_open, fiscal_memory_almost_full, z_report_overdue, disconnected. The full enum values for severity are warning, error, info.

For the broader devices API surface (list, get, status, commands) see API → Devices. For the typed SDK wrappers around the same endpoint see SDK → Devices.

Where to next

• Devices — the device list and Device Detail page where alerts surface in the UI.
• Notifications — configure the email recipients and per-category subscriptions that drive alert emails.
• API → Devices — the broader devices REST surface.
• SDK → Devices — typed client methods for getAllAlerts and the rest of the devices API.