Problem statement
- The /v2/properties/search API returns null for the pricing field when called with date parameters, making it impossible to display approximate pricing on property listing pages
- Integrations cannot show "starting from" or indicative nightly rates without requiring additional API calls or complex calculations
Current workaround
- Call the calendar endpoint per property to extract minimum/average nightly rates
- Use base nightly rate as a static fallback (less dynamic)
- Pass sample dates to search endpoint and parse daily pricing (requires additional logic)
Impact
- Increased API calls and latency for displaying pricing on listing pages
- Poor user experience — users can't quickly determine if a property fits their budget before browsing
- Complex integration logic required to derive indicative pricing from multiple sources
Proposed solution
Include an indicative pricing field (e.g., nightly rate or "starting from" price) in the /v2/properties/search and /v2/properties/{uuid} API responses, even when called without date parameters. This could be the base nightly rate or a calculated average from upcoming calendar data.
Unlock
- Integrations can display approximate pricing directly on property listing pages
- Users can quickly filter properties by budget before initiating bookings
- Reduced API calls and simpler integration logic