---
uuid: c15f9e07-75d2-443a-b7aa-f34e8582c345
date_created: 2026-02-27T06:19:33.652Z
date_updated: 2026-04-03T17:59:13.621Z
seo_url: retrieve-resort-period-information
category: Resort content
tags: 
  - Product Information
routes: 
  - GET /v1/products/{product_id}/periods_info
  - GET /v1/products/{product_id}/periods_info
---

# Retrieve resort period information

This scenario shows how to retrieve the operating, event, and closure periods of a resort through the product periods endpoint.

## Flow

```mermaid
flowchart LR
    step0["Retrieve resort operating periods"]
    step1["Identify closure and event periods"]
    step0 --> step1
```

## Overview

Use `GET /v1/products/{product_id}/periods_info` to access the resort period information attached to a product. This is useful to expose opening windows, event periods, or closure periods in a product information context.

## Prerequisites

* `product_id` must be known.
* `accept-language` and `x-api-key` headers are required.
* Additional query options are not fully visible in the available source material.

## 1 - Retrieve resort operating periods

Use `GET /v1/products/{product_id}/periods_info` to retrieve the period entries exposed for a product, including operation windows that can be surfaced in a resort information page.

#### Prerequisites

* Header `accept-language`
* Header `x-api-key`
* Optional header `authorization`
* Path `product_id`

#### Calling CURL

```bash
curl -X GET "https://api.clubmed.com/v1/products/MPAC/periods_info" \
  -H "accept-language: en-US" \
  -H "x-api-key: <your-api-key>"
```

#### Example answer

```json
[
  {
    "type": "EXCLUSIVITY",
    "start_date": "2020-12-01",
    "end_date": "2020-12-31"
  }
]
```

> **info:** Start by storing the raw period entries as returned by the API. They provide the base dataset for calendars, product pages or operational labels in downstream channels.

***

**Response codes**

* `200`: period entries returned successfully.
* `400`: bad request or validation error.
* `401`: unauthorized when a protected context is requested.
* `403`: forbidden.
* `404`: unknown product.

**Related route**: [GET https://api.clubmed.com//v1/products/{product\_id}/periods\_info](https://api.clubmed.com/doc?search=GET%20%2Fv1%2Fproducts%2F%7Bproduct_id%7D%2Fperiods_info)

## 2 - Identify closure and event periods

Use the same `GET /v1/products/{product_id}/periods_info` response to interpret the returned `type` values and distinguish operating, closure or event periods in your channel logic.

#### Prerequisites

* Header `accept-language`
* Header `x-api-key`
* Optional header `authorization`
* Path `product_id`

#### Calling CURL

```bash
curl -X GET "https://api.clubmed.com/v1/products/MPAC/periods_info" \
  -H "accept-language: en-US" \
  -H "x-api-key: <your-api-key>"
```

#### Example answer

```json
[
  {
    "type": "EXCLUSIVITY",
    "start_date": "2020-12-01",
    "end_date": "2020-12-31"
  }
]
```

> **info:** The route returns one flat list of period entries. Your application must interpret the `type` field to decide whether a period should be shown as an opening window, an exclusivity period, a closure or an event-related label.

***

**Response codes**

* `200`: period entries returned successfully.
* `400`: bad request or validation error.
* `401`: unauthorized when a protected context is requested.
* `403`: forbidden.
* `404`: unknown product.

**Related route**: [GET https://api.clubmed.com//v1/products/{product\_id}/periods\_info](https://api.clubmed.com/doc?search=GET%20%2Fv1%2Fproducts%2F%7Bproduct_id%7D%2Fperiods_info)