> 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/add-a-closure-day-to-the-holiday-calendar.md).

# Add a closure day to the holiday calendar

Add a day of the tenant's own to the holiday calendar — the days their stores are shut that no public holiday calendar knows about, such as a staff day or a summer week. Supply serviceHolidayUid to make the call idempotent: a repeat with the same serviceHolidayUid returns the day already created and writes nothing — any serviceHolidayUid the tenant already holds for a day of its own returns that day — while a malformed uid stays refused. A serviceHolidayUid held by a public holiday is refused with a 400. The day is created active and belongs to the whole tenant rather than to a country, so its countryCode comes back empty. That empty countryCode is what marks it as the tenant's own, and unlike a public holiday it can therefore be deleted. Adding a day changes nothing that has already been estimated: it is read when a business-day figure is next computed, and the readyAtEstimate dates already on service orders stand as they were set.

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-_]+"},"ServiceHolidayCreateRequestSchema":{"title":"ServiceHolidayCreateRequestSchema","description":"A closure day of the tenant's own — the days their stores are shut that no public holiday calendar knows about, such as a staff day or a summer week. Supply serviceHolidayUid to make the call idempotent: a repeat with the same serviceHolidayUid returns the day already created and writes nothing — any serviceHolidayUid the tenant already holds for a day of its own returns that day — while a malformed uid stays refused. A serviceHolidayUid held by a public holiday is refused with a 400. The day is created active and with an empty countryCode, which is what makes it the tenant's own: it applies to every store, and unlike a public holiday it can be deleted.","type":"object","required":["date","name"],"properties":{"serviceHolidayUid":{"$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-07-13."},"name":{"type":"string","description":"What to call the day. Shown in the holiday calendar next to the public holidays."}}}},"requestBodies":{"ServiceHolidayCreateRequest":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceHolidayCreateRequestSchema"}}}}}},"paths":{"/tenants/{tenantUid}/serviceorders/holidays":{"post":{"summary":"Add a closure day to the holiday calendar","operationId":"post-serviceorders-holidays","description":"Add a day of the tenant's own to the holiday calendar — the days their stores are shut that no public holiday calendar knows about, such as a staff day or a summer week. Supply serviceHolidayUid to make the call idempotent: a repeat with the same serviceHolidayUid returns the day already created and writes nothing — any serviceHolidayUid the tenant already holds for a day of its own returns that day — while a malformed uid stays refused. A serviceHolidayUid held by a public holiday is refused with a 400.\nThe day is created active and belongs to the whole tenant rather than to a country, so its countryCode comes back empty. That empty countryCode is what marks it as the tenant's own, and unlike a public holiday it can therefore be deleted.\nAdding a day changes nothing that has already been estimated: it is read when a business-day figure is next computed, and the readyAtEstimate dates already on service orders stand as they were set.\n\nRequired permissions: SERVICE_CONFIG","responses":{"201":{"$ref":"#/components/responses/ServiceHolidayResponse"}},"tags":["Service"],"requestBody":{"$ref":"#/components/requestBodies/ServiceHolidayCreateRequest"}}}}}
```


---

# 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/add-a-closure-day-to-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.
