Addresses
Description:
The physical address(es) associated with the business or business location.
Child attributes (and data file structure):
Column Name | Data Type | Description | Example |
---|---|---|---|
street_address1 | string | The street name (and number) associated with the business. | 245 5th Avenue |
street_address2 | string | The suite name, floor name, or other more granular information. | Fl 17 |
city | string | The city associated with the business. | New York |
state | string | The US state associated with the business. | NY |
postal_code | string | The US zip code associated with the business. | 10016 |
type | string | The type of address. Valid values are registered, site, mailing, registered_agent, headquarters, officer. | site |
JSON Sample:
"addresses": [
{
"street_address1": "245 5TH AVE",
"street_address2": "FL 17",
"city": "NEW YORK",
"state": "NY",
"postal_code": "10016"
"type": ""
}
],
Coverage:
- Business: 97%
- Business Locations: 100%
Data sources:
- Addresses from panel of credit and debit card transactions estimated to cover 40% of all credit and debit card transactions in the US
- The transaction data is sourced from credit card issuers (as opposed to merchant acquirers or payment processors)
- Addresses from corporate registrations of the business
Methodology:
- For businesses, we only show the single address most commonly associated with the business (across underlying data sources) for identification/verification
- Business locations must have a complete physical address (i.e., they can’t only have some parts of the address object such as city and
postal_code
)
Other notes and tips:
- Variations of the same address are all resolved to the single, most granular address available in our underlying data sources
Updated 4 months ago