---
uuid: 7d8795e0-1e50-48ed-9b5d-a5a230967e90
date_created: 2026-02-26T16:41:35.679Z
date_updated: 2026-04-07T09:48:40.789Z
seo_url: best-product-prices
category: Shopping
routes: 
  - GET /v1/search_price
---

# Best product prices

This scenario explains how to search informative prices for one or more products based on travel criteria such as dates, duration, and traveler composition. It fits shopping, comparison, and pre-booking journeys that need indicative pricing before proposal creation.

The flow uses one price-search route and returns the best informative price blocks that can feed a shopping interface.

## Flow

false

## Overview

This scenario helps a shopping interface retrieve indicative prices without creating a proposal.

## Prerequisites

* The product identifiers or commercial search context to evaluate.
* A valid `accept-language` header and `x-api-key`.
* The travel criteria required by the route, such as dates, duration, attendee count, and transport context when relevant.

## Expected result

The application can compare informative prices for one or more products and reuse the returned price context to orient the next step of the shopping journey.

## 1 - Search informative prices

Use `GET /v1/search_price` to retrieve informative best prices for one or several products before creating any proposal. This route is useful for inspiration, merchandising, or price-comparison widgets when you want to display indicative pricing without persisting a booking file.

#### Prerequisites

* Send `accept-language` and `x-api-key`.
* Provide the main travel criteria in query parameters, especially `product_id`, `duration`, and the travel dates.
* Add traveler composition such as `number_attendees` and `birthdates` when pricing depends on age.

#### Calling CURL

```bash
curl -X 'GET' \
  'https://api.clubmed.com/v1/search_price?product_id=MPAC&duration=7&first_date=2026-07-01&last_date=2026-08-31&number_attendees=2' \
  -H 'accept: application/json' \
  -H 'accept-language: en-US' \
  -H 'x-api-key: YOUR_API_KEY'
```

#### Example answer

```json
{
  "currency": "EUR",
  "amount": 2890,
  "breakdown": [
    {
      "label": "Stay",
      "amount": 2500
    },
    {
      "label": "Transport",
      "amount": 390
    }
  ]
}
```

> **info:** This route is informative only. If the user wants to hold stock or continue to booking, switch to proposal-search endpoints instead.

***

**Response codes**

* `200 OK`: returns indicative best-price data for the submitted criteria.
* `400 Bad Request`: one query parameter is missing, malformed, or inconsistent.
* `401 Unauthorized`: non documented in the current Swagger extract.
* `404 Not Found`: non documented in the current Swagger extract.

**Related route**: [GET https://api.clubmed.com//v1/search\_price](https://api.clubmed.com/doc?search=GET%20%2Fv1%2Fsearch_price)