Constructing Property Queries

The Datafiniti API lets you build out a wide variety of search queries so you can get the exact data you want.

Querying a single field

The simplest query you can do is querying a single field. Here's an example:

{
	"query": "city:Austin"
}

This tells the API to search the property database for any business that has the value Austin in its city field.

You can do similar queries on any of the fields in the property schema. Here's an example that queries the country field:

{
	"query": "country:US"
}

Querying multiple fields

You can run more complicated queries by combining fields with various boolean operators (e.g., AND OR). For example:

{
	"query": "city:Austin AND numBathroom:2"
}

This returns any properties in Austin that have 2 bathrooms.

You can use the OR operator to run broader queries. For example:

{
	"query": "city:Austin OR city:Houston"
}

That's not all though. We can group fields and operators with parentheses to do some really fancy stuff:

{
	"query": "(categories:Austin OR city:Houston) AND numBathroom:2"
}

Querying multiple values

If you want to query multiple values within the same field, there is a simple way to do this. For example:

{
	"query": "city:(Austin OR Houston OR Dallas)"
}

This returns any properties in any of the above cities. This is much simpler than:

{
	"query": "city:Austin OR city:Houston OR city:Dallas"
}

Exact matches

You can use " quotes to match the exact string you are searching for

{
 "query":"dateUpdated:[2022-01-01 TO *] AND mostRecentStatus:(Rental OR \"For Sale\")"
}

Wildcards

You can use * to query a field for any value, like this:

{
	"query": "prices:*"
}

This will return any properties that have price information. This is helpful if we want to make sure any properties we get back are guaranteed to have certain fields filed out.

Wildcards can do more though. You can also append * to the value we're searching on to broaden its potential matches. For example:

{
	"query": "buildingName:Tower*"
}

This will return properties with any of the following in their buildingName field: Tower, Towers, and so on.

Querying sub-fields

Several fields in our schema have sub-fields. For example, reviews has sub-fields like date, rating, and others. Everything you can do to query fields, you can also do to query sub-fields. For example:

{
	"query": "reviews.rating:3"
}

will return all properties that have a review with a 3-star rating.

It's important to note here that querying on sub-fields will not only return sub-objects that match your query. The entire field will be returned.

For instance, if a property look likes this:

{
  "address": "123 Anywhere Ln",
  "reviews:": [
    {
      "rating": 3
    },
    {
      "rating": 4
    }
  ]
}

then you'll see both rating values in your data, even if you do "query": "reviews.rating:3".

Compound Queries on sub-fields

Along with querying individual sub-fields, you can also query for sub-objects that have multiple fields that meet specific requirements. For example, you can find all properties that have a broker with a listed email and phone number.

{
   "query":"{ brokers.emails:* AND brokers.phones:* }",
    "num_records":10
}

The key thing to note for these queries is that any sub-field requirements that you want to match within a single sub-object must be contained within curly brackets "{ }"

Range queries

Any fields that are dates, integers, or doubles will let you search them based on a range.

{
	"query": "dateAdded:[2017-01-01 TO 2017-02-01]"
}

will return all properties that have been added to the database between Jan 1, 2017 and Feb 2, 2017.

You can do unbounded range queries as well, like:

{
	"query": "dateAdded:[2017-01-01 TO *]"
}

This will return all properties have been added since Jan 1, 2017 until the current date.

You can also use comparison operators like >, >=, <=, and <. These are helpful when you want to search for products that are cheaper or more expensive than certain limits. E.g.:

{
	"query": "reviews.rating:>3"
}

returns all properties that have reviews greater than 3.

Excluding values

For some searches, you'll want to exclude certain values from returning. For example, let's say you wanted to find all listings, except for those in the US. You would use the - operator to negate US values:

{
	"query": "-country:US"
}

Searching by Address

You can use the API to search via the address field. For example, if you would like to find 2815 Manor Rd you could use the following query.

{
    "query":"address:\"2815 Manor Rd\" AND postalCode:78722"
}

However there are many different ways to approach searching via an address. You can learn more here about Search address in property or business data For more information on our postal code abbreviations, you can visit here: postal code abbreviations

Geo Queries

You can also use the API to do queries based around latitude and longitude values. For example, if you would like to find all properties within 10 miles of a specific point in Austin, Texas you could use the following query.

{
    "query":"geoLocation:[-97.7430600,30.2671500,10,mi]"
}

The format for the parameter values is: [ Longitude, Latitude, Distance, Distance Unit ]

You can also use the following units for measuring distance:

m - meters
mi - miles
ft - feet
in - yards
mm - millimeters
km - kilometers
NM - nautical miles
cm - centimeters

Count Feature

As an alternative or used for testing purposes you can set your num_records to 0 in your property search query. This is will only return the num_found of the query and will cost 0 credits to search. Try it out

{
  "query": "country:US",
  "num_records":0
}

📘

Count Feature

Please note that this is feature is only for paid accounts. So please check your account plan or contact [email protected].

Paging Over Results

As an alternative to running a download, you can also use the API to page through the data. This approach allows you to consume one chunk at a time.

POST https://api.datafiniti.co/v4/properties/paginate?page=1&limit=500
{
  "query": "keys:*"
}

The pagination endpoint uses the following parameters:

• page - You specify which chunk of data you would like to access. You can iterate the page to work your way through all of the results. You cannot paginate further than the 10,000th record.
• limit - This specifies the number of results you want returned within the page. The maximum number of results that can be returned per page is 500.