Skip to main content
POST
/
v1
/
businesses
/
match
Match Businesses
curl --request POST \
  --url https://api.explorium.ai/v1/businesses/match \
  --header 'Content-Type: application/json' \
  --header 'api_key: <api-key>' \
  --data '{
  "request_context": {},
  "businesses_to_match": [
    {
      "name": "<string>",
      "domain": "<string>",
      "url": "<string>",
      "linkedin_url": "<string>"
    }
  ]
}'
{
  "response_context": {
    "correlation_id": "<string>",
    "request_status": "success",
    "time_took_in_seconds": 123
  },
  "total_results": 123,
  "total_matches": 1,
  "matched_businesses": []
}

​
Description

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.
AttributeCoverage Details
Total Businesses80M+ businesses across 150+ countries
Matching AccuracyAdvanced entity resolution for precise business identification
Real-Time UpdatesEnsures the latest business records are used for matching
  • Input: A list of business names and domains.
  • 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.
FieldTypeDescription
businesses_to_matchArrayList of business name-domain pairs to match
business_idStringUnique identifier for the matched business (null if not found)
  • Always store the Business ID – It serves as the key for all future enrichment and analytics.
  • Use multiple identifiers (e.g., name + domain) 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

Authorizations

​
api_key
string
header
required

Body

application/json
​
businesses_to_match
BusinessMatchInput · object[]
required
Required array length: 1 - 50 elements
​
request_context
object

Response

Successful Response

This is base response model for all responses in partner service.

​
response_context
object
required
​
total_results
integer
required

The total_results number matched businesses

Required range: x > 0
​
total_matches
integer
required

The total number of matches.

Required range: x >= 0
​
matched_businesses
Matched Businesses · array

A list of all businesses. If they not matched business_id will None.

  • BusinessMatchOutputWithErrors
  • BusinessMatchOutput
⌘I