Transit Lines - Qwady Docs

transitLines is not a current Borough search parameter. This page is kept so older references resolve cleanly, but line-by-line transit filtering is not part of the live contract today.

What to use instead

minTransitScore for building-level transit accessibility filtering. It only matches listings Borough has linked to their building, which happens when it loads a listing’s full detail, so listings without that link are left out even when their building qualifies.
areas for neighborhood and borough scoping
building score detail endpoints when you need the current transit score itself

Current status

These requests are common, but they are not current Borough filters:

transitLines
prewar
view-style amenity enums such as CITY_VIEW or WATER_VIEW

Search does not reject transitLines or prewar: it ignores them and returns results as if they were not passed. The SDK drops them before sending the request. Instead of line filtering, you can filter by transit accessibility score:

# Listings with excellent transit access
curl "https://borough.qwady.app/v1/search/rentals?minTransitScore=80"

Transit scores (0-100) are available on building detail responses via GET /v1/building/{id}/scores. The score is computed from public GTFS stop data (MTA subway, bus, LIRR, and Metro-North, plus NYC Ferry and the Staten Island Ferry). Points are added per mode, and the total is capped at 100:

Component	Max points	Radius
Subway proximity (distance to the nearest stop)	40	800 m
Subway density (stops within the radius; full points at 15 or more)	25	800 m
LIRR / Metro-North proximity	15	1,000 m
Ferry proximity	10	800 m
Bus proximity	12	400 m
Bus density (stops within the radius; full points at 7 or more)	8	400 m

The components add up to 110 before the cap, so a building does not need every mode to reach 100. See Building Scores for details on how scores are computed.