How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Lob.com US Verifications API

Validate, automatically correct, and standardize the addresses in youraddress book based on USPS's Coding Accuracy Support System (CASS).back to top## US Verifications Test EnvWhen verifying US addresses, you'll likely want to test against a wide array of addresses toensure you're handling responses correctly. With your test API key, requests that use specificvalues for `address` or `primary_line` and (if using `primary_line`) an arbitrary five digitnumber for `zip_code` (e.g. "11111") let you explore the responses to many types of addresses: ADDRESS TYPE FOR SAMPLE RESPONSE DELIVERABILITY SET primary_line OR address TO Commercial highrise deliverable commercial highrise Residential highrise deliverable residential highrise Residential house deliverable residential house PO Box deliverable po box Rural route deliverable rural route Puerty Rico address w/ urbanization deliverable puerto rico Military address deliverable military Department of state deliverable department of state Generic deliverable deliverable deliverable Missing a suite number deliverable_missing_unit missing unit Suite number doesn't exist deliverable_incorrect_unit incorrect unit Residential house with unnecessary suite number deliverable_unnecessary_unit unnecessary unit Undeliverable and block matched undeliverable undeliverable block match Undeliverable and no block matched undeliverable undeliverable no match See the `test` request & response examples under [US Verification Examples](#operation/us_verification) within the"Verify a US or US territory address" section in US Verifications.You can rely on the response from these examples generally matching the response you'd see in the live environment with anaddress of that type (excluding the `recipient` field).The test API key does not perform any verification, automatic correction, or standardization for addresses. If you wish totry these features out, use our live demo or the free plan (see our pricing for details).back to top

Lob.com US Verifications API is one of 32 APIs that Lob.com publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include U S Verifications. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 2 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 1.22.0.

Requests are made against a single base URL, https://api.lob.com/v1.

2 operations 2 paths 27 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.22.0
Base URL
https://api.lob.com/v1
Authentication
HTTP Basic
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Lob.com US Verifications API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.

US Verifications 2

Validate, automatically correct, and standardize the addresses in your address book based on USPS's Coding Accuracy Support System (CASS) . back to top US Verifications Test Env W…

POST
/bulk/us_verifications
Bulk Verify
bulk_us_verifications 1 param body → 200default
POST
/us_verifications
Single Verify
us_verification 1 param body → 200default

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are us_components (27 properties), deliverability_analysis (15 properties), us_verification (12 properties), us_verifications (2 properties). Each schema is shown below with its type and property counts.

error
object
Lob uses RESTful HTTP response codes to indicate success or failure of an API request. In general, 2xx indicates success, 4xx indicate an input error, and 5xx…
1 property 1 required
city
secondary_line
string
The secondary delivery line of the address. This field is typically empty but may contain information if primaryline is too long.
us_components
object
A nested object containing a breakdown of each component of an address.
27 properties 25 required
primary_number
string
The numeric or alphanumeric part of an address preceding the street name. Often the house, building, or PO Box number.
street_name
string
The name of the street.
zip_code
string
zip_code_type
string
A description of the ZIP code type. For more detailed information about each ZIP code type, see [US Verification Details](tag/US-Verification-Types).
failure_status_code
integer
A conventional HTTP status code: 401 - Authorization error with your API key or account 403 - Forbidden error with your API key or account 404 - The requested…
us_verifications_writable
urbanization
string
Only present for addresses in Puerto Rico. An urbanization refers to an area, sector, or development within a city. See USPS documentation for clarification.
multiple_components_list
object
1 property 1 required
recipient
stringnull
The intended recipient, typically a person's or firm's name.
dpv_footnote
string
us_verifications
object
2 properties 2 required
us_verification
object
12 properties
single_line_address
object
1 property 1 required
multiple_components
us_ver_id
string
Unique identifier prefixed with usver.
city_no_description
string
lob_confidence_score
object
Lob Confidence Score is a nested object that provides a numerical value between 0-100 of the likelihood that an address is deliverable based on Lob’s mail deli…
2 properties 2 required
county_fips
string
A 5-digit FIPS county code which uniquely identifies components[county]. It consists of a 2-digit state code and a 3-digit county code.
primary_line_us
string
The primary delivery line (usually the street address) of the address. Combination of the following applicable components: primarynumber streetpredirection str…
deliverability_analysis
object
A nested object containing a breakdown of the deliverability of an address.
15 properties 15 required
zip_code_plus_4
string
state
string
The ISO 3166-2 two letter code for the state.
county
string
County name of the address city.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lobcom-us-verifications-api-openapi.yml Raw ↑

Other APIs Lob.com publishes across the network.

Lob.com Accounts API
Lob.com Addresses API
Lob.com Bank Accounts API
Lob.com Billing Groups API
Lob.com Booklets API
Lob.com Buckslip Orders API
Lob.com Buckslips API
Lob.com Campaigns API
Lob.com Card Orders API
Lob.com Cards API
Lob.com Checks API
Lob.com Creatives API
Where this information came from

This is an independent, third-party profile of Lob.com US Verifications API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.