Calls & approvals
Audit trail for buzzer calls and approve/deny decisions.
Overview
Each buzzer session materializes as a Call with nested Approval rows when residents respond.
Admin API
| Method | Path | Description |
|---|---|---|
GET | /api/admin/calls | Filterable call history |
Typical query parameters include date range, property, unit, or user — see handler implementation for the authoritative filter set.
Call fields (important)
| Field | Meaning |
|---|---|
startedAt | When the voice session began (not createdAt) |
durationSec | Length in seconds (integer) |
finalState | completed, no-answer, busy, failed, timeout |
Approvals
| Field | Meaning |
|---|---|
action | approve or deny — use these exact literals |
Multiple approvals may exist if several residents are notified; business rules determine which action wins for door release.
Analytics
Derived metrics (SLAs, answer rates) surface under /api/admin/analytics/* and /api/admin/stats — pair with calls for deep dives.