Some MLS Deals showing as Active, but are actually Closed
happening for a small subset of listings in sporadic sets of MLS boards e.g. San Diego MLS

RealEstateAPI About 1 year ago
High Priority
MLS Search & Detail APIs
Some MLS Deals showing as Active, but are actually Closed
happening for a small subset of listings in sporadic sets of MLS boards e.g. San Diego MLS

RealEstateAPI About 1 year ago
High Priority
MLS Search & Detail APIs
Increase Max # of Linked Properties that can be returned
current max is 50 in some cases there are more, so we will make some way to expose the remaining linked properties

RealEstateAPI About 1 year ago
High Priority
Property Search & Detail APIs
Increase Max # of Linked Properties that can be returned
current max is 50 in some cases there are more, so we will make some way to expose the remaining linked properties

RealEstateAPI About 1 year ago
High Priority
Property Search & Detail APIs
MLS Search - "public_property_use_code" accepted typing
only accepts integer type right now, add array[int] support like on Property Search, so compound queries not needed to search for multiple property use code types

RealEstateAPI About 1 year ago
High Priority
MLS Search & Detail APIs
MLS Search - "public_property_use_code" accepted typing
only accepts integer type right now, add array[int] support like on Property Search, so compound queries not needed to search for multiple property use code types

RealEstateAPI About 1 year ago
High Priority
MLS Search & Detail APIs
Property Detail Schema Update - add "taxExemptionCodes"
to help people be able to determine Homesteads

RealEstateAPI About 1 year ago
Property Search & Detail APIs
Property Detail Schema Update - add "taxExemptionCodes"
to help people be able to determine Homesteads

RealEstateAPI About 1 year ago
Property Search & Detail APIs
New Field - add field "buildingCondition"
useful for fix/flip & rehab use cases Property Search API Filter - “building_condition” AVERAGE FAIR GOOD EXCELLENT POOR UNSOUND Property Detail Response Field - “propertyInfo.buildingCondition”

RealEstateAPI About 1 year ago
Property Search & Detail APIs
New Field - add field "buildingCondition"
useful for fix/flip & rehab use cases Property Search API Filter - “building_condition” AVERAGE FAIR GOOD EXCELLENT POOR UNSOUND Property Detail Response Field - “propertyInfo.buildingCondition”

RealEstateAPI About 1 year ago
Property Search & Detail APIs
MLS Search - ids_only & listing_ids_only Flags
fix ids_only (bool) functionality to work similar to Property Search ids_only add listing_ids_only (bool) so users can do MLS Detail enrichment for a larger result set faster

RealEstateAPI About 1 year ago
High Priority
MLS Search & Detail APIs
MLS Search - ids_only & listing_ids_only Flags
fix ids_only (bool) functionality to work similar to Property Search ids_only add listing_ids_only (bool) so users can do MLS Detail enrichment for a larger result set faster

RealEstateAPI About 1 year ago
High Priority
MLS Search & Detail APIs
Increase Max # of boundaries that can be returned
the “polygon” field allows users to grab all property boundaries in their specified shape - however our system will only pull the first 1000 The fix would allow for paging more boundaries if desired

RealEstateAPI About 1 year ago
Low Priority
Property Boundary and Other Mapping APIs
Increase Max # of boundaries that can be returned
the “polygon” field allows users to grab all property boundaries in their specified shape - however our system will only pull the first 1000 The fix would allow for paging more boundaries if desired

RealEstateAPI About 1 year ago
Low Priority
Property Boundary and Other Mapping APIs
v3/PropertyComps Returning "NaN" for some queries
"input": { "address": "3415 Blossom St, Columbia SC 29205", "same_baths": true, "same_beds": true, "max_radius_miles": 2, "max_days_back": 90, "arms_length": true }, from response: "reapiAvm": "NaN", "reapiAvmLow": "NaN", "reapiAvmHigh": "NaN",

RealEstateAPI About 1 year ago
Comps & Other Valuation APIs
v3/PropertyComps Returning "NaN" for some queries
"input": { "address": "3415 Blossom St, Columbia SC 29205", "same_baths": true, "same_beds": true, "max_radius_miles": 2, "max_days_back": 90, "arms_length": true }, from response: "reapiAvm": "NaN", "reapiAvmLow": "NaN", "reapiAvmHigh": "NaN",

