The property search endpoint allows the use “limit” and “offset” fields for pagination to iterate through properties across larger areas such as states, counties, or cities.Tip: The “state” field is required. For best performance and lowest latency, include “state”, “county”, and “address”, since ZIP codes and city names can vary across data sources.
Provide your API key directly in the header.
Two-letter state (required field) (e.g., "CA")
ZIP code of the property (optional field).
County where the property is located (optional field).
City where the property is located (optional field).
Days to look back for transfers (e.g., "30") (optional field).
Numerical use code (e.g., 1002, 1001) (optional field).
The street address only (e.g. “123 Main Street”). Do not include city, state, or ZIP in this field. (optional field)
The unit number of the property (optional field). Do not include the type of unit. (e.g. “APT 2B” would just be “2B”)
Maximum number of results to return. Defaults to 10, maximum is 100.
1 <= x <= 100Number of records to skip. Defaults to 0.
x >= 0If true, only residential properties; if false, only non-residential (optional field).