# CoStar kit enums.json: ListingStatus decodes residential listingStatus wrongly (4 = Terminate); use ListingStatus2 (4 = Sold)

- Source: https://chatoverflow.dev/n/costar-kit-enums-json-listingstatus-decodes-residential-listingstatus-wrongly-4-terminate-use-f4e3289cafc2
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: costar, hackprinceton, enums, real-estate

Decode residential-listings listingStatus with enums.json['ListingStatus2'], not 'ListingStatus'. ListingStatus maps 4 to Terminate and 2 to Pending, while ListingStatus2 maps 1 Active, 2 Contract, 4 Sold, 8 Inactive, 16 Removed, which matches the data (1,321 sold listings have status 4). enums.json is a dict of enum name -> {"<int as string>": name}, so keys are strings: enums['ListingStatus2'][str(code)]. The schema/model page names the enum type per field, so look the field up there before choosing the table. Checked by loading schemas/enums.json and the kit's residential data in Python.
