Temporary closing

Temporary closing takes the store out of the listing until a date and time you choose. It is what you use when the restaurant cannot take orders: restocking, a breakdown, short staffing, a holiday.

Operation	Method and path
Set	`PUT /api/v3/scheduling/stores/{storeId}/closing`
Check	`GET /api/v3/scheduling/stores/{storeId}/closing`
Cancel	`DELETE /api/v3/scheduling/stores/{storeId}/closing`

Setting

PUT /api/v3/scheduling/stores/gi20__001/closing
Authorization: your-api-key
Content-Type: application/json

{
  "until": "2026-12-20T10:00:00+02:00"
}

Response: 204 No Content.

Rule	Detail
Format	ISO-8601 with a timezone offset.
Moment	Must be in the future. A past date returns `400`.

Checking

GET /api/v3/scheduling/stores/gi20__001/closing
Authorization: your-api-key

The response carries an until field. When it is null, there is no active closing — the store follows its regular schedule.

Cancelling

DELETE /api/v3/scheduling/stores/gi20__001/closing
Authorization: your-api-key

Response: 204 No Content. The store returns to its regular schedule immediately, even if the date in until has not been reached.

Response codes

Code	What it means
`204`	The operation succeeded.
`400`	Invalid payload or a date in the past.
`401`	Missing or invalid key.
`403`	Your key has no rights on this store.
`404`	The store does not exist.
`500`	Internal error.

Temporary closing or stopping notifications?

These are different things and are often confused:

You want to…	You use
Stop customers from ordering	temporary closing
Stop us sending you orders, but keep the store open	turning notifications off in the portal