> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/developers/api-documentation/service/list-the-non-working-days-of-a-year.md).

# List the non-working days of a year

List the tenant's non-working days for one year — the holiday calendar the business-day math runs on. Both the public holidays Flow put there and the closure days the tenant added itself are returned, active and deactivated alike, so the whole year can be shown and edited from one list. countryCode tells the two apart: a day carrying one came out of that country's public holidays, and a day with an empty countryCode is the tenant's own. Reading a year is what seeds it. The first read of a year the tenant has no rows for generates that year's public holidays from Flow's own holiday computation, for each country the tenant's stores are in, and stores them as rows before answering. Later reads of the same year return those rows as they now stand, edits included: the generation happens once and never overwrites what the tenant has since done to the year. The calendar feeds two things and nothing else: intake skips its days when it prefills a service order's readyAtEstimate from the expected turnaround, and avgWorkOpenDays on the service order statistics leaves them out. It closes no store, blocks no work and stops no message from going out. A day only counts as non-working while it is active. A public holiday the tenant's stores work through is deactivated rather than deleted — a day carrying a countryCode can be renamed and deactivated but never deleted — and stops counting from then on. Reading it asks for any service permission — SERVICE\_ORDER or SERVICE\_STORE\_CONFIG at the tenant, at an organization or at any one store, or SERVICE\_CONFIG, which is held at the tenant only — because whoever configures the holiday calendar reads it. A tenant-wide ADMIN grant counts as every permission. A caller holding none of them, a user with no role assignments included, is refused with a 403.

Required permissions: SERVICE\_ORDER, SERVICE\_STORE\_CONFIG, SERVICE\_CONFIG

