Active Market Statistics

GET 
/v4/market-statistics/active

Get market statistics based on search criteria. This endpoint returns aggregated statistics for any listings that have an active or pending status.

Required: Filters must include either a boundary-id or an MLS plus one additional area filter. Area filters include city, area-level-1, area-level-2, and postal-code.

Request

Query Parameters

status string[]

The status or statuses you want aggregated market statistics for. See RESO Standard Status Lookups for more information on status types. We expect the status to be in "PascalCase" format but will attempt map any casing convention to the relevant status.

Possible values: [Active, ActiveUnderContract, Pending]

Default value: [Active, Pending, ActiveUnderContract]

Example: ?status=Active&status=Pending

Examples:

Active

Example: Active

Pending

Example: Pending

ActiveUnderContract

Example: ActiveUnderContract

mls string[]
The MLS code you want associated boundary IDs from.
Example: &mls=recolorado&mls=pikespeak
boundary-id string[]
The boundary id or ids you want aggregated market statistics for. Boundary ids are the only way to get data by legally defined geometry. All other parameters like city, search on the postal address. See Cities vs Postal Cities. By default, all boundary IDs will be grouped together. If you want to group by individual boundary IDs, you can use the
group-by
query parameter. Note: at least one boundary-id, city, local-area-1, local-area-2, or postal-code is required.
Example: &boundary-id=593979d6da3374b282bb7bbb&boundary-id=593979d6da3374b282bb7bcb
property-type string[]
The property type or types you want aggregated market statistics for.
Possible values: [Residential, ResidentialLease, Commercial, CommercialLease, Land, Industrial, Other, Timeshare]
Default value: [Residential]
Example: &property-type=Residential&property-type=Commercial
property-sub-type string[]
The property sub type or sub types you want aggregated market statistics for. Sub Types are used to distinguish between the types of residential or commercial data available.

For instance, the most common suburban home would be a SingleFamilyResidence. A Condominium is usually defined as a subsection of a building made to be a place of dwelling. The place of dwelling is usually only 1 story tall. A Townhouse is usually a multilevel building attached to other multilevel buildings with no dwelling above or below it. See the RESO Standard Lookups for more information on property sub types.
Disclaimer: LiveBy ensures the availability of SingleFamilyResidence, Townhouse, and Condominium in each MLS. The availability of other PropertySubTypes may vary and is more limited by MLS.
For Residential Listings, we recommend using SingleFamilyResidence, Townhouse, and Condominium.
Possible values: [SingleFamilyResidence, Agriculture, Apartment, BoatSlip, Business, Cabin, Condominium, DeededParking, Farm, Hotel, Industrial, ManufacturedHome, MixedUse, Mobile, MultiFamily, Office, OwnYourOwn, Ranch, Retail, StockCooperative, Timeshare, Townhouse, Land, UnimprovedLand, Warehouse, Other]
Example: &property-sub-type=SingleFamilyResidence&property-sub-type=Condominium
city string[]
The postal city or cities you want aggregated market statistics for. You can use this instead of a boundary id. This uses the RESO Standard field “City”.
Example: &city=Lincoln&city=Omaha
area-level-1 string[]
The first political subdivision you want aggregated market statistics for. You can use this instead of a boundary id. This is often called “state”, “province” or “district” in various countries. This uses the RESO standard field “StateOrProvince”.
Example: &area-level-1=Nebraska&area-level-1=Iowa
area-level-2 string[]
The second political subdivision you want aggregated market statistics for. You can use this instead of a boundary id. This uses the RESO standard field “CountyOrParish”.
Example: &area-level-2=Lancaster&area-level-2=Seward
postal-code string[]
The postal code or codes you want aggregated market statistics for. You can use this instead of a boundary id. This uses the RESO standard field “PostalCode”.
Example: &postal-code=68521&postal-code=68502
mls-area-major string[]
The MLS Area Major for which you want market statistics.
Example: &mls-area-major=napa
outlier-original-list-price-low number
LiveBy by default cleans the data to remove outliers. LiveBy does not remove outlier data from the total counts, only the field’s counts, and statistics. You can use the count value of each field to determine if that field had outliers and was available from the MLS data sources.
Default value: 5000
Example: &outlier-original-list-price-low=5000
outlier-original-list-price-high number
LiveBy by default cleans the data to remove outliers. LiveBy does not remove outlier data from the total counts, only the field’s counts, and statistics. You can use the count value of each field to determine if that field had outliers and was available from the MLS data sources.
Default value: 1000000000
Example: &outlier-original-list-price-high=1000000000
outlier-list-price-low number
LiveBy by default cleans the data to remove outliers. LiveBy does not remove outlier data from the total counts, only the field’s counts, and statistics. You can use the count value of each field to determine if that field had outliers and was available from the MLS data sources.
Default value: 5000
Example: &outlier-list-price-low=5000
outlier-list-price-high number
LiveBy by default cleans the data to remove outliers. LiveBy does not remove outlier data from the total counts, only the field’s counts, and statistics. You can use the count value of each field to determine if that field had outliers and was available from the MLS data sources.
Default value: 1000000000
Example: &outlier-list-price-high=1000000000
outlier-living-area-low number
LiveBy by default cleans the data to remove outliers. LiveBy does not remove outlier data from the total counts, only the field’s counts, and statistics. You can use the count value of each field to determine if that field had outliers and was available from the MLS data sources.
Example: &outlier-living-area-low=0
outlier-living-area-high number
LiveBy by default cleans the data to remove outliers. LiveBy does not remove outlier data from the total counts, only the field’s counts, and statistics. You can use the count value of each field to determine if that field had outliers and was available from the MLS data sources.
Default value: 10000
Example: &outlier-living-area-high=10000
outlier-year-built-low number
LiveBy by default cleans the data to remove outliers. LiveBy does not remove outlier data from the total counts, only the field’s counts, and statistics. You can use the count value of each field to determine if that field had outliers and was available from the MLS data sources.
Default value: 1700
Example: &outlier-year-built-low=1700
outlier-year-built-high number
LiveBy by default cleans the data to remove outliers. LiveBy does not remove outlier data from the total counts, only the field’s counts, and statistics. You can use the count value of each field to determine if that field had outliers and was available from the MLS data sources.
Default value: 2025
Example: &outlier-year-built-high=2025
list-price-low number
This filters out any listings that have a list price less than the value specified. Unlike the outlier filter, this will remove listings from all statistics, not just the price statistics.
Example: ?list-price-low=100000
list-price-high number
This filters out any listings that have a list price greater than the value specified. Unlike the outlier filter, this will remove listings from all statistics, not just the price statistics.
Example: ?list-price-high=10000000
group-by string
This lets you group the data by boundary ID, by specifying
&group-by=boundary-id
you'll receive aggregates for each boundary ID requested. Otherwise, you'll receive the data aggregated together for all requested boundary IDs.
Possible values: [boundary-id]
Example: &group-by=boundary-id

