> 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/update-a-day-in-the-holiday-calendar.md).

# Update a day in the holiday calendar

Rename a day in the holiday calendar, or say whether it counts as non-working. The date of a day cannot be changed: a day with an empty countryCode — the tenant's own — that sits on the wrong date is deleted and added again where it belongs, and a day carrying a countryCode, which cannot be deleted, is deactivated instead. Clearing active is what the tenant does with a public holiday their stores work through. The day stops counting as non-working from then on: whether it is one of a store's working days is decided by the store's open days and serviceCountWeekendsAsWorkingDays alone. Setting it again brings the day back. Renaming a public holiday is allowed and changes nothing but the label.

Required permissions: 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":{"ServiceHolidayResponse":{"description":"Example response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceHolidayResponseSchema"}}}}},"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-_]+"},"ServiceHolidayUpdateRequestSchema":{"title":"ServiceHolidayUpdateRequestSchema","description":"The day as it should read from now on. Only the name and whether it counts can be changed — the date of a day is fixed, and a day on the wrong date is deleted and added again where it belongs, or, where it carries a countryCode and cannot be deleted, deactivated instead.\nClearing active is what the tenant does with a public holiday their stores work through: the day stops counting as non-working, and whether it is one of a store's working days is decided by the store's open days and serviceCountWeekendsAsWorkingDays alone.","type":"object","required":["name"],"properties":{"name":{"type":"string","description":"What the day is called. Renaming a public holiday is allowed and changes nothing but the label."},"active":{"type":"boolean","description":"Whether the day counts as non-working. Left out, the day keeps what it has."}}}},"requestBodies":{"ServiceHolidayUpdateRequest":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceHolidayUpdateRequestSchema"}}}}}},"paths":{"/tenants/{tenantUid}/serviceorders/holidays/{serviceHolidayUid}":{"put":{"summary":"Update a day in the holiday calendar","operationId":"put-serviceorders-holidays","description":"Rename a day in the holiday calendar, or say whether it counts as non-working. The date of a day cannot be changed: a day with an empty countryCode — the tenant's own — that sits on the wrong date is deleted and added again where it belongs, and a day carrying a countryCode, which cannot be deleted, is deactivated instead.\nClearing active is what the tenant does with a public holiday their stores work through. The day stops counting as non-working from then on: whether it is one of a store's working days is decided by the store's open days and serviceCountWeekendsAsWorkingDays alone. Setting it again brings the day back.\nRenaming a public holiday is allowed and changes nothing but the label.\n\nRequired permissions: SERVICE_CONFIG","responses":{"200":{"$ref":"#/components/responses/ServiceHolidayResponse"}},"tags":["Service"],"requestBody":{"$ref":"#/components/requestBodies/ServiceHolidayUpdateRequest"}}}}}
```


---

# 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/update-a-day-in-the-holiday-calendar.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.
