ZIP Demographics API GET

ZIP Demographics provides detailed demographic data for any US ZIP code including population, income, education, housing, employment, and racial composition from the US Census American Community Survey.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/zipdemographics

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // ZIP Demographics response payload
  }
}

About the ZIP Demographics API

ZIP Demographics uses 5-year American Community Survey (ACS) estimates from the US Census Bureau, providing reliable demographic data for all 33,000+ ZIP Code Tabulation Areas (ZCTAs) in the United States.

What people use it for

Market Research: Analyze demographics for market segmentation and targeting
Real Estate: Evaluate neighborhoods for real estate investment and valuation
Site Selection: Choose business locations based on demographic profiles
Ad Targeting: Build demographic profiles for advertising and personalization

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use ZIP Demographics

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the ZIP Demographics API.

Read the docs →

What does the ZIP Demographics API do?

How do I authenticate ZIP Demographics API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the ZIP Demographics API cost?

Each call spends 10 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the ZIP Demographics API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the ZIP Demographics API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the ZIP Demographics API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/zipdemographics

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`zip`Required	string	`90210`	5-digit US ZIP code length 5-5

Example request

1
2

curl "https://api.apiverve.com/v1/zipdemographics?zip=90210" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/zipdemographics

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "zip": "90210",
    "name": "ZCTA5 90210",
    "acsYear": 2022,
    "population": {
      "total": 21741,
      "male": 10234,
      "female": 11507,
      "medianAge": 45.3
    },
    "income": {
      "medianHousehold": 153891,
      "perCapita": 98234
    },
    "housing": {
      "medianHomeValue": 2875000,
      "medianRent": 3250,
      "totalUnits": 10234,
      "homeOwnershipRate": 63.2
    },
    "education": {
      "collegeEducatedPct": 72.4
    },
    "employment": {
      "laborForce": 11234,
      "unemploymentRate": 3.8
    },
    "race": {
      "white": {
        "count": 16892,
        "percent": 77.7
      },
      "asian": {
        "count": 2345,
        "percent": 10.8
      }
    },
    "formatted": {
      "medianHouseholdIncome": "$153,891",
      "perCapitaIncome": "$98,234",
      "medianHomeValue": "$2,875,000",
      "medianRent": "$3,250"
    }
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`zip`	string	`"90210"`	ZIP Code Tabulation Area identifier
`name`	string	`"ZCTA5 90210"`	ZCTA descriptive name
`acsYear`	number	`2022`	American Community Survey year used for data
`population`	object	`{...}`
`total`	number	`21741`	Total population count in ZIP code
`male`Premium	number	`10234`	Male population count
`female`Premium	number	`11507`	Female population count
`medianAge`Premium	number	`45.3`	Median age of population in years
`income`	object	`{...}`
`medianHousehold`	number	`153891`	Median household income in dollars
`perCapita`Premium	number	`98234`	Per capita income in dollars
`housing`	object	`{...}`
`medianHomeValue`Premium	number	`2875000`	Median home value in dollars
`medianRent`Premium	number	`3250`	Median rent price in dollars
`totalUnits`Premium	number	`10234`	Total housing units in area
`homeOwnershipRate`Premium	number	`63.2`	Percentage of homes owner-occupied
`education`	object	`{...}`
`collegeEducatedPct`Premium	number	`72.4`	Percentage with college degree or higher
`employment`	object	`{...}`
`laborForce`Premium	number	`11234`	Total labor force population count
`unemploymentRate`Premium	number	`3.8`	Unemployment rate as percentage
`race`	object	`{...}`
`white`	object	`{...}`
`count`Premium	number	`16892`	White population count
`percent`Premium	number	`77.7`	White population percentage
`asian`	object	`{...}`
`count`Premium	number	`2345`	Asian population count
`percent`Premium	number	`10.8`	Asian population percentage
`formatted`Premium	object	`{...}`	Human-readable formatted currency values
`medianHouseholdIncome`Premium	string	`"$153,891"`
`perCapitaIncome`Premium	string	`"$98,234"`
`medianHomeValue`Premium	string	`"$2,875,000"`
`medianRent`Premium	string	`"$3,250"`

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	ZIP Demographics calls	Per 1,000 calls
Free	Free	200	20	Free
Starter	$29.99	200,000	20,000	$1.50
Pro	$99.99	1,000,000	100,000	$1.00
Mega	$299.99	4,000,000	400,000	$0.75

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/zipdemographics

No SDK to install — this is a plain HTTPS call to /v1/zipdemographics with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/zipdemographics" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/zipdemographics-apiSource, issues and the examples this page is built from.ReferenceZIP Demographics API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/zipdemographicsnpm APIVerve.API.ZIPDemographicsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/zipdemographics

Install the Node.js SDK, then call the ZIP Demographics API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/zipdemographics

Node.js

const res = await fetch("https://api.apiverve.com/v1/zipdemographics", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/zipdemographicsThe published Node.js client, versioned and signed.GitHubapiverve/zipdemographics-apiSource, issues and the examples this page is built from.ReferenceZIP Demographics API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.ZIPDemographicsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/zipdemographics

No SDK to install — this is a plain HTTPS call to /v1/zipdemographics with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/zipdemographics",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/zipdemographicsnpm APIVerve.API.ZIPDemographicsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/zipdemographics

Install the C# / .NET SDK, then call the ZIP Demographics API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.ZIPDemographics

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/zipdemographics");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.ZIPDemographicsThe published C# / .NET client, versioned and signed.GitHubapiverve/zipdemographics-apiSource, issues and the examples this page is built from.ReferenceZIP Demographics API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/zipdemographicsnpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/zipdemographics

No SDK to install — this is a plain HTTPS call to /v1/zipdemographics with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/zipdemographics", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/zipdemographicsnpm APIVerve.API.ZIPDemographicsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/zipdemographics

No SDK to install — this is a plain HTTPS call to /v1/zipdemographics with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/zipdemographics");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/zipdemographicsnpm APIVerve.API.ZIPDemographicsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/zipdemographics

No SDK to install — this is a plain HTTPS call to /v1/zipdemographics with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/zipdemographics")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/zipdemographicsnpm APIVerve.API.ZIPDemographicsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

The Timezone Bug That Cost Us a ClientA scheduled email went out at 3 AM instead of 9 AM. The client wasn't happy. Here's what went wrong.Read

Build a Lead Enrichment Pipeline That Actually WorksTurn email addresses into full customer profiles. Location, company, social links—automatically. Here's how to build it.Read

Weather APIs: Build a Dashboard That's Actually UsefulCurrent conditions, forecasts, air quality, sunrise times—here's how to build a weather dashboard users will love.Read

ZIP Demographics API GET

Try it — live request, no key required

About the ZIP Demographics API

What people use it for

Ways to call it

Other ways to use ZIP Demographics

Questions.

Request parameters — GET /v1/zipdemographics

Required

Authentication

Response — GET /v1/zipdemographics

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — GET /v1/zipdemographics

Resources

Also published for

Call it from Node.js — GET /v1/zipdemographics

Resources

Also published for

Call it from Python — GET /v1/zipdemographics

Resources

Also published for

Call it from C# / .NET — GET /v1/zipdemographics

Resources

Also published for

Call it from Go — GET /v1/zipdemographics

Resources

Also published for

Call it from PHP — GET /v1/zipdemographics

Resources

Also published for

Call it from Ruby — GET /v1/zipdemographics

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — ZIP Demographics API

Data Lookup

Related articles

Ready to build with ZIP Demographics? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog