Bergen County, NJ parcel and infrastructure data API

Parcel coverage in Bergen County

About 300,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from July 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:

Bergen County records do not include owner names. See pricing for credit costs.

Infrastructure in and around Bergen County

Example requests for Bergen 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 nearby data-center projects

/v1/lookup matches 140 FOREST AVE, PARAMUS, NJ and returns the parcel's korzy_id and record, plus the data-center projects within 10 km, nearest first. 2 credits.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address":"140 FOREST AVE, PARAMUS, NJ","sections":["datacenters"]}' \
  https://api.korzy.co/v1/lookup

import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "140 FOREST AVE, PARAMUS, NJ", "sections": ["datacenters"]},
    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"]["datacenters"]["status"])

{
  "location": {
    "longitude": -74.05058845486944,
    "latitude": 40.925274000051246,
    "address": "140 FOREST AVE, PARAMUS",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "34003-2e949fcca8b9e7fa1c71",
        "korzy_id": "34003-2e949fcca8b9e7fa1c71",
        "parcelid": "0246_2710_7",
        "parceladdr": "140 FOREST AVE",
        "parcelcity": "PARAMUS",
        "situs_zip": "07652",
        "statefp": "34",
        "geoid": "34003",
        "longitude": -74.05058845486944,
        "latitude": 40.925274000051246,
        "usedesc": "Church & Charitable (Exempt)",
        "land_use_code": "15D",
        "yearbuilt": 1973,
        "bldgsqft": 14414,
        "taxacres": 1.86,
        "totalvalue": 3482100,
        "land_value_usd": 1387500,
        "improvement_value_usd": 2094600,
        "saledate": "1998-04-09",
        "saleamt": 0,
        "updated": "2025-10-21"
      }
    ],
    "truncated": false
  },
  "sections": {
    "datacenters": {
      "status": "ok",
      "data": {
        "radius_km": 10,
        "truncated": false,
        "note": "Straight-line distance to the reported project point; inspect location_precision. Projects merge supported source matches, not every nearby building. Approximate locations do not identify a parcel. Reported IT load, facility power, planned capacity and estimates remain separate source claims. No record or unknown status does not establish absence or inactivity."
      },
      "provenance": [
        {
          "dataset": "datacenters",
          "as_of": "2026-11-02",
          "data_version": "20261102T123021962884Z"
        }
      ]
    }
  },
  "credits": {
    "charged": 2,
    "refunded": 0
  }
}

2. Add value and sale fields

/v1/enrich returns the fields you choose for up to 25 parcels per request; here the parcel 34003-2e949fcca8b9e7fa1c71. 1 credit.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items":[{"korzy_id":"34003-2e949fcca8b9e7fa1c71"}],"fields":["identity","value","sale"]}' \
  https://api.korzy.co/v1/enrich

3. 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/34003-2e949fcca8b9e7fa1c71

const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("34003-2e949fcca8b9e7fa1c71")}`, {
  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);

Bergen County data questions

How many parcels in Bergen County include year built?

About 260,000 of about 300,000 parcel records (86%) include year built.

Does the Korzy API return owner names for Bergen County parcels?

Bergen County parcel records do not include owner names. Values, land use and building facts are returned where the county publishes them.

How many data-center projects are in Bergen County?

Korzy tracks 5 data-center projects in Bergen County: 3 operating, 1 proposed and 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 Bergen County?

8 operable power plants in Bergen County total about 1,400 MW of nameplate capacity, mainly natural gas, battery and pumped storage and solar.

Which water systems serve Bergen County?

Service areas of about 30 community water systems cover about 79% of Bergen County, and sewer service areas cover about 80%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.

More featured counties

• Hudson County, NJBorders Bergen County · about 150,000 parcels
• Passaic County, NJBorders Bergen County · about 130,000 parcels
• New York County, NYBorders Bergen County · about 180,000 parcels
• Rockland County, NYBorders Bergen County · about 93,000 parcels
• Westchester County, NYBorders Bergen County · about 250,000 parcels
• Middlesex County, NJabout 280,000 parcels

All featured New Jersey counties