Retrieve holiday and restricted-day data for a date range
GET /task/v1/calendar/holidays
Operation id: getHolidayInformation
Description
Retrieves holiday and restricted-day information for the authenticated user's domain over an inclusive date range. Corresponds to legacy: POST /service/rtm/getHolidayInformation.
Always-injected from session: domainId is resolved from the validated session. Clients do not send domainId or authToken as query/form fields.
Date format: MM/dd/yyyy (same as the legacy form body and GET /mywork/v1/app-config?config_type=holidays).
An empty range (no holidays in the window) is a successful result — {status: OK, holiday_data: {}} — not E404.
Response Fields — holiday_data
| Field | Type | Description |
|---|---|---|
holidays[] | Array | Holiday entries. Each: date (MM/dd/yyyy), reason |
restricted_days[] | Array | Restricted / blackout days. Each: date (MM/dd/yyyy), reason |
Error Scenarios
| Scenario | HTTP | Error Code | Message |
|---|---|---|---|
Missing X-reflexis-csrf-token-X header | 400 | E112 | X-reflexis-csrf-token-X header is mandatory |
| Invalid or expired token | 401 | E204 | Invalid or expired token |
Missing start_date or end_date | 400 | E132 | start_date and end_date are required for holidays |
| Unexpected server-side error | 500 | E302 | Internal server error |
Error Codes Reference
| Code | Description |
|---|---|
E132 | start_date and end_date are required for holidays |
E112 | X-reflexis-csrf-token-X header is mandatory |
E204 | Invalid or expired token |
E302 | Internal server error |
Tags: MyWorkCalendar
Parameters
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
end_date | string | Yes | Required (→ E132 if missing, together with start_date). Range end date. Format: MM/dd/yyyy. |
start_date | string | Yes | Required (→ E132 if missing, together with end_date). Range start date. Format: MM/dd/yyyy. |
Security
- AuthTokenHeader (apiKey)
- Session authentication token validated server-side against the user session store.
Responses
200 — Success — {status: OK, holiday_data: {holidays[], restricted_days[]}}.
Empty range returns {status: OK, holiday_data: {}}.
Content type: application/json
400 — E132 — start_date and end_date are required for holidays.
Content type: application/json
401 — Invalid or expired X-reflexis-csrf-token-X token (HTTP 401)
Content type: application/json
500 — Unexpected server-side error
Content type: application/json
Response models
200 — Success — {status: OK, holiday_data: {holidays[], restricted_days[]}}.
Empty range returns {status: OK, holiday_data: {}}.
Content type: application/json
Schema
JSON object (structure varies by endpoint).
{
"type": "object",
"description": "JSON object (structure varies by endpoint)."
}
Example:
{
"status": "OK",
"holiday_data": {
"holidays": [
{
"date": "07/04/2026",
"reason": "Independence Day"
},
{
"date": "12/25/2026",
"reason": "Christmas"
}
],
"restricted_days": [
{
"date": "11/28/2026",
"reason": "BlackOut"
}
]
}
}
400 — E132 — start_date and end_date are required for holidays.
Content type: application/json
Schema
| Property | Type | Required | Description |
|---|---|---|---|
status | string | Yes | Always "ER" for error responses |
errorCode | string | Yes | Application-level error code (e.g. E204, E112, E302) |
response | string | Yes | Human-readable error message |
{
"type": "object",
"example": {
"status": "ER",
"errorCode": "E204",
"response": "Invalid or expired token"
},
"required": [
"status",
"errorCode",
"response"
],
"properties": {
"status": {
"type": "string",
"description": "Always \"ER\" for error responses",
"enum": [
"ER"
]
},
"errorCode": {
"type": "string",
"description": "Application-level error code (e.g. E204, E112, E302)"
},
"response": {
"type": "string",
"description": "Human-readable error message"
}
}
}
Example:
{
"status": "ER",
"error_code": "E132",
"response": "start_date and end_date are required for holidays"
}
401 — Invalid or expired X-reflexis-csrf-token-X token (HTTP 401)
Content type: application/json
Schema
| Property | Type | Required | Description |
|---|---|---|---|
status | string | Yes | Always "ER" for error responses |
errorCode | string | Yes | Application-level error code (e.g. E204, E112, E302) |
response | string | Yes | Human-readable error message |
{
"type": "object",
"example": {
"status": "ER",
"errorCode": "E204",
"response": "Invalid or expired token"
},
"required": [
"status",
"errorCode",
"response"
],
"properties": {
"status": {
"type": "string",
"description": "Always \"ER\" for error responses",
"enum": [
"ER"
]
},
"errorCode": {
"type": "string",
"description": "Application-level error code (e.g. E204, E112, E302)"
},
"response": {
"type": "string",
"description": "Human-readable error message"
}
}
}
Example:
{
"status": "ER",
"errorCode": "E204",
"response": "Invalid or expired token"
}
500 — Unexpected server-side error
Content type: application/json
Schema
| Property | Type | Required | Description |
|---|---|---|---|
status | string | Yes | Always "ER" for error responses |
errorCode | string | Yes | Application-level error code (e.g. E204, E112, E302) |
response | string | Yes | Human-readable error message |
{
"type": "object",
"example": {
"status": "ER",
"errorCode": "E204",
"response": "Invalid or expired token"
},
"required": [
"status",
"errorCode",
"response"
],
"properties": {
"status": {
"type": "string",
"description": "Always \"ER\" for error responses",
"enum": [
"ER"
]
},
"errorCode": {
"type": "string",
"description": "Application-level error code (e.g. E204, E112, E302)"
},
"response": {
"type": "string",
"description": "Human-readable error message"
}
}
}
Example:
{
"status": "ER",
"errorCode": "E302",
"response": "Internal server error"
}