User Tools

Site Tools


incoming_leads_api

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
incoming_leads_api [2016/05/27 21:08]
igor [Property fields]
incoming_leads_api [2016/05/27 21:09]
igor [Property fields]
Line 144: Line 144:
 | ''​listing_status'' ​        | string ​ | optional | If the property is being sold this is the current status, any format is allowed. ex.: "For Sale" | | ''​listing_status'' ​        | string ​ | optional | If the property is being sold this is the current status, any format is allowed. ex.: "For Sale" |
 | ''​listing_days_on_market''​ | integer | optional | If the property has pending date, the number of days between list date and pending date. If the property has no pending date, but has a closing date, the number of days between list date and closing date.  If the property has no closing date, but has a list date, the number of days between list date and today. Otherwise, nothing| | ''​listing_days_on_market''​ | integer | optional | If the property has pending date, the number of days between list date and pending date. If the property has no pending date, but has a closing date, the number of days between list date and closing date.  If the property has no closing date, but has a list date, the number of days between list date and today. Otherwise, nothing|
 +| ''​list_date'' ​             | string ​ | optional | When this property was listed for sale. Format must be a combined date and time according to ISO 8601, ex.: “2015-04-01T08:​41:​51+00:​00” |
 | ''​estimated_value'' ​       | string ​ | optional | Estimated value this property could be sold for, useful for Seller or Potential Seller leads. ​ Could be from an automated or personalized valuation. ​ The supported format is a number with optional decimal places, ex.: "​100500"​ or "​100500.90"​ | | ''​estimated_value'' ​       | string ​ | optional | Estimated value this property could be sold for, useful for Seller or Potential Seller leads. ​ Could be from an automated or personalized valuation. ​ The supported format is a number with optional decimal places, ex.: "​100500"​ or "​100500.90"​ |
 | ''​last_sold_date'' ​        | string ​ | optional | Doesn'​t have any format requirement,​ could be something like ''"​2015-12-25"''​ | | ''​last_sold_date'' ​        | string ​ | optional | Doesn'​t have any format requirement,​ could be something like ''"​2015-12-25"''​ |
Line 151: Line 152:
 | ''​latitude'' ​              | float   | optional | | | ''​latitude'' ​              | float   | optional | |
 | ''​longitude'' ​             | float   | optional | | | ''​longitude'' ​             | float   | optional | |
-| ''​list_date'' ​             | string ​ | optional | When this property was listed for sale. Format must be a combined date and time according to ISO 8601, ex.: “2015-04-01T08:​41:​51+00:​00” | 
 | ''​year_built'' ​            | integer | optional | Year this property was built | | ''​year_built'' ​            | integer | optional | Year this property was built |
 ====== Example code ====== ====== Example code ======
incoming_leads_api.txt · Last modified: 2016/07/06 21:37 by igor