Street Address Parser API

About the Street Address Parser API

Street Address Parser works by analyzing the US street address provided and splitting it into its components: street number, directional prefix and suffix, street name, street type, secondary unit, city, state and ZIP code. Intersections such as "Main St and 5th Ave" come back as two streets. PO boxes, written as PO Box, P.O. Box, POB or Post Office Box, come back as sec_unit_type "PO Box" with the box number, city, state and ZIP code. With standardize=true the response adds a standardized block: the address type is free, while the delivery line, last line and ZIP+4 extension require a paid plan. The parser formats what you send; it does not check the address against postal records.

What people use it for

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.

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

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/streetaddressparser

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

Optional

1
2

curl "https://api.apiverve.com/v1/streetaddressparser?address=1600%20Amphitheatre%20Parkway%2C%20Mountain%20View%2C%20CA%2090210&standardize=true" \
  -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.

Response — GET /v1/streetaddressparser

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.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

{
  "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"
    },
    "standardized": {
      "addressType": "street",
      "deliveryLine1": "1600 Amphitheatre Pkwy",
      "lastLine": "Mountain View, CA 90210",
      "zipPlus4": null
    }
  }
}

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.

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.

Errors

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

What a call costs — 2 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.

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.

Zero-code embed — one snippet, no backend

Drop an interactive Street Address Parser form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — Street Address Parser API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1