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 Bulk API

The Bulk API from Lob — 2 operation(s) for bulk.

Lob Bulk API is one of 48 APIs that Lob publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Bulk. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

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

2 operations 2 paths 36 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Lob Bulk 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.

Bulk 2
POST
/bulk/us_verifications
Bulk Verify
bulk_us_verifications 1 param body → 200default
POST
/bulk/intl_verifications
Bulk Verify
bulk_intl_verifications body → 200default

Schemas 36

The contract defines 36 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), intl_components (5 properties). Each schema is shown below with its type and property counts.

primary_line
string
The primary delivery line (usually the street address) of the address.
city
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.
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_ver_id
string
Unique identifier prefixed with usver.
primary_number
string
The numeric or alphanumeric part of an address preceding the street name. Often the house, building, or PO Box number.
intl_ver_id
string
Unique identifier prefixed with intlver.
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
country_extended
string
Must be a 2 letter country short-name code (ISO 3166). Does not accept US, AS, PR, FM, GU, MH, MP, PW, or VI. For these addresses, please use the US verificati…
multiple_components
street_name
string
The name of the street.
intl_verification
country_short
string
The country of the address. Will be returned as a 2 letter country short-name code (ISO 3166).
postal_code
string
The postal code.
county
string
County name of the address 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.
multiple_components_intl
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.
zip_code_plus_4
string
intl_verifications_payload
object
1 property 1 required
primary_line_us
string
The primary delivery line (usually the street address) of the address. Combination of the following applicable components: primarynumber streetpredirection str…
us_verifications
object
2 properties 2 required
recipient
stringnull
The intended recipient, typically a person's or firm's name.
city_no_description
string
zip_code
string
us_verification
object
12 properties
intl_verifications
object
2 properties 2 required
state
string
The ISO 3166-2 two letter code for the state.
deliverability_analysis
object
A nested object containing a breakdown of the deliverability of an address.
15 properties 15 required
us_components
object
A nested object containing a breakdown of each component of an address.
27 properties 25 required
dpv_footnote
string
multiple_components_list
object
1 property 1 required
intl_components
object
A nested object containing a breakdown of each component of an address.
5 properties
intl_verification_base
object
3 properties
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).
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 Lobs mail deliv…
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lob-bulk-api-openapi.yml Raw ↑

Other APIs Lob publishes across the network.

Lob Accounts API
Lob Addresses API
Lob Bank Accounts API
Lob Bank_id API
Lob Bg_id API
Lob Billing Groups API
Lob Booklet_id API
Lob Booklets API
Lob Buckslip_id API
Lob Buckslips API
Lob Campaigns API
Lob Cards API
Where this information came from

This is an independent, third-party profile of Lob Bulk 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.