Migration of the route GET /v0/products/{product_id}/bookable_dates to GET /v1/products/{product_id}/bookable_dates
- Obsolète
- 10 juin 2025
- 1 route liée
Context
Upgrade from GET - /v0/products/{product_id}/bookable_dates to GET - /v1/products/{product_id}/bookable_dates
⭐ Key benefit :
- Uniformise the
GET/v1/products/{product_id}/bookable_datesoutput with theGET/v2/products/{product_id}/calendaroutput for existing status - Get the new PRE_BOOKABLE and SIBLING_OPEN status
Impacts
Route to call :
- GET -
/v1/products/{product_id}/bookable_dates
Output
- Both previous AVAILABLE and UNKNOWN status will be merged under the OPEN status (to match with the calendar output).
- A first new availibility status will also be available : PRE_BOOKABLE. This status means that the product is not yet available for booking, but will be in the near future.
- A second new availibility status will also be available : SIBILING_OPEN.
This status means that the product is closed but its sibling product from another season is open.
Related to this new status, we are adding the optional field
sibling_id, which will allow you to get the product_id from the sibling product.
| field name | field type | Description | Example | nullable |
|---|---|---|---|---|
| months.days.availabilities.sibling_id | string | id of the sibling product from another season | TIGC_SUMMER | true |
{
"months": [
{
"id": 202001,
"days": [
{
"id": 20200101,
"availabilities": [
{
- "status": "AVAILABLE",
+ "status": "OPEN",
"durations": [
7
]
}
]
},
{
"id": 20200102,
"availabilities": [
{
- "status": "UNKNOWN",
+ "status": "OPEN",
"durations": [
7
]
}
]
}
{
"id": 20200103,
"availabilities": [
{
! "status": "PRE_BOOKABLE",
"durations": [
7
]
}
]
},
{
"id": 20200104,
"availabilities": [
{
! "status": "SIBLING_OPEN",
+ "sibling_id": "TIGC_SUMMER",
"durations": [
7
]
}
]
}
]
}
]
}