Evolution of GET /v0/products/{product_id}/must_try_experiences in GET v0/products/{product_id}/highlights

Context

Evolution of the route GET /v0/products/{product_id}/must_try_experiences in GET v0/products/{product_id}/highlights

⭐ Key beneficts : To have a one route for all ClubMed highlights and will allows to welcome new ones later.

Impacts

• Deprecation of GET /v0/products/{product_id}/must_try_experiences

• New route to call : GET v0/products/{product_id}/highlights

2 types :

• MUST_TRY_EXPERIENCE
• REASON_TO_GO

[
  {
    "id": "Must_try_experience_01",
+    "type": "MUST_TRY_EXPERIENCE"
    "title": "AN ENCHANTING PERFORMANCE",
    "theme" : "",
    "description": "Sit back and cap off the perfect day with a charming performance.",
    "image": "http://mypicture02.jpg"
  }
]

Migration help to keep the must try experience

• Change the route
• use the filter with type MUST_TRY_EXPERIENCE to keep stricly the same information as before