Tracking a market over time

Pull daily series of asking rates, occupancy and supply with /api/v1/trends, and check how much history exists before comparing periods.

One snapshot a day

JokerPrice stores one snapshot per destination per day: supply, the median asking rate and, where calendars are tracked, occupancy, ADR, RevPAR and nights on the books. GET /api/v1/trends returns those snapshots as a series.

Request a series

curl -H "Authorization: Bearer $JOKERPRICE_KEY" \
  "https://jokerprice.com/api/v1/trends?city=dubai&metric=asking&days=90"

Read the response

The series is in trends.points, one entry per day with a day and a value; for asking each point also carries the 25th and 75th percentiles. trends.changes compares the latest value with 7, 30 and 90 days earlier where that much history exists, and trends.supply follows the listing count.

Check history first

trends.history.days and trends.history.firstDay say how much history is stored, and trends.notice explains in words when the series is short. Year-over-year comparison appears in trends.yearOverYear only once a full year is stored. Do not compare a two-week series with a seasonal pattern; wait for it to fill in.

Combine with the current metrics

For the latest occupancy picture, including lead times and weekday patterns, call GET /api/v1/metrics?city=riyadh and check its maturity field. Use trends for direction over time and metrics for the detail of the current window.

More in API cookbook

Put the numbers to work for your property.

Start free trial