Pinal County, AZ parcel and infrastructure data API

Parcel coverage in Pinal County

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

Owner name and mailing address are returned by /v1/enrich with the owner group, at 2 credits per parcel instead of 1 credit. 94% of Pinal County records carry an owner name.

Infrastructure in and around Pinal County

Example requests for Pinal 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 15624 N KENWORTHY RD, COOLIDGE, AZ 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":"15624 N KENWORTHY RD, COOLIDGE, AZ","sections":["datacenters"]}' \
  https://api.korzy.co/v1/lookup

import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "15624 N KENWORTHY RD, COOLIDGE, AZ", "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": -111.54453602429524,
    "latitude": 33.02176085,
    "address": "15624 N KENWORTHY RD, COOLIDGE",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "04021-96a82e635c23e6645ca5",
        "korzy_id": "04021-96a82e635c23e6645ca5",
        "parcelid": "209050010",
        "parceladdr": "15624 N KENWORTHY RD",
        "parcelcity": "COOLIDGE",
        "situs_zip": "85128",
        "statefp": "04",
        "geoid": "04021",
        "longitude": -111.54453602429524,
        "latitude": 33.02176085,
        "usedesc": "Industrial",
        "taxacres": 50.25,
        "saledate": "2001-09-17",
        "updated": "2026-10-30"
      }
    ],
    "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 owner and sale fields

/v1/enrich returns the fields you choose for up to 25 parcels per request; here the parcel 04021-96a82e635c23e6645ca5, 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":"04021-96a82e635c23e6645ca5"}],"fields":["identity","sale","owner"]}' \
  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/04021-96a82e635c23e6645ca5

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

Pinal County data questions

How many parcels in Pinal County include last sale?

About 250,000 of about 280,000 parcel records (91%) include last sale.

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

Yes. 94% of Pinal 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 Pinal County?

Korzy tracks 6 data-center projects in Pinal County: 4 proposed and 2 permitted. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.

How much power generation is in Pinal County?

About 25 operable power plants in Pinal County total about 5,100 MW of nameplate capacity, mainly natural gas, solar and battery and pumped storage.

Which water systems serve Pinal County?

Service areas of about 75 community water systems cover about 15% of Pinal County, and sewer service areas cover about 3%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.

More featured counties

• Maricopa County, AZBorders Pinal County · about 1.8 million parcels
• Pima County, AZBorders Pinal County · about 450,000 parcels

All featured Arizona counties