Skip to main content
POST
/
v1
/
prospects
/
contacts_information
/
enrich
Contacts Information
curl --request POST \
  --url https://api.explorium.ai/v1/prospects/contacts_information/enrich \
  --header 'Content-Type: application/json' \
  --header 'api_key: <api-key>' \
  --data '{
  "request_context": {},
  "parameters": {},
  "prospect_id": "<string>"
}'
{
  "response_context": {
    "correlation_id": "<string>",
    "request_status": "success",
    "time_took_in_seconds": 123
  },
  "data": {
    "emails": [
      {}
    ],
    "professions_email": "jsmith@example.com",
    "professional_email_status": "valid",
    "phone_numbers": [
      {}
    ],
    "mobile_phone": "<string>"
  },
  "entity_id": "<string>"
}

​
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.
  • Retrieve multiple email addresses, including personal and professional.
  • Ensure accurate and up-to-date data for prospecting and engagement.

​
Endpoint: POST /prospects/contacts_information/enrich

  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 contact details, emails, and phone numbers.
FieldTypeDescription
prospect_idStringA unique identifier for the prospect (Required)
  • 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.
SignalAPI NameDescriptionData Type Final
professional_email_statusIndividual’s professional email validity statusRecommended validity status for the listed ‘Professional email’ address. Returns one of the following possible values: ‘valid’ emails are determined as safe to email, ‘invalid’ emails are addresses we recommend to erase from mailing lists, ‘catch-all’ emails are created as a precaution by domain owners. For recommendations on how best to use ‘catch all’ emails, read more on our resource center page ‘Email validation: catch-all domains’.object
emailsIndividual’s emailsList of all email addresses associated with the individual labeled as a professional or personal email address.array
professions_emailIndividual’s professional emailCurrent professional email address associated with the individualstring
mobile_phoneIndividual’s mobile phoneIndividual’s direct dial mobile phone number.string
phone_numbersIndividual’s phone numbersList of all phone numbers associated with the individual.array

​
Body Params - Try Me Example

prospect_id: ee936e451b50c70e068e1b54e106cb89173198c4
Email Only (2 credits): 
  {
    "prospect_id": "ee936e451b50c70e068e1b54e106cb89173198c4",
    "parameters": {
      "contact_types": ["email"]
    }
  }
Phone Only (5 credits): 
{
    "prospect_id": "ee936e451b50c70e068e1b54e106cb89173198c4",
    "parameters": {
      "contact_types": ["phone"]
    }
  }
Both Email and Phone (5 credits) - Default behavior: 
{
    "prospect_id": "ee936e451b50c70e068e1b54e106cb89173198c4",
    "parameters": {
      "contact_types": ["email", "phone"]
    }
  }
Backward Compatible (no parameters = all contact types): 
prospect_id: ee936e451b50c70e068e1b54e106cb89173198c4

Authorizations

​
api_key
string
header
required

Body

application/json
​
prospect_id
string
required

The prospect_id to enrich.

​
request_context
object
​
parameters
object

Response

Successful Response

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

​
response_context
object
required
​
data
​
entity_id
⌘I