Parse Addresses into Structured Components

Street Address Parser API.

Parse unstructured address strings into normalized components. Extract street number, street name, street type, city, state, and zip code. Perfect for cleaning address data, validating form inputs, and standardizing shipping information.

Get your free API key Read the docs

Free tier, no card< 200ms responses99.9% uptime SLA

GET/v1/streetaddressparserlive

query

Response200 OK · sample

{
  "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"
    }
  }
}

Sample response · verify to run one live call, no signup

How it works

Street Address Parser API

Extract all address components accurately
Handles various address formats and abbreviations
Perfect for data normalization and cleaning
Shipping and logistics ready output

1
Send one request
A single authenticated GET with the location you care about — no SDK required.
```
GET /v1/streetaddressparser?query=…
x-api-key: your_key
```
2
We do the aggregation
Each request pulls from multiple upstream sources and computes the derived fields for you.
3
Get clean JSON back
One structured object, typically under 200 ms — ready to render.
```
{ address, parsed, … }
```

The response

Everything in a single call.

/v1/streetaddressparserapplication/json

address"1600 Amphitheatre Parkway, Mountain View, CA 90210"

parsedstreetNumber, streetType, streetAddress, cityName, stateName, zipCode

Use cases

What developers build with it.

Real applications shipping on this endpoint today — each with the numbers that made it worth wiring up.

See every use case

Address Data Normalization

Parse all addresses into consistent structured components. Normalize street types, standardize formatting, and enable accurate address matching.

Consistent address format across systemsEnable accurate deduplicationImprove address matching

Standardizedaddress format

Betterdata quality

Automateddata cleaning

Address Form Auto-fill

Detect when a full address is pasted and automatically populate city, state, and zip fields. Improve form UX while ensuring structured data.

Better form user experienceFewer form errorsStructured data collection

Better UXfor address forms

Fewer errorsin submissions

Fasterform completion

Start coding

Call it in your language.

Copy a working request, or install a typed SDK. Same endpoint, same key.

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" },
});
const { data } = await res.json();
console.log(data);

Included in your key

One subscription, the whole parse addresses into structured components stack.

Every related API ships with your key — no separate plans, no extra keys, one bill.

See pricing

8APIs in this bundle

99.9%uptime SLA

The bundle

streetaddressparserYou’re herezipcodes reversegeocode citieslookup countrylookup distancecalculator iplookup countydata

No code required

Wire it into the tools you already run.

Ready-made recipes for Zapier, Make, and n8n — trigger on an event, and the data lands where your team works.

Google Sheets

Parse addresses from a spreadsheet column

WhenNew row added

ThenFetch parsed address → update row

Slack

Parse addresses shared in a channel

WhenNew message in channel

ThenFetch parsed address → reply with components

Airtable

Auto-parse addresses on new records

WhenNew record created

ThenFetch parsed address → update record

Notion

Parse addresses in a Notion database

WhenNew database item created

ThenFetch parsed address → update properties

Salesforce

Parse lead addresses on creation

WhenNew lead created

ThenFetch parsed address → update custom fields

GitHub

Create issues for address parsing failures

WhenScheduled daily

ThenFetch parsed address → create issue if parse fails

Browse all integrations

Learn

Understand the data behind the API.

Address Components Explained

Understanding the parts of US addresses.

International Address Formats

How address formats vary around the world.

Data Quality and Normalization

Ensuring clean, consistent address data.

Questions about the API

What address formats are supported?

The API handles standard US address formats including various abbreviations (St, Street, Ave, Avenue), different ordering, and common formatting variations.

Does it work with international addresses?

The API is optimized for US addresses. International address parsing may work for addresses following similar patterns, but results vary.

Can it handle apartment or unit numbers?

Yes, the parser recognizes secondary address units like Apt, Suite, Unit, and # designations.

What if the address is incomplete?

The API parses whatever information is available. Missing components will be null or omitted in the response.

Does this validate addresses?

This API parses addresses into components but does not verify if the address exists. Use with a geocoding or address validation service for verification.

How does it handle PO Boxes?

PO Box addresses are recognized and parsed appropriately with the box number extracted.

Start building with the Street Address Parser API. Free tier, no card required — your key is live in minutes.

Get your free API key→Read the docs

Bonus: 300+ more APIs

The same key unlocks every other APIVerve endpoint — reach for them when you need them.

Browse the catalog