Skip to main content
Through the API you read the same figures the account sees in Housera: the chart on the account’s front page, each listing’s row in My listings, and the price comparison with the area on the listing’s page. They all need the listings:read permission and cover only the listings the key sees (see Which listings each key sees). There are three figures: Days are calendar days in the time zone given in timezone. Today comes with partial: true because it is not over yet, and its figures keep growing until midnight.

The account’s chart

GET /account/stats?range=30 gives the chart from the account’s front page, over 7, 30 or 90 days:
  • previous holds the totals of the period before, of the same length, so you can see whether the listings are doing better or worse.
  • The key of an account with no team (a person or an agent) gets the account’s listings (scope: account), and top has the five most viewed listings.
  • The key of the owner, an administrator or a manager gets the listings of the team it sees in the portal (scope: team): the whole firm for the owner and administrators, their team for a manager. top then has the colleagues with the most views. With agent=<email> you get one colleague’s figures only.
  • moments and contacts come from client requests, so you get them only if the key also has leads:read. Without it they are null.

A listing’s days

GET /account/listings/{code}/stats?from=2026-10-01&to=2026-10-31 gives one listing’s days, at most 90 in one request. Without from and to you get the last 30 days, today included. A future date stops at today.
views_total holds every view since the listing was published. For a weekly report to the owner, ask for the listing’s last 7 days and compare them with the week before.

The figures in the listings list

Every listing in GET /account/listings and GET /account/listings/{code} has its row from My listings:
If you only want the figures, ask for fields=code,stats_30d,views_total.

The price against the area

The listing also carries the comparison from its page, when you ask for it in fields:
  • price_per_sqm is the price per square metre in euro, for sales only.
  • price_vs_area compares the listing with listings of the same type and transaction in the area: the median, the typical range (the middle half of the listings sits between p25 and p75) and how far the listing is from the median (delta_pct, positive above, negative below). The *_price values are the same figures at the listing’s surface.
  • price_vs_area is null when the area does not have enough comparable listings, as on the listing’s page.
  • The comparison is worked out for each listing, so it comes only when you ask for it in fields, in GET /account/listings or GET /account/listings/{code}, for example fields=code,price_per_sqm,price_vs_area. The answer to a write (POST, PUT, PATCH) does not have it.