---
uuid: 73733260-ccc2-40fe-a99e-d7a13f52f34b
date_created: 2025-10-27T10:57:12.502Z
date_updated: 2026-04-07T09:48:40.789Z
seo_url: list-club-med-destinations
category: Resort content
tags: 
  - Destinations
routes: 
  - GET /v0/destinations
---

# List Club Med destinations

This scenario explains how to retrieve the Club Med destinations grouped by geographic area and by country. It fits inspiration, destination-navigation, and catalog entry-point journeys.

The flow relies on a single listing route that returns the geographic structure, countries, and associated products.

## Flow

false

## Overview

This scenario helps an application build a destination browser from the geographic segmentation exposed by the API.

## Prerequisites

* An `accept-language` header matching the target locale.
* A valid `x-api-key`.
* Optionally a filter to narrow the returned list.

## Expected result

The application receives an exploitable tree of geographic areas, countries, and Club Med products that can be used in a destination-discovery journey.

## 1 - List the available destinations

Use `GET /v0/destinations` to retrieve the Club Med destinations available before letting the user pick a geographical area, a country, and then a product.

#### Prerequisites

* Send `accept-language` and `x-api-key`.
* Add a `filter` only if you need to narrow the returned scope.
* Reuse the same locale as the rest of the discovery flow.

#### Calling CURL

```bash
curl -X 'GET' \
  'https://api.clubmed.com/v0/destinations' \
  -H 'accept: application/json' \
  -H 'accept-language: en-US' \
  -H 'x-api-key: YOUR_API_KEY'
```

#### Example answer

```json
[
  {
    "id": "product_geographical_area_alps",
    "geographical_area": "les Alpes",
    "countries": [
      {
        "id": "FR",
        "label": "France",
        "products": [
          {
            "id": "SECC_WINTER",
            "type": "VILLAGE"
          }
        ]
      }
    ]
  }
]
```

> **info:** Reuse the geographical area first, then the country, then the `product_id` to build a progressive browsing flow.

***

**Response codes**

* **OK Response (200):** returns the destinations grouped by geographical area and then by country.
* **Error (400):** the request or the submitted filter is invalid.
* **Error (401):** non documented in Swagger.
* **Error (404):** `not_found`.

**Related route**: [GET https://api.clubmed.com//v0/destinations](https://api.clubmed.com/doc?search=GET%20%2Fv0%2Fdestinations)