---
title: "List closure periods"
method: GET
path: "/api/v1/closures"
tags: ["Closures"]
---

# List closure periods

`GET /api/v1/closures`

## Request

- Base URL: `https://www.gerezi.com`
- URL: `https://www.gerezi.com/api/v1/closures`
- Auth: HTTP bearer

Lists closure periods (fermetures), CLOSED AvailabilityRule 'Schedule Exceptions', AND WAITLIST_ONLY AvailabilityRule windows for the restaurants this key can access. Each row carries a `kind` (CLOSURE_PERIOD | SCHEDULE_EXCEPTION | WAITLIST_ONLY) and, for rules, `service_period_id`/`service_period_name` (null = restaurant-wide). Every kind exposes the `id` needed to lift it (ClosurePeriod via DELETE /api/v1/closures/:id, rules via DELETE /api/v1/availability-rules/:id). WAITLIST_ONLY windows accept only guest waitlist sign-ups; staff can still book via POST /bookings with `force_closed:true`. Recurring annual rules are excluded. Defaults to current + future entries. Read scope: bookings:read.

## Query parameters

- `from` string, date
- `to` string, date
- `include_past` boolean

## Response `200`

List of closure periods

## Other responses

- `401`: Missing or invalid API key
- `403`: Key lacks required scope

---

[API](https://skmtc.dev/gerezi/apis/gerezi-restaurant-api.md) · [All operations](https://skmtc.dev/gerezi/apis/gerezi-restaurant-api/llms.txt) · [OpenAPI document](https://skmtc.dev/gerezi/apis/gerezi-restaurant-api/revisions/323b530e81cb?raw)