---
title: "List access control events"
method: GET
path: "/v1/access-control/events"
tags: ["events"]
---

# List access control events

`GET /v1/access-control/events`

Returns events emitted by access control devices: card scans
(`card_reader_event`), grant/deny decisions (`access_control_event`),
REX presses (`rex_event`), door-held-open alarms (`door_held_open_event`),
battery alerts, and so on. Use the filters to narrow down by door,
cardholder, event type, or time window. Pagination uses the same
`page` + `limit` + `has_more` shape as every other developer-API list
endpoint.

The per-event `details` object carries event-type-specific data
(card_id, access_decision_reason, etc.). Treat it defensively: new
keys may appear in future event types.

## Query parameters

- `start_time` string, date-time
- `end_time` string, date-time
- `door_ids` integer[]
- `cardholder_ids` integer[]
- `event_types` string[]
- `page` integer
- `limit` integer

## Response `200`

Successful Response

- EventList
  - `results` Event[], required
    - `id` integer, required — Stable identifier for the event.
    - `timestamp` string, date-time, required — RFC3339 timestamp (UTC) at which the device emitted the event.
    - `event_type` string, required — Event type as emitted by the controller. See the `event_types` query param on the list endpoint for the current enumeration.
    - `door` EventDoor
      - `id` integer, required
      - `name` string, required
      - `location_id` integer, nullable
    - `details` object, required — Event-type-specific payload (card_id, access_decision_reason, dpi_state, etc.). The set of keys depends on `event_type` and may expand over time — clients should ignore unknown keys. `card_id` and `pin` are credential identifiers and are only present when the API key's creator holds an admin role.
  - `has_more` boolean, required — True if a further page beyond `page` exists.

## Other responses

- `400` — Invalid filter values
- `401` — Missing or invalid API key
- `403` — API key lacks the required scope

---

[API](https://skmtc.dev/coram/apis/coram-api.md) · [All operations](https://skmtc.dev/coram/apis/coram-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/coram/coram-api/revisions/2842f226f93b/schema)