Responses

200

application/json

Schema

Schema

successbooleanrequired

data

object[]

Array [

priceRangestring[]

Price range of the properties

boundaryIdstring[]

If the query is grouping by boundary id, this is the id of the boundary.

PropertySubTypestring[]

If the query is grouping by property sub type, this is the property sub type.

PropertyTypestring[]

If the query is grouping by property type, this is the property type.

metadataobjectrequired

The MLSes that provided data for these statistics

Example: {"attribution":[{"name":"North MLS"},{"name":"Northeast MLS"}]}

data

object

required

countnumberrequired

Total count of listings within the period

ListPrice

object

required

Statistics about the price that the property was listed for when it sold

countnumberrequired

Amount of non null and numeric values used to make statistics that is within the outlier range specified

Example: 10

mediannumberrequired

Median of the non null and numeric values that is within the outlier range specified

Example: 500000

averagenumberrequired

Mean average of the non null and numeric values that is within the outlier range specified

Example: 532561

minimumnumberrequired

Smallest value of the non null and numeric values that is within the outlier range specified

Example: 100000

maximumnumberrequired

Largest value of the non null and numeric values that is within the outlier range specified

Example: 20000000

sumnumberrequired

Total sum of the non null and numeric values that is within the outlier range specified

Example: 256373500

OriginalListPrice

object

required

Statistics about the First List Price before price adjustments

countnumberrequired

Amount of non null and numeric values used to make statistics that is within the outlier range specified

Example: 10

mediannumberrequired

Median of the non null and numeric values that is within the outlier range specified

Example: 500000

averagenumberrequired

Mean average of the non null and numeric values that is within the outlier range specified

Example: 532561

minimumnumberrequired

Smallest value of the non null and numeric values that is within the outlier range specified

Example: 100000

maximumnumberrequired

Largest value of the non null and numeric values that is within the outlier range specified

Example: 20000000

sumnumberrequired

Total sum of the non null and numeric values that is within the outlier range specified

Example: 256373500

YearBuilt

object

required

Statistics about the year the properties were built

countnumberrequired

Amount of non null and numeric values used to make statistics that is within the outlier range specified

Example: 10

mediannumberrequired

Median of the non null and numeric values that is within the outlier range specified

Example: 500000

averagenumberrequired

Mean average of the non null and numeric values that is within the outlier range specified

Example: 532561

minimumnumberrequired

Smallest value of the non null and numeric values that is within the outlier range specified

Example: 100000

maximumnumberrequired

Largest value of the non null and numeric values that is within the outlier range specified

Example: 20000000

sumnumberrequired

Total sum of the non null and numeric values that is within the outlier range specified

Example: 256373500

LivingArea

object

required

Statistics about the square footage of the properties

countnumberrequired

Amount of non null and numeric values used to make statistics that is within the outlier range specified

Example: 10

mediannumberrequired

Median of the non null and numeric values that is within the outlier range specified

Example: 500000

averagenumberrequired

Mean average of the non null and numeric values that is within the outlier range specified

Example: 532561

minimumnumberrequired

Smallest value of the non null and numeric values that is within the outlier range specified

Example: 100000

maximumnumberrequired

Largest value of the non null and numeric values that is within the outlier range specified

Example: 20000000

sumnumberrequired

Total sum of the non null and numeric values that is within the outlier range specified

Example: 256373500

pricePerSquareFoot

object

required

Statistics about the price per square foot of the properties

countnumberrequired

Amount of non null and numeric values used to make statistics that is within the outlier range specified

Example: 10

mediannumberrequired

Median of the non null and numeric values that is within the outlier range specified

Example: 500000

averagenumberrequired

Mean average of the non null and numeric values that is within the outlier range specified

Example: 532561

minimumnumberrequired

Smallest value of the non null and numeric values that is within the outlier range specified

Example: 100000

maximumnumberrequired

Largest value of the non null and numeric values that is within the outlier range specified

Example: 20000000

sumnumberrequired

Total sum of the non null and numeric values that is within the outlier range specified

Example: 256373500

daysOnSite

object

required

Statistics about the number of days from the On Market Date to today. This field is derived from the On Market Date specified by an MLS, and can be null. If daysOnSite is missing null, either daysToClose or daysToContract can be used.

countnumberrequired

Amount of non null and numeric values used to make statistics that is within the outlier range specified

Example: 10

mediannumberrequired

Median of the non null and numeric values that is within the outlier range specified

Example: 500000

averagenumberrequired

Mean average of the non null and numeric values that is within the outlier range specified

Example: 532561

minimumnumberrequired

Smallest value of the non null and numeric values that is within the outlier range specified

Example: 100000

maximumnumberrequired

Largest value of the non null and numeric values that is within the outlier range specified

Example: 20000000

sumnumberrequired

Total sum of the non null and numeric values that is within the outlier range specified

Example: 256373500

priceReductionCountnumberrequired

Count of listings that the final List Price was less than the Original List Price

Example: 10

priceReductionPercentagenumberrequired

Percentage of listings that the final List Price was less than the Original List Price

Example: 3.23

]

