February 2026
The Property Search API now supports filtering by metropolitan statistical area — including CBSA, CSA, and Metro Division codes and names. These filters let you target properties within specific metro areas defined by the U.S. Census Bureau, giving you a precise way to search by market geography.
What Are Metro Area Filters?
The U.S. Census Bureau defines three levels of metropolitan geography that group counties into economic regions:
Level | Filter Fields | Description |
CBSA (Core Based Statistical Area) |
| Metropolitan and micropolitan areas — the most commonly used metro boundary (e.g., "Phoenix-Mesa-Chandler, AZ") |
CSA (Combined Statistical Area) |
| Larger regions that combine adjacent CBSAs with significant commuting ties (e.g., "Phoenix-Mesa, AZ" CSA includes both Phoenix and Prescott metros) |
Metro Division |
| Subdivisions within large CBSAs that have distinct employment centers (e.g., Atlanta CBSA splits into "Atlanta-Sandy Springs-Roswell" and "Marietta-Roswell-Sandy Springs" divisions) |
How they relate:
CSA (broadest — combined metros)
└── CBSA (individual metro area)
└── Metro Division (sub-area within large metros)
Not all metros have divisions — only the largest CBSAs (like Atlanta, New York, and Dallas) are subdivided. Most CBSAs (like Phoenix) are a single unit.
Why This Matters
Traditional property searches rely on city, county, or zip code boundaries. Metro area filters give you a way to search by economic market boundaries instead — the same boundaries used by real estate analysts, lenders, and government agencies to define housing markets.
This is especially useful when:
Targeting an entire metro market — Search all properties in the Phoenix metro without listing every city and zip code
Comparing sub-markets — Use Metro Division filters to distinguish between the Atlanta core and outer suburbs like Marietta
Building regional portfolios — Use CSA filters to capture a broader economic region including satellite metros
How to Use
All six filters are available under searchCriteria.address and support standard string operators: equals, contains, startsWith, inList, and notInList.
Search by CBSA (Metro Area)
Find properties in the Phoenix metro area:
{
"searchCriteria": {
"query": "AZ",
"address": {
"cbsaTitle": {
"contains": "Phoenix"
}
}
}
}
Or use the numeric CBSA code directly:
{
"searchCriteria": {
"query": "AZ",
"address": {
"cbsaCode": {
"equals": "38060"
}
}
}
}
Search by CSA (Combined Statistical Area)
Find properties across the broader Phoenix-Mesa combined region:
{
"searchCriteria": {
"query": "AZ",
"address": {
"csaCode": {
"equals": "429"
}
}
}
}
Search by Metro Division
Find properties in a specific sub-market within a large metro. For example, the Atlanta-Sandy Springs-Roswell division within the Atlanta CBSA:
{
"searchCriteria": {
"query": "GA",
"address": {
"metroDivisionCode": {
"equals": "12054"
}
}
}
}
Combine with Other Filters
Metro area filters work alongside all existing search filters. For example, find 3+ bedroom single-family homes in the Atlanta metro:
{
"searchCriteria": {
"query": "GA",
"address": {
"cbsaTitle": {
"contains": "Atlanta"
}
},
"building": {
"bedroomCount": {
"min": 3
}
},
"general": {
"propertyTypeDetail": {
"equals": "Single Family Residential"
}
}
}
}
Common Metro Area Codes
Here are codes for some frequently searched markets:
Metro Area | CBSA Code | CBSA Title | CSA Code |
Phoenix, AZ | 38060 | Phoenix-Mesa-Chandler, AZ | 429 |
Atlanta, GA | 12060 | Atlanta-Sandy Springs-Roswell, GA | 122 |
Dallas, TX | 19100 | Dallas-Fort Worth-Arlington, TX | 206 |
Los Angeles, CA | 31080 | Los Angeles-Long Beach-Anaheim, CA | 348 |
New York, NY | 35620 | New York-Newark-Jersey City, NY-NJ-PA | 408 |
Chicago, IL | 16980 | Chicago-Naperville-Elgin, IL-IN-WI | 176 |
Houston, TX | 26420 | Houston-The Woodlands-Sugar Land, TX | 288 |
Miami, FL | 33100 | Miami-Fort Lauderdale-Pompano Beach, FL | 370 |
For a complete list of CBSA, CSA, and Metro Division codes, see the U.S. Census Bureau Metropolitan Delineation Files.
No Code Changes Required
These filters were already supported by the API and are now documented in the Property Search API specification. Your existing integrations will continue to work as expected.
Questions?
Contact our support team at support@batchservice.com or visit https://help.batchdata.io for more information.
