Match a list of businesses attributes to ids.
Returns a list of the same length and order as the input list, with the matched ids.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Endpoint:POST /businesses/match
POST /businesses/matchDescription
The Match Businesses endpoint is the first step in the data enrichment process. It enables users to accurately identify businesses based on their name or domain, returning a unique Business ID that acts as the foundation for all subsequent API interactions.
This endpoint is designed to provide high-accuracy business matching by leveraging multiple data sources, validation layers, and proprietary algorithms to ensure precise identification.
Once a business is successfully matched, its Business ID becomes the primary key for retrieving enriched company data, accessing financial insights, monitoring real-time business events, and performing additional analytics through other Explorium APIs.
Coverage
| Attribute | Coverage Details |
|---|---|
| Total Businesses | 80M+ businesses across 150+ countries |
| Matching Accuracy | Advanced entity resolution for precise business identification |
| Real-Time Updates | Ensures the latest business records are used for matching |
How It Works
* Input: A list of business identifiers, which can include name, domain, and LinkedIn company URL.
- Processing: Our system cross-references multiple datasets to find the best match.
- Output: A structured response with the matched Business IDs, maintaining the same order as the input list.
Schema Explanation
| Field | Type | Description |
|---|---|---|
businesses_to_match | Array | List of business identifiers to match (can include name, domain, LinkedIn) |
name | String | Business name provided for matching |
domain | String | Business domain provided for matching |
linkedin_url | String | LinkedIn company profile URL (optional, improves matching accuracy) |
business_id | String | Unique identifier for the matched business (null if not found) |
Body Params – Example with LinkedIn URL
{
"request_context": {
"seller_id": "sample_seller"
},
"businesses_to_match": [
{
"name": "microsoft",
"linkedin_url": "https://linkedin.com/company/microsoft"
}
]
}Best Practices
* Always store the Business ID – It serves as the key for all future enrichment and analytics.
- Use multiple identifiers (e.g., name + domain, or LinkedIn URL) for higher match accuracy.
- Batch requests efficiently to optimize API performance.
- Handle null values gracefully to account for unmatched businesses.
- Update and validate input data regularly to ensure the most accurate matches.
📌 For detailed endpoint explanations, request examples, and integration tips, explore the documentation sections above.
Body Params - Try Me Example
name: Apple
domain: apple.com
name: Microsoft
domain: microsoft.com