Zip Codes Lookup API
Overview
To use Zip Codes Lookup, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/zipcodesExample
How to call the Zip Codes Lookup API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/zipcodes?zip=64082" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/zipcodes?zip=64082', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/zipcodes?zip=64082', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/zipcodes?zip=64082", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"zipcode": "64082",
"state_abbr": "MO",
"latitude": "38.850243",
"longitude": "-94.39570",
"city": "Lees Summit",
"state": "Missouri"
}
}Authentication
The Zip Codes Lookup API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Zip Codes Lookup API directly in your browser with live requests and responses.
Parameters
The Zip Codes Lookup API supports multiple query options. Use one of the following:
Option 1: Lookup Zip Code
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
zip | string | required | The zip code for which you want to get the data Length: 5 - 5 chars | - |
Option 2: Lookup Zip Code of City
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
city | string | required | The city for which you want to get the zip code data (e.g., Los Angeles) | - | |
state | string | required | The state for which you want to get the zip code data | - |
Response
The Zip Codes Lookup API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<zipcode>64082</zipcode>
<state_abbr>MO</state_abbr>
<latitude>38.850243</latitude>
<longitude>-94.39570</longitude>
<city>Lees Summit</city>
<state>Missouri</state>
</data>
</response>
status: ok
error: null
data:
zipcode: '64082'
state_abbr: MO
latitude: '38.850243'
longitude: '-94.39570'
city: Lees Summit
state: Missouri
| key | value |
|---|---|
| zipcode | 64082 |
| state_abbr | MO |
| latitude | 38.850243 |
| longitude | -94.39570 |
| city | Lees Summit |
| state | Missouri |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
zipcode | string | The ZIP code for the requested location | |
state_abbr | string | Two-letter state abbreviation code | |
latitudePremium | string | Geographic latitude coordinate of the location | |
longitudePremium | string | Geographic longitude coordinate of the location | |
city | string | City name associated with the ZIP code | |
state | string | Full state name corresponding to the abbreviation |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Zip Codes Lookup through GraphQL to combine it with other API calls in a single request. Query only the zip codes lookup data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
zipcodes(
input: {
zip: "64082"
}
) {
zipcode
state_abbr
latitude
longitude
city
state
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Zip Codes Lookup API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Zip Codes Lookup requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Zip Codes Lookup API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Zip Codes Lookup
Official Zip Codes Lookup packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Zip Codes Lookup works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Zip Codes Lookup?
How many credits does Zip Codes Lookup cost?
Each successful Zip Codes Lookup API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful zip codes lookup lookups.
Can I use Zip Codes Lookup in production?
The free plan is for testing and development only. For production use of Zip Codes Lookup, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Zip Codes Lookup from a browser?
What happens if I exceed my Zip Codes Lookup credit limit?
When you reach your monthly credit limit, Zip Codes Lookup API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