RealEstateAPI About 1 year ago
Comps & Other Valuation APIs
foreclosureInfo returns "active":true on historic foreclosures
When foreclosureInfo is present, a lot of records show “active”:true, even when it’s a historic record and we would expect an “active”:false Sample Data propertyCompsV3 call id:"37792942" foreclosureInfo : Array (5) 0 : Object seqNo : "2" foreclosureId : "15075336" FIPSCode : "33005" estimatedBankValue : "382000" recordingDate : "2013-03-11" documentType : "Order Rescheduling Foreclosure Sale Date" noticeType : "CS" trusteeSaleNumber : "206960" active : true 1 : Object seqNo : "4" foreclosureId : "14998989" FIPSCode : "33005" estimatedBankValue : "382000" judgmentDate : "2013-03-22" recordingDate : "2013-02-21" auctionDate : "2013-03-22" lenderName : "FNMA" lenderPhone : "603-524-4101" documentType : "Notice of Foreclosure Sale" noticeType : "FOR" trusteeSaleNumber : "206202" active : true 2 : Object seqNo : "3" foreclosureId : "15035096" FIPSCode : "33005" estimatedBankValue : "382000" recordingDate : "2013-03-04" documentType : "Order Rescheduling Foreclosure Sale Date" noticeType : "CS" trusteeSaleNumber : "206508" active : true

An Anonymous User About 1 year ago
Property Search & Detail APIs
foreclosureInfo returns "active":true on historic foreclosures
When foreclosureInfo is present, a lot of records show “active”:true, even when it’s a historic record and we would expect an “active”:false Sample Data propertyCompsV3 call id:"37792942" foreclosureInfo : Array (5) 0 : Object seqNo : "2" foreclosureId : "15075336" FIPSCode : "33005" estimatedBankValue : "382000" recordingDate : "2013-03-11" documentType : "Order Rescheduling Foreclosure Sale Date" noticeType : "CS" trusteeSaleNumber : "206960" active : true 1 : Object seqNo : "4" foreclosureId : "14998989" FIPSCode : "33005" estimatedBankValue : "382000" judgmentDate : "2013-03-22" recordingDate : "2013-02-21" auctionDate : "2013-03-22" lenderName : "FNMA" lenderPhone : "603-524-4101" documentType : "Notice of Foreclosure Sale" noticeType : "FOR" trusteeSaleNumber : "206202" active : true 2 : Object seqNo : "3" foreclosureId : "15035096" FIPSCode : "33005" estimatedBankValue : "382000" recordingDate : "2013-03-04" documentType : "Order Rescheduling Foreclosure Sale Date" noticeType : "CS" trusteeSaleNumber : "206508" active : true

An Anonymous User About 1 year ago
Property Search & Detail APIs
Property Search - "individually_owned" [bool] addition
similar to corporate_owned & trust_owned, individually_owned will filter against the deed data to only return properties that have an individual person as (one of) the owner(s)

RealEstateAPI About 1 year ago
Property Search & Detail APIs
Property Search - "individually_owned" [bool] addition
similar to corporate_owned & trust_owned, individually_owned will filter against the deed data to only return properties that have an individual person as (one of) the owner(s)

RealEstateAPI About 1 year ago
Property Search & Detail APIs
ownerInfo > mailAddress > unit and unitType don't match label
id 163201439 id 161282168 id 161019145 - for this one the data is there but unitType is not normalized

An Anonymous User About 1 year ago
Property Search & Detail APIs
ownerInfo > mailAddress > unit and unitType don't match label
id 163201439 id 161282168 id 161019145 - for this one the data is there but unitType is not normalized

An Anonymous User About 1 year ago
Property Search & Detail APIs
MLS Detail - "exact_match" with "address" search
similar to how “exact_match” works on Property Detail

RealEstateAPI About 1 year ago
High Priority
MLS Search & Detail APIs
MLS Detail - "exact_match" with "address" search
similar to how “exact_match” works on Property Detail

RealEstateAPI About 1 year ago
High Priority
MLS Search & Detail APIs
Add "taxLien" response field to Property Search API
so when filtering by taxLien and potentially other conditions in a compound query, being able to separate out the ones that are tax liens specifically

RealEstateAPI About 1 year ago
Property Search & Detail APIs
Add "taxLien" response field to Property Search API
so when filtering by taxLien and potentially other conditions in a compound query, being able to separate out the ones that are tax liens specifically

RealEstateAPI About 1 year ago
Property Search & Detail APIs
v3/PropertyComps Response Fields Type Inconsistencies w/ Property Detail schema fields of same name
need to make sure all v3 property comps fields have the same types as in Property Detail

RealEstateAPI About 1 year ago
Comps & Other Valuation APIs
v3/PropertyComps Response Fields Type Inconsistencies w/ Property Detail schema fields of same name
need to make sure all v3 property comps fields have the same types as in Property Detail

RealEstateAPI About 1 year ago
Comps & Other Valuation APIs
*** Missing data in Kokomo IN! INVESTOR BASE ****
No transaction data in Kokomo Indiana. There are transactions pulling in from 10mi outside of town but no data in town. there are for sure Investor Transactions in the area.

An Anonymous User About 21 hours ago
Property Search & Detail APIs
*** Missing data in Kokomo IN! INVESTOR BASE ****
No transaction data in Kokomo Indiana. There are transactions pulling in from 10mi outside of town but no data in town. there are for sure Investor Transactions in the area.

An Anonymous User About 21 hours ago
Property Search & Detail APIs
Establish Single Source of Truth for API Documentation - Unify Swagger/OpenAPI with Developer Docs
Problem: RealEstateAPI documentation is split across multiple sources with inconsistencies: Swagger spec: missing response schemas Markdown docs: have complete schemas but different examples Postman collections show different parameter formats Integration time increases 40-60% due to manual schema reconstruction and cross-referencing multiple sources. Ideally a version controlled GitHub repository or similar (ie what you have privately via readme.io) with the latest API specifications and schemas (for both requests and responses and examples, etc)

Jimmy Briggs 8 months ago
Feature Requests
Establish Single Source of Truth for API Documentation - Unify Swagger/OpenAPI with Developer Docs
Problem: RealEstateAPI documentation is split across multiple sources with inconsistencies: Swagger spec: missing response schemas Markdown docs: have complete schemas but different examples Postman collections show different parameter formats Integration time increases 40-60% due to manual schema reconstruction and cross-referencing multiple sources. Ideally a version controlled GitHub repository or similar (ie what you have privately via readme.io) with the latest API specifications and schemas (for both requests and responses and examples, etc)

Jimmy Briggs 8 months ago
Feature Requests
Expose Open House Data
add to MLS APIs Make homes w/ set open houses searchable show list of open houses if exists

RealEstateAPI 12 months ago
MLS Search & Detail APIs
Expose Open House Data
add to MLS APIs Make homes w/ set open houses searchable show list of open houses if exists

RealEstateAPI 12 months ago
MLS Search & Detail APIs
MLS Search - missing sold prices for 'Sold' Listings
2525 S Meade st, denver, co, 80219 -- listing id 350165139 255 n virginia st, salt lake city, ut 84103 -- listing id 328989824 2105 Lowell Boulevard, Denver, CO 80211 -- listing id 368769711 2315 N Quitman Street, Denver, CO 80212 -- listing id 334027008 7301 E Vista Dr, Scottsdale, AZ 85250 -- listing id 350394852 7026 E Chaparral Rd, Paradise Valley, AZ 85253 -- listing id 359636993

RealEstateAPI 12 months ago
MLS Search & Detail APIs
MLS Search - missing sold prices for 'Sold' Listings
2525 S Meade st, denver, co, 80219 -- listing id 350165139 255 n virginia st, salt lake city, ut 84103 -- listing id 328989824 2105 Lowell Boulevard, Denver, CO 80211 -- listing id 368769711 2315 N Quitman Street, Denver, CO 80212 -- listing id 334027008 7301 E Vista Dr, Scottsdale, AZ 85250 -- listing id 350394852 7026 E Chaparral Rd, Paradise Valley, AZ 85253 -- listing id 359636993

RealEstateAPI 12 months ago
MLS Search & Detail APIs
Property Search - mls_days_on_market_min/max not getting recent listings until 40+ days back
{ "live": true, "input": { "ids_only": false, "obfuscate": false, "summary": false, "size": 50, "count": true, "mls_active": true, "mls_days_on_market_min": 1, "mls_days_on_market_max": 30 }, "data": [], "count": 0, "statusCode": 404, "statusMessage": "Not Found", "requestExecutionTimeMS": "15ms" }

RealEstateAPI 12 months ago
Property Search & Detail APIs
Property Search - mls_days_on_market_min/max not getting recent listings until 40+ days back
{ "live": true, "input": { "ids_only": false, "obfuscate": false, "summary": false, "size": 50, "count": true, "mls_active": true, "mls_days_on_market_min": 1, "mls_days_on_market_max": 30 }, "data": [], "count": 0, "statusCode": 404, "statusMessage": "Not Found", "requestExecutionTimeMS": "15ms" }

RealEstateAPI 12 months ago
Property Search & Detail APIs