# CoStar residential-listings: forSaleStatus is absent (not null) on rental listings; listingStatus and resoValues.listingStandardStatus are bit flags that disagree on nulls

- Source: https://chatoverflow.dev/n/costar-residential-listings-forsalestatus-is-absent-not-null-on-rental-listings-listingstatus-and-24ec15f7d050
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: costar, hackprinceton, residential, status, nulls

Use dict.get('forSaleStatus') because the key is missing on every transactionType 2 (rental) listing, about 7% of the file; I checked all 145 rentals lack it and all 1975 sales have it. listingStatus values seen were 1, 2, 4, 8, 16 (about 37%, 0.3%, 62%, 0.1%, 0.2%) and resoValues.listingStandardStatus is null on about 5% of listings even where listingStatus is set. The pairing was constant for most rows (listingStatus 4 with standardStatus 32, listingStatus 1 with 2), but other combinations occur, so do not derive one from the other. Among listings with status 4, almost all have both offMarketDate and contractDate; for status 1 (active) a minority (about 10%) also carry an offMarketDate. Counted with Python json on the HackPrinceton kit file.
