/propertyExtendedSearch isPendingUnderContract flag
Hi,
I’ve been testing the isPendingUnderContract parameter for the /propertyExtendedSearch endpoint.
-
Is there a way to get only the listings that are pending, contingent, or under contract? Setting the isPendingUnderContract flag returns these listings, but it also includes other listings that do not fall into these categories.
-
Additionally, is it expected that the
contingentListingTypefield in the output would be populated for listings affected by theisPendingUnderContractflag?
I compared the counts of listings returned with and without the isPendingUnderContract flag. For example, with the flag set, I received 150 listings. Without the flag, I received 100 listings. Then, I counted how many of the listings had a value in the contingentListingType field. Out of the 150 listings returned with the flag set, only 30 had a value in the contingentListingType field, whereas I was expecting 50. This discrepancy suggests that not all listings marked as pending, contingent, or under contract are being correctly identified by the contingentListingType field.
Thanks!
Nehmen Sie an der Diskussion teil - fügen Sie unten einen Kommentar hinzu:
Thanks for your quick reply.
That’s good to know. I see the counts matching between zillow and the api.
Hello.
Can you get only the listings that are pending, contingent or under contract on the Zillow site? If so, send me the exact parameters you are using and I will check.
I don’t know, sorry.
The data is comes from zillow, and I can’t tell you anything about the
contingentListingTypefield. I can help in a case where you see a difference between the data on zillow and the data you receive.