Example (from schema)

{
  "success": true,
  "data": [
    {
      "priceRange": [
        "string"
      ],
      "boundaryId": [
        "string"
      ],
      "PropertySubType": [
        "string"
      ],
      "PropertyType": [
        "string"
      ],
      "metadata": {
        "attribution": [
          {
            "name": "North MLS"
          },
          {
            "name": "Northeast MLS"
          }
        ]
      },
      "data": {
        "count": 0,
        "ListPrice": {
          "count": 10,
          "median": 500000,
          "average": 532561,
          "minimum": 100000,
          "maximum": 20000000,
          "sum": 256373500
        },
        "OriginalListPrice": {
          "count": 10,
          "median": 500000,
          "average": 532561,
          "minimum": 100000,
          "maximum": 20000000,
          "sum": 256373500
        },
        "YearBuilt": {
          "count": 10,
          "median": 500000,
          "average": 532561,
          "minimum": 100000,
          "maximum": 20000000,
          "sum": 256373500
        },
        "LivingArea": {
          "count": 10,
          "median": 500000,
          "average": 532561,
          "minimum": 100000,
          "maximum": 20000000,
          "sum": 256373500
        },
        "pricePerSquareFoot": {
          "count": 10,
          "median": 500000,
          "average": 532561,
          "minimum": 100000,
          "maximum": 20000000,
          "sum": 256373500
        },
        "daysOnSite": {
          "count": 10,
          "median": 500000,
          "average": 532561,
          "minimum": 100000,
          "maximum": 20000000,
          "sum": 256373500
        },
        "priceReductionCount": 10,
        "priceReductionPercentage": 3.23
      }
    }
  ]
}

401

Unauthorized

403

Forbidden

429

Too Many Requests

500

Internal Server Error

504

Service Unavailable