Overview
Street Address Parser works by analyzing the US street address provided and parsing the components. It uses advanced algorithms to parse the street address and returns the parsed components such as street number, street name, city, state, and more.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/streetaddressparser?address=1600%20Amphitheatre%20Parkway%2C%20Mountain%20View%2C%20CA%2090210" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/streetaddressparser?address=1600%20Amphitheatre%20Parkway%2C%20Mountain%20View%2C%20CA%2090210', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/streetaddressparser?address=1600%20Amphitheatre%20Parkway%2C%20Mountain%20View%2C%20CA%2090210",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/streetaddressparser?address=1600%20Amphitheatre%20Parkway%2C%20Mountain%20View%2C%20CA%2090210", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
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.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
addressRequired | string | The street address to parse |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"address": "1600 Amphitheatre Parkway, Mountain View, CA 90210",
"parsed": {
"streetNumber": "1600",
"streetType": "Pkwy",
"streetAddress": "Amphitheatre",
"cityName": "Mountain View",
"stateName": "CA",
"zipCode": "90210"
}
}
}
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 |
|---|---|---|---|
address | string | "1600 Amphitheatre Parkway, Mountain View, CA 90210" | The original street address provided for parsing |
parsed | object | {...} | |
streetNumber | string | "1600" | House or building number from the address |
streetType | string | "Pkwy" | Abbreviated street type like Pkwy, St, Ave |
streetAddress | string | "Amphitheatre" | The name of the street parsed from address |
cityName | string | "Mountain View" | City name extracted from the address |
stateName | string | "CA" | State abbreviation parsed from address |
zipCode | string | "90210" | Postal code extracted from the address |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Start from a template
A working app built on this API, ready to deploy with your own key. Vercel asks for the key when you deploy; the code is on GitHub to change first.
Address Parser
Split a one-line US address into street number, street, city, state and ZIP.
- Node.js
- Express
Use cases
- Mailing Label Printing
- To prepare bulk shipping labels, fulfillment software isolates street numbers, street types, and ZIP codes from freeform buyer text.
- Real Estate Ingestion
- When property portals ingest raw MLS remarks, backend pipelines extract city and state abbreviations to index homes into regional search databases.
- Voter Registration Intake
- Separate unformatted residential entries into discrete building numbers and street names to match voter registrations against county records.
- Tax Jurisdiction Lookup
- Accounting platforms assign municipal sales tax rates by breaking customer billing strings into standardized city names and state codes.
Other ways to use Street Address Parser
Set up Street Address Parser on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Parsers:
