Prepare a price estimate before ODR

  • Prebooking
  • 1 route
How do I build a price estimate page before ODR from the product catalog?

This scenario is an entry point for a B2C price estimate page. It helps retrieve the resort catalog and expose a first layer of commercial information in order to collect customer preferences before ODR.

It is useful to qualify a travel intent, prepare a later prebooking flow, and guide the user toward the most relevant products.

Overview

Use this scenario to build the first layer of a B2C price-estimate page before ODR. The documented flow focuses on browsing the resort catalog and exposing enough product information to qualify travel intent before later search, pricing, or prebooking steps.

Prerequisites

  • Have a valid x-api-key.
  • Send an accept-language that matches the targeted market.
  • Plan for a front-end that can reuse the selected product_id in later pricing flows.
1

List resorts

Optional

Use GET/v2/products to list the resorts available before building the price-estimate page.

Prerequisites

Prepare the parameters required by the call. Keep x-api-key and, when the route is customer-scoped, a valid bearer token.

Calling CURL

curl -X GET \
  -H "x-api-key: YOUR_API_KEY" \
  -H "accept-language: en-US" \
  "https://api.clubmed.com/v2/products?limit=20&page=1"

Example answer

[
  {
    "id": "product-1",
    "label": "Club Med Valmorel",
    "country_code": "FR",
    "type": "RESORT"
  }
]

info: Select the relevant resort product_id to continue toward pricing or the estimate flow.

Response codes

  • 200 OK: the expected data is returned.
  • 400 Bad Request: the request is invalid or incomplete.
  • 404 Not Found: the requested resource cannot be found.
Click to expand
GET/v2/products
See more