Displaying attraction details 3.2 Beta

Best practices for presenting attraction information retrieved via accommodations/details endpoint.

Key information to display

When showing attraction details to travellers, focus on the most relevant information first:

• Name & category - Present the attraction name prominently, alongside main categories such as museum, tours, or food_drinks.

• Short description - Display a concise summary of the attraction (long_description) to help travellers quickly understand the experience.

• Location - Include the city, landmark, exact address, and optionally a map for context.

• Photos - Display high-quality images, ideally using the first item from photos. Consider carousels for multiple images.

• Duration - Show estimated visit time (duration) in an easy-to-read format, e.g., “Approx. 2 hours”.

• Ratings - Include average score and number of reviews from ratings. Visual stars help with immediate recognition.

• Supported languages - Display languages in which the attraction is available.

Highlight badges and categories

Badges and categories influence traveller decisions:

• Badges (badges) - Highlight features like best_seller or guest_pickup. Use visual tags or icons to make these stand out.
• Categories (categories) - Use icons or tags to communicate the type of attraction (museums_arts_culture, nature_outdoor, food_drinks) for quick scanning.

Handling multiple locations

Some attractions have multiple locations (e.g., pickup points, entrances):

• Display each location clearly with type (arrival, attraction, departure, guest_pickup).
• Use maps, lists, or pins to help travellers visualise the itinerary.

Optional enhancements

Combine /attractions/details with search results (/attractions/search) to show pricing, availability, or free cancellation alongside static details.

• Highlight nearest landmarks if travellers searched by coordinates.
• Use pagination (page and rows) to load large result sets incrementally for better performance.

Example layout

This structure ensures clarity, consistency, and a smooth traveller experience while using /attractions/details data.

Example: