Ramsey County, MN parcel and infrastructure data API

Korzy has about 170,000 parcel records for Ramsey County, Minnesota, with source updates through November 2026. Nearly every record carries owner names, values, last sale, land use and building size; 93% include year built. In and around the county the API also maps 2 data-center projects (1 operating); 4 power plants with about 700 MW of capacity, led by natural gas; and 1 port with reported cargo. Look up any parcel by address or coordinates, then check water, sewer and infrastructure context at the same point.

Parcel coverage in Ramsey County

About 170,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 /api/parcel-record. Share of records with each field:

FieldCoverageShare
Situs addressNearly all · 100%
Owner nameNearly all · 95%
Assessed or market valueNearly all · 99%
Year builtMost · 93%
Building sizeNearly all · 95%
Last saleNearly all · 98%
Land useNearly all · 99%
ZoningNot published

Owner name and mailing address are returned with include_owner=true, which doubles a request's cost: a parcel record costs 2 credits instead of 1. 95% of Ramsey County records carry an owner name.

Infrastructure in and around Ramsey County

Power plants

4 operable plants with about 700 MW of nameplate capacity; largest by capacity: natural gas, battery and pumped storage, other fuels.

Plant details: /api/power/plants/{plant_id}

Substations and transmission

About 30 in-service substations, 2 rated 230 kV or higher.

About 130 miles of transmission lines: about 80 mi at 100–161 kV; 1 mi at 220–287 kV; about 40 mi at 345 kV.

Water and sewer service

Service areas of about 25 community water systems cover about 81% of the county.

Sewer service areas of 1 system cover about 82%.

At a point: /api/utilities/context

Data-center projects

2 tracked projects: 1 operating, 1 status not reported.

Within 10 km of a point: /api/datacenters/context

Flood zones and wetlands

Special flood hazard areas cover about 17% of the county on the current federal flood maps, published October 2026.

Mapped wetlands cover about 7%.

Rail, ports and freight

  • About 160 miles of active rail, about 90 of it main line
  • About 50 miles of national freight network highway
  • 1 port area with reported cargo tonnage
  • 1 intermodal rail terminal

Within 25 km of a point: /api/logistics/context

Example requests for Ramsey County

Real responses from the production API, trimmed to the main fields. Every request needs an API key with api:read; see authentication and credits and limits.

1. Find a parcel by address

/api/search matches 5 Mackubin Street, St Paul, MN and returns the parcel's korzy_id, coordinates and record. 1 credit.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'q=5 Mackubin Street, St Paul, MN' \
  https://api.korzy.co/api/search
Python
import os
import requests

response = requests.get(
    "https://api.korzy.co/api/search",
    params={"q": "5 Mackubin Street, St Paul, MN"},
    headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
    timeout=30,
)
response.raise_for_status()
parcel = response.json()["results"][0]
print(parcel["korzy_id"], parcel["longitude"], parcel["latitude"])
Response (trimmed)
{
  "results": [
    {
      "korzy_id": "27123-d9566fdbc09249386b9b",
      "address": "5 Mackubin Street",
      "city": "St Paul",
      "postcode": "55102",
      "county": "Ramsey",
      "statefp": "27",
      "longitude": -93.12154159811622,
      "latitude": 44.94166965,
      "match_type": "exact",
      "parcelid": "012823230186",
      "parceladdr": "5 Mackubin Street",
      "parcelcity": "St Paul",
      "situs_zip": "55102",
      "usedesc": "5e Charitable Institution",
      "yearbuilt": 1894,
      "bldgsqft": 6893,
      "taxacres": 0.35,
      "totalvalue": 1140400,
      "land_value_usd": 309100,
      "improvement_value_usd": 745000,
      "market_value_usd": 1054100,
      "saledate": "2015-07-29",
      "saleamt": 1250000,
      "updated": "2026-11-03",
      "geoid": "27123"
    }
  ],
  "truncated": false
}

With include_owner=true (2 credits) the record adds owner fields, shown here as placeholders:

{
  "owner_name": "EXAMPLE HOLDINGS LLC",
  "owner_mailing_address": "100 EXAMPLE ST, SAMPLE CITY, ST 00000"
}

2. Look up the parcel at a point

/api/query/point returns every parcel whose boundary covers the coordinates; here it returns the same record, 27123-d9566fdbc09249386b9b, in records. 1 credit per 10 records requested.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-93.121542' \
  --data-urlencode 'latitude=44.94167' \
  --data-urlencode 'limit=5' \
  https://api.korzy.co/api/query/point
JavaScript
const params = new URLSearchParams({"longitude": "-93.121542", "latitude": "44.94167", "limit": "5"});
const response = await fetch(`https://api.korzy.co/api/query/point?${params}`, {
  headers: { Authorization: `Bearer ${process.env.KORZY_API_KEY}` },
});
if (!response.ok) throw new Error(`Korzy API ${response.status}`);
const { records } = await response.json();
console.log(records.map((record) => record.korzy_id));

3. Check water and sewer service

/api/utilities/context returns the water and sewer service areas at the point and the nearest treatment plants. 1 credit.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-93.121542' \
  --data-urlencode 'latitude=44.94167' \
  https://api.korzy.co/api/utilities/context
Python
import os
import requests

response = requests.get(
    "https://api.korzy.co/api/utilities/context",
    params={"longitude": "-93.121542", "latitude": "44.94167"},
    headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
    timeout=30,
)
response.raise_for_status()
matches = response.json()["matches"]
print([area["name"] for area in matches["water"]])
Response (trimmed)
{
  "longitude": -93.121542,
  "latitude": 44.94167,
  "matches": {
    "water": [
      {
        "feature_id": "water:37577",
        "name": "Saint Paul Regional Water Services",
        "boundary_basis": "System Sourced"
      }
    ],
    "sewer": [
      {
        "feature_id": "sewer:988",
        "name": "METROPOLITAN WWTP",
        "boundary_basis": "Sourced"
      }
    ]
  },
  "nearby_treatment": [
    {
      "feature_id": "treatment:7077",
      "name": "METROPOLITAN WWTP",
      "distance_km": 6.254483573116852
    },
    {
      "feature_id": "treatment:7079",
      "name": "SENECA TREATMENT WWTF",
      "distance_km": 14.635899455874396
    }
  ]
}

Ramsey County data questions

How many parcels in Ramsey County include year built?
About 160,000 of about 170,000 parcel records (93%) include year built.
Does the Korzy API return owner names for Ramsey County parcels?
Yes. 95% of Ramsey County parcel records carry an owner name. Add include_owner=true to a point, search or parcel-record request; it doubles the request's cost, so a single parcel record costs 2 credits.
How many data-center projects are in Ramsey County?
Korzy tracks 2 data-center projects in Ramsey County: 1 operating and 1 status not reported. /api/datacenters/context lists projects within 10 km of any point.
How much power generation is in Ramsey County?
4 operable power plants in Ramsey County total about 700 MW of nameplate capacity, mainly natural gas, battery and pumped storage and other fuels.
Which water systems serve Ramsey County?
Service areas of about 25 community water systems cover about 81% of Ramsey County, and sewer service areas cover about 82%. /api/utilities/context returns the water and sewer matches at a point.

More featured counties

All featured Minnesota counties

Build on Ramsey County parcel data

Search, point and record lookups work the same in every county Korzy covers. Credits are shared across parcels, utilities, environment, logistics and data-center routes.