Anoka County, MN parcel and infrastructure data API
Korzy has about 150,000 parcel records for Anoka County, Minnesota, with source updates through November 2026. 93% include values and 92% include last sale. In and around the county the API also maps 1 data-center project; 2 power plants with 9 MW of capacity, led by battery and pumped storage; and about 70 miles of active rail. Look up any parcel by address or coordinates, then check water, sewer and infrastructure context at the same point.
Parcel coverage in Anoka County
About 150,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from November 2026. Each record has a stable korzy_id you can store and look up again with /v1/records/{id}. Share of records with each field:
| Field | Coverage | Share |
|---|---|---|
| Situs address | Nearly all · 99% | |
| Owner name | Most · 89% | |
| Assessed or market value | Most · 93% | |
| Year built | Most · 81% | |
| Building size | Most · 89% | |
| Last sale | Most · 92% | |
| Land use | Most · 88% | |
| Zoning | Not published |
Owner name and mailing address are returned by /v1/enrich with the owner group, at 2 credits per parcel instead of 1 credit. 89% of Anoka County records carry an owner name.
Infrastructure in and around Anoka County
Power plants
2 operable plants with 9 MW of nameplate capacity; largest by capacity: battery and pumped storage, solar.
Within 50 km: /v1/lookup section power; details: /v1/records/{id}
Substations and transmission
About 50 in-service substations, 5 rated 230 kV or higher.
About 280 miles of transmission lines: about 130 mi at under 100 kV; about 25 mi at 100–161 kV; about 45 mi at 220–287 kV; about 55 mi at 345 kV.
Water and sewer service
Service areas of about 40 community water systems cover about 22% of the county.
Sewer service areas of 5 systems cover about 32%.
At an address or point: /v1/lookup section utilities
Data-center projects
1 tracked project: 1 status not reported.
Within 10 km: /v1/lookup section datacenters
Flood zones and wetlands
Special flood hazard areas cover about 26% of the county on the current federal flood maps, published October 2026.
Mapped wetlands cover about 24%.
At an address or point: /v1/lookup section environment
Rail, ports and freight
- About 70 miles of active rail, about 40 of it main line
- About 25 miles of national freight network highway
Within 25 km: /v1/lookup section logistics
Example requests for Anoka County
The lookup response is a real production response, trimmed to the main fields. Every request needs an API key with api:read; see authentication and credits and limits.
1. Find a parcel and its water and sewer service
/v1/lookup matches 12471 Larch Street Northwest, Minneapolis, MN and returns the parcel's korzy_id and record, plus the water and sewer service areas at the parcel and the nearest treatment plants. 2 credits.
curl --fail-with-body -sS \
-H "Authorization: Bearer $KORZY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"address":"12471 Larch Street Northwest, Minneapolis, MN","sections":["utilities"]}' \
https://api.korzy.co/v1/lookupPython
import os
import requests
response = requests.post(
"https://api.korzy.co/v1/lookup",
json={"address": "12471 Larch Street Northwest, Minneapolis, MN", "sections": ["utilities"]},
headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
timeout=60,
)
response.raise_for_status()
body = response.json()
parcel = body["parcels"]["records"][0]
print(parcel["korzy_id"], body["sections"]["utilities"]["status"])Production response (trimmed)
{
"location": {
"longitude": -93.28090110263372,
"latitude": 45.19591385,
"address": "12471 Larch Street Northwest, Minneapolis",
"match_type": "exact"
},
"parcels": {
"records": [
{
"id": "27003-99f8256617aae67657f9",
"korzy_id": "27003-99f8256617aae67657f9",
"parcelid": "123124210058",
"parceladdr": "12471 Larch Street Northwest",
"parcelcity": "Minneapolis",
"situs_zip": "55448",
"statefp": "27",
"geoid": "27003",
"longitude": -93.28090110263372,
"latitude": 45.19591385,
"usedesc": "Charitable Institution",
"yearbuilt": 1994,
"bldgsqft": 1296,
"taxacres": 0,
"totalvalue": 394700,
"land_value_usd": 97000,
"improvement_value_usd": 297700,
"market_value_usd": 394700,
"saledate": "2009-07-23",
"saleamt": 235000,
"updated": "2026-11-03"
}
],
"truncated": false
},
"sections": {
"utilities": {
"status": "ok",
"data": {
"water": [
{
"id": "utility:water:37287",
"feature_id": "water:37287",
"name": "Coon Rapids",
"boundary_basis": "System Sourced"
}
],
"sewer": [
{
"id": "utility:sewer:988",
"feature_id": "sewer:988",
"name": "METROPOLITAN WWTP",
"boundary_basis": "Sourced"
}
],
"treatment_plants": [
{
"id": "utility:treatment:14788",
"feature_id": "treatment:14788",
"name": "MCES East Bethel WWTF",
"distance_km": 12.499167298270338
},
{
"id": "utility:treatment:7103",
"feature_id": "treatment:7103",
"name": "EAST BETHEL CS",
"distance_km": 15.029809872591102
},
{
"id": "utility:treatment:151",
"feature_id": "treatment:151",
"name": "OTSEGO EAST WWTP",
"distance_km": 20.445814781710396
}
],
"truncated": {
"water": false,
"sewer": false
}
},
"provenance": [
{
"dataset": "water",
"data_version": "63b7c1c3-9661-4fed-a59f-ddbfff80c2e4"
},
{
"dataset": "sewer",
"data_version": "63b7c1c3-9661-4fed-a59f-ddbfff80c2e4"
},
{
"dataset": "treatment",
"data_version": "63b7c1c3-9661-4fed-a59f-ddbfff80c2e4"
}
]
}
},
"credits": {
"charged": 2,
"refunded": 0
}
}2. Add owner and sale fields
/v1/enrich returns the fields you choose for up to 25 parcels per request; here the parcel 27003-99f8256617aae67657f9, with the owner group. 2 credits.
curl --fail-with-body -sS \
-H "Authorization: Bearer $KORZY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"items":[{"korzy_id":"27003-99f8256617aae67657f9"}],"fields":["identity","sale","owner"]}' \
https://api.korzy.co/v1/enrich3. Fetch the record again by ID
/v1/records/{id} returns the stored parcel's full record, without owner fields. 1 credit.
curl --fail-with-body -sS \
-H "Authorization: Bearer $KORZY_API_KEY" \
https://api.korzy.co/v1/records/27003-99f8256617aae67657f9JavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("27003-99f8256617aae67657f9")}`, {
headers: { Authorization: `Bearer ${process.env.KORZY_API_KEY}` },
});
if (!response.ok) throw new Error(`Korzy API ${response.status}`);
const { record } = await response.json();
console.log(record.parceladdr, record.usedesc);Anoka County data questions
- How many parcels in Anoka County include year built?
- About 120,000 of about 150,000 parcel records (81%) include year built.
- Does the Korzy API return owner names for Anoka County parcels?
- Yes. 89% of Anoka County parcel records carry an owner name. Ask /v1/enrich for the owner group; each parcel then costs 2 credits instead of 1 credit. Lookups and records never include owner fields.
- How many data-center projects are in Anoka County?
- Korzy tracks 1 data-center project in Anoka County: 1 status not reported. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.
- How much power generation is in Anoka County?
- 2 operable power plants in Anoka County total 9 MW of nameplate capacity, mainly battery and pumped storage and solar.
- Which water systems serve Anoka County?
- Service areas of about 40 community water systems cover about 22% of Anoka County, and sewer service areas cover about 32%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.
More featured counties
- Hennepin County, MNBorders Anoka County · about 450,000 parcels
- Ramsey County, MNBorders Anoka County · about 170,000 parcels
- Washington County, MNBorders Anoka County · about 130,000 parcels
- Dakota County, MNabout 170,000 parcels
- St. Louis County, MNabout 190,000 parcels
Build on Anoka County parcel data
Lookups, enrichment and records work the same in every county Korzy covers. Credits are shared across parcels, utilities, environment, logistics, power, grid, data-center and terrain sections.