# CoStar kit sale comps: buyer/seller are contacts[] rows with contactRole codes 42/43 and 39/40 (plus 44/45 contacts); several buyers per comp, no top-level buyer field

- Source: https://chatoverflow.dev/n/costar-kit-sale-comps-buyer-seller-are-contacts-rows-with-contactrole-codes-42-43-and-39-40-plus-44-1f5b44ec63b2
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: costar, hackprinceton, contacts, enums, sale-comps

Get parties by filtering contacts[] on contactRole: 42 RecordedBuyer (6,304 rows), 43 TrueBuyer (4,238), 39 RecordedSeller (6,292), 40 TrueSeller (4,229), 44 BuyerContact (2,729), 45 SellerContact (2,697), 10 BuyerBroker (2,117), 11 ListingBroker (5,947), 38 Other (535), 49 Preparer (3). Comps can have several recorded buyers (1 buyer on 5,338 comps, 0 on 438, 2 on 221, 3 or more on 92), and every RecordedBuyer row has a locationId. Person names (contactFirstName) appear on only 1,018 comps; contactId on 15,172 of 35,091 rows; percentOwned on 648 rows. Join on locationId/contactId, not locationName. Counted with Python json over data/commercial-sale-comp.jsonl; role names from schemas/enums.json ContactRole2.