```json
{"openapi":"3.0.2","info":{"title":"Flow Retail API version 2","version":"2.0.0"},"tags":[{"name":"Service","description":"Service"}],"servers":[{"description":"Flow Retail Production","url":"https://api.flowretail.com/v2"},{"description":"Flow Retail Stage","url":"https://api.stage.flowretail.com/v2"}],"security":[{"accessToken":[]},{"authToken":[]},{"integrationToken":[]}],"components":{"securitySchemes":{"accessToken":{"description":"Access token recevied after user login with a deviceToken","scheme":"bearer","type":"http"},"authToken":{"description":"Token received from the auth service","scheme":"bearer","type":"http"},"integrationToken":{"scheme":"bearer","type":"http"}},"responses":{"ServiceHolidayListResponse":{"description":"Example response","content":{"application/json":{"schema":{"type":"object","properties":{"items":{"type":"array","items":{"$ref":"#/components/schemas/ServiceHolidayResponseSchema"}}},"required":["items"]}}}}},"schemas":{"ServiceHolidayResponseSchema":{"title":"ServiceHolidayResponseSchema","description":"One day the tenant's stores do not work — a public holiday out of a country's calendar, or a closure day the tenant added itself. Together the days of a year make up the tenant's holiday calendar.\nThe calendar is what the business-day math runs on: its active days that apply to a store are not among the store's working days, which both the readyAtEstimate prefill from the expected turnaround and avgWorkOpenDays on the service order statistics count. Nothing else reads it: it closes no store, blocks no work and stops no message from going out.\ncountryCode says which of the two a day is, and it is the only thing that says it. A day carrying a countryCode is one Flow put in the calendar from that country's public holidays: it can be renamed and deactivated, but never deleted. A day with an empty countryCode is the tenant's own, applies to every store, and can be deleted as well.\nA day only counts as non-working while active is true. Deactivating a public holiday is how the tenant says its stores keep that day as any other, and the day then takes no part in either calculation: whether it is one of a store's working days is decided by the store's open days and serviceCountWeekendsAsWorkingDays alone.","type":"object","required":["serviceHolidayUid","tenantUid","date","name","countryCode","active","createdAt","createdBy","lastModifiedAt","lastModifiedBy"],"properties":{"serviceHolidayUid":{"$ref":"#/components/schemas/UID"},"tenantUid":{"$ref":"#/components/schemas/UID"},"date":{"type":"string","format":"date","description":"The day that is not worked, as a date in the tenant's timezone. ISO 8601 date format: YYYY-MM-DD, e.g. 2026-05-17."},"name":{"type":"string","description":"What the day is called — the name of the public holiday, or whatever the tenant called its own closure day. A public holiday Flow put in the calendar is named in its country's own language (a Norwegian day reads \"Grunnlovsdag\", a Swedish one \"Sveriges nationaldag\") until the tenant renames it."},"countryCode":{"type":"string","description":"The country whose public holiday calendar the day came out of, which is how the same calendar carries days that only some of the tenant's stores keep: a day applies to a store when this matches the store's countryCode. It is also what says where the day came from. A day carrying a country is one Flow put there: it can be renamed and deactivated, but never deleted. An empty string on a day the tenant added itself, which applies to every store and can be deleted as well. This is what \"the days that apply to the store\" means everywhere the working-day count is described."},"active":{"type":"boolean","description":"Whether the day counts as non-working. Clearing it means the day stops counting as non-working: whether it is one of a store's working days is decided by the store's open days and serviceCountWeekendsAsWorkingDays alone. It is what a public holiday the tenant works through gets instead of a deletion — a day carrying a countryCode is deactivated rather than removed."},"createdAt":{"type":"string","format":"date-time"},"createdBy":{"type":"string"},"lastModifiedAt":{"type":"string","format":"date-time"},"lastModifiedBy":{"type":"string"}}},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"}},"parameters":{"serviceHolidayYearQuery":{"name":"year","in":"query","required":true,"schema":{"type":"integer","minimum":2000,"maximum":2999},"description":"The year to list the non-working days for, as four digits, e.g. 2026. The days are dates in the tenant's timezone. Reading a year seeds it: the first read of a year the tenant has no rows for generates that year's public holidays before answering, so the list always comes back complete. A business-day computation that reaches into an unseeded year — the readyAtEstimate prefill crossing a year end, or the open-hours work figure spanning one — seeds it the same way before computing, so the math never runs against an empty year."}}},"paths":{"/tenants/{tenantUid}/serviceorders/holidays":{"get":{"summary":"List the non-working days of a year","tags":["Service"],"responses":{"200":{"$ref":"#/components/responses/ServiceHolidayListResponse"}},"operationId":"get-serviceorders-holidays","description":"List the tenant's non-working days for one year — the holiday calendar the business-day math runs on. Both the public holidays Flow put there and the closure days the tenant added itself are returned, active and deactivated alike, so the whole year can be shown and edited from one list. countryCode tells the two apart: a day carrying one came out of that country's public holidays, and a day with an empty countryCode is the tenant's own.\nReading a year is what seeds it. The first read of a year the tenant has no rows for generates that year's public holidays from Flow's own holiday computation, for each country the tenant's stores are in, and stores them as rows before answering. Later reads of the same year return those rows as they now stand, edits included: the generation happens once and never overwrites what the tenant has since done to the year.\nThe calendar feeds two things and nothing else: intake skips its days when it prefills a service order's readyAtEstimate from the expected turnaround, and avgWorkOpenDays on the service order statistics leaves them out. It closes no store, blocks no work and stops no message from going out.\nA day only counts as non-working while it is active. A public holiday the tenant's stores work through is deactivated rather than deleted — a day carrying a countryCode can be renamed and deactivated but never deleted — and stops counting from then on.\nReading it asks for any service permission — SERVICE_ORDER or SERVICE_STORE_CONFIG at the tenant, at an organization or at any one store, or SERVICE_CONFIG, which is held at the tenant only — because whoever configures the holiday calendar reads it. A tenant-wide ADMIN grant counts as every permission. A caller holding none of them, a user with no role assignments included, is refused with a 403.\n\nRequired permissions: SERVICE_ORDER, SERVICE_STORE_CONFIG, SERVICE_CONFIG","parameters":[{"$ref":"#/components/parameters/serviceHolidayYearQuery"}]}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flowretail.com/docs/developers/api-documentation/service/list-the-non-working-days-of-a-year.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
