Fast, accurate ZIP Code and Postal Code data API.

Free and low-cost ZIP code APIs—Zippopotam, ZipCodeAPI, ZipCodeBase, ZipCodeStack—typically return 5–9 fields drawn from public datasets like GeoNames. Some charge $45–200/year for that same basic data. The underlying issue isn't price—it's the source. GeoNames coordinates are algorithmically estimated (their own documentation notes that unmatched postal codes use “an average lat/lng of neighbouring postal codes”), newly created ZIP codes can take years to appear, and the data is provided “as-is” with no accuracy warranty. That's fine for a quick prototype, but risky for production.

This API returns 50+ fields in a base credit, with opt-in access to 542 ACS demographic fields across 14 years of Census data, spatial boundary radius search with per-ZIP overlap percentages, congressional and school districts, full Canadian postal code support, plus street address validation with USPS ZIP+4 matching—all through the same endpoint. Our US ZIP boundary data is commercially licensed and updated quarterly from authoritative sources.

The free tier (2,500 credits/day, no credit card) gives you full access to every enrichment so you can evaluate the depth before committing to a paid plan.

Yes. The v2 API is new (launched March 2026), but it runs on infrastructure and data sources that have served 84,000+ customers since 2003—including Fortune 500 companies like Wells Fargo and Abbott Laboratories. The underlying boundary data, ACS demographics, and Canadian postal data are the same production-grade sources our customers have relied on for over two decades.

We call it “new” because the developer interface is new—the data, the uptime, and the support are not. Email support, usage monitoring, and an unconditional money-back guarantee are in place from day one.

Yes — the /address endpoint parses raw street addresses and matches them against USPS ZIP+4 delivery-point data. It returns the standardized address, ZIP+4 code, parsed components, carrier route, and delivery metadata. Input is flexible: ZIP code and state are optional — we resolve them automatically. 1 credit per request. Batch processing available for paid plans. Try it in the interactive demo.

The USPS retired their Web Tools API on January 25, 2026. The replacement at developers.usps.com imposes a default rate limit of 60 requests per hour — with no documented self-serve path to increase it. Our /address endpoint has no per-hour rate limit at that level — paid plans support hundreds of requests per second. You get USPS ZIP+4 matching, standardized output, and parsed address components through a simple REST call. No OAuth tokens, no federal developer account, no approval process. Sign up, get an API key, and start validating addresses in under a minute. The free tier includes 2,500 credits per day — enough to evaluate thoroughly before committing.

Yes. You can create a free account that includes 2,500 free credits per day—no credit card required. The free tier supports all enrichment types (including historical ACS data), address validation, and all endpoints. Free radius searches are capped at 100 miles (standard) or 50 miles (spatial boundary mode), and suggest is limited to 15 results. Paid plans unlock significantly higher radius limits—up to 500 miles for centroid mode and 250 miles for spatial—plus batch access and higher request rates. Plans start at $49/month, or you can purchase Credit Packs that never expire and kick in when your daily/monthly limit is reached.

Every request returns base information—city, state/province, county, latitude/longitude, and code type—at no extra cost. You can opt in to additional enrichments like American Community Survey (ACS) demographic profiles (current or historical years), economic and housing data, timezone details, Census boundaries (congressional districts, state legislative districts, school districts), and more. Each enrichment you request adds to that single credit's cost, so you only pay for the data you need. For street addresses, the /address endpoint returns the standardized address, ZIP+4, parsed components, and delivery metadata — 1 credit per request.

Our US ZIP code boundaries are commercially licensed and derived from actual postal delivery routes—not Census ZCTA approximations. We've partnered with the same data provider for over 15 years, and boundaries are updated quarterly. Demographic and economic data comes directly from the US Census Bureau's American Community Survey (ACS), updated annually. Canadian postal code data is sourced from Statistics Canada. Base ZIP code data is refreshed monthly.

US ZIP code base data is updated monthly. ZIP code boundaries are refreshed quarterly. American Community Survey (ACS) data is updated annually when the Census Bureau releases new estimates (typically each December)—and we maintain multiple historical years so you can track demographic trends over time. Canadian postal codes are updated monthly, and Canadian Census boundaries follow Statistics Canada's release cycle.

Yes. The API supports both US ZIP codes and Canadian postal codes through the same endpoints. Canada uses two formats—3-character Forward Sortation Areas (FSAs like M5V) and full 6-character postal codes (like M1R 0E9)—and the API handles both. Canadian lookups return province, coordinates, timezone, and Census boundary data from Statistics Canada.

We chose to cover North America thoroughly rather than the world thinly. Most APIs that claim global postal coverage return 2–3 fields per country from public datasets. We maintain 542 enrichment fields, 14 years of historical data, and quarterly-updated boundary polygons—that depth requires focus.

Most ZIP code APIs use centroid mode—finding ZIP codes whose center point falls within your search radius. It's fast, but incomplete. A ZIP code's centroid might be just outside your radius while a significant portion of the actual boundary falls inside. In centroid mode, you'd miss it entirely. Spatial mode uses actual boundary polygons to calculate the exact percentage of each ZIP code that overlaps your search circle—every result includes a pct_inside value.

Yes—the /v2/suggest endpoint provides real-time autocomplete for ZIP codes, cities, counties, CBSAs, and Canadian postal codes. It includes fuzzy matching (handles misspellings), geographic proximity bias, and returns up to 500 results per query on paid plans. Free accounts get up to 15 results per query, paid plans can query up to 500 results. Try it in the interactive demo.

We answer the phone and we respond to emails—typically within 30 minutes during business hours. Zip-Codes.com has been in operation since 2003, serving over 84,000 customers including Fortune 500 companies and government agencies. Customer service isn't a department here; it's the foundation of everything we do. Every account is backed by an unconditional money-back guarantee, and our team is available by phone (9am–5pm EST) and email (8am–10pm EST), Monday through Friday.