Skip to main content
POST
V2 Prospects Contact Information Enrich

Introduction

The Contact details enrichments API provides detailed information about individual prospects, including contact details, professional emails, and phone numbers. This API is crucial for lead enrichment, personalized outreach, and enhancing sales intelligence workflows. Key Benefits:
  • Access validated contact information for prospects.
  • Get SHA256-hashed email identifiers (professional and personal) for ABM and ad-audience matching, without handling plain-text addresses.
  • Ensure accurate and up-to-date data for prospecting and engagement.

Endpoint: POST /prospects/contact_information/enrich

v2: this endpoint accepts either a single ID (a string) or a list of up to 50 IDs — the separate /bulk_enrich route is gone. See v2 conventions.

Enrich by prospect details instead of IDs

prospect_ids is the primary way to call this endpoint. If you don’t have Explorium IDs yet, you can send prospects_to_match instead: up to 50 people, described with the same fields the Match prospects endpoint accepts (full_name, company_name, email, phone_number, linkedin, business_id). Each person is matched and enriched in the same call. Send either prospect_ids or prospects_to_match, never both (that returns a 422). Any parameters the endpoint takes work the same either way.
Each row echoes its input and returns the matched prospect_id. People who don’t match come back with prospect_id: null and data: null, and aren’t charged. total_matches counts the matched rows.
Need higher coverage? The asynchronous variant supports waterfall enrichment — prospects that Explorium data cannot enrich are retried against a verified external provider. The waterfall parameter is available only on the async endpoint; passing it here returns a validation error.
  1. Input: Provide a prospect_id (retrieved from the Match Prospects endpoint) to retrieve enrichment details.
  2. Processing: The system scans and fetches available data from multiple sources.
  3. Output: A structured response containing the professional email, phone numbers, and mobile number.
  • Use verified prospect IDs for accurate enrichment.
  • Cross-check multiple contact points to reach prospects effectively.
  • Store enriched data in CRM for seamless sales workflows.
  • Update prospect details regularly to maintain accuracy in outreach campaigns.

Hashed identifiers for ABM

Add hashed_identifiers to contact_types to get each prospect’s email addresses as SHA256 hashes, split into hashed_professional_emails and hashed_personal_emails. Hashed emails are the format ad platforms and ABM tools use to match audiences, so you can build and sync account-based audiences without handling plain-text addresses.
  • Cost: 1 credit per prospect returned with hashed identifiers. Email (2 credits) and phone (5 credits) are charged as usual when requested in the same call.
  • Opt-in: hashed identifiers are returned only when you request them. Omitting parameters returns email and phone, as before.
  • Gmail addresses are hashed twice, as written and with the dots in the name removed (jane.doe@gmail.com → janedoe@gmail.com), so both variants are in the array.
  • No emails: both arrays are null when the prospect has no email on record.
Response row with hashed identifiers

Body Params - Try Me Example

Email Only (2 credits):
Phone Only (5 credits):
Both Email and Phone (5 credits) - Default behavior:
Hashed identifiers only (1 credit):
Email and hashed identifiers (2 + 1 = 3 credits):
Backward Compatible (no parameters = email and phone):

Authorizations

api_key
string
header
required

Body

application/json

Provide exactly one of prospect_ids or prospects_to_match; at most 50 entities.

prospect_ids
required
Pattern: ^[a-f0-9]{40}$
request_context
Request Context · object | null
Example:

null

parameters
ContactsEnrichmentParams · object
prospects_to_match
ProspectMatchInput · object[]

Match and enrich up to 50 prospects. Provide this or prospect_ids, never both.

Required array length: 1 - 50 elements
Example:

Response

Successful Response

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

response_context
V2ResponseContext · object
required
data
V2ProspectEnrichRow[V2ContactsInformationOutputSchema] · object[]
required
total_results
integer
required