HTTP status: attendance matrix validation
This page documents the problem type URI returned when GET /api/v1/activities/activities/{id} /attendance-matrix/ rejects the query string (missing required parameters, invalid integers,
unknown timezone, or max_columns out of range).
Clients should branch on status, type, and structured errors[].code values (not only free-text detail).
Canonical problem type
Section titled “Canonical problem type”type: "https://docs.keja.co/troubleshooting/status-codes/activities.attendance_matrix_validation"
HTTP mapping
Section titled “HTTP mapping”| Item | Value |
|---|---|
| Status code | 422 |
| Content-Type | application/problem+json |
title (problem) | Short human label such as `Attendance matrix requires parameters`, `Invalid attendance matrix parameters`, or `Invalid timezone`. |
detail (problem) | Human explanation; do not parse for automation per RFC 9457. |
Typical issue codes (errors[].code)
Section titled “Typical issue codes (errors[].code)”-
activities.attendance_matrix.missing_query - One or more of
iana_timezone,anchor_ymd, andmax_columnswere not provided. -
activities.attendance_matrix.invalid_max_columns -
max_columnswas present but not a valid integer. -
activities.attendance_matrix.max_columns_out_of_range -
max_columnsmust be between 1 and 14. -
activities.attendance_matrix.invalid_cursor -
cursor_occurrence_idwas present but not a valid integer (optional parameter). -
activities.attendance_matrix.invalid_timezone -
iana_timezoneis not a known IANA identifier.
Each issue object should include a pointer (for example /query/max_columns) where the API supplies it.
Related
Section titled “Related”- OpenAPI:
GET /api/v1/activities/activities/{id}/attendance-matrix/(experimental stability).