error_id — the same fingerprint id used here — so an error event links straight into this report.
An error is addressed by {error}, its deterministic fingerprint (a UUID derived from the site and the exact error message; the id field returned by the endpoints below). Fingerprint resolution is range-independent — a known fingerprint always resolves, even for a range with zero matching occurrences — but a fingerprint that has never belonged to the site returns 404 Not Found, so one team can never probe another’s errors.
A site is addressed by {siteKey} (UUID or domain). All endpoints require Authorization: Bearer {token} and accept the shared range/from/to and filter query parameters described in Conventions.
List error names
data/meta/links envelope — see Conventions.
Query parameters
Filter dimensions are also accepted.
Response — each item in
data:
Status:
200 OK.
Get an error
Query parameters
Filter dimensions are also accepted. A recognized fingerprint outside the requested range/filters still returns
200 OK with occurrences/sessions at 0, not 404 — only an unknown fingerprint 404s.
Response — flat object:
Status:
200 OK (404 for an unknown fingerprint).
Error timeseries
Query parameters
Filter dimensions are also accepted.
Response — flat object:
Status:
200 OK (404 for an unknown fingerprint).
List error events
data/meta/links envelope.
Path parameters
Query parameters
Filter dimensions are also accepted.
Response — each item in
data:
Status:
200 OK (404 for an unknown fingerprint).

