Contact details

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`

How It Works

Input: Provide a prospect_id (retrieved from the Match Prospects endpoint) to retrieve enrichment details.
Processing: The system scans and fetches available data from multiple sources.
Output: A structured response containing contact details, emails, and phone numbers.

Request Schema

Field	Type	Description
`prospect_id`	String	A unique identifier for the prospect (Required)

Best Practices

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.

Contacts Information Output Signal

Signal	API Name	Description	Data Type Final
professional_email_status	Individual’s professional email validity status	Recommended 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
emails	Individual’s emails	List of all email addresses associated with the individual labeled as a professional or personal email address.	array
professions_email	Individual’s professional email	Current professional email address associated with the individual	string
mobile_phone	Individual’s mobile phone	Individual’s direct dial mobile phone number.	string
phone_numbers	Individual’s phone numbers	List 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

Request Context · object

Example:

null

parameters

Parameters · object

Response

Successful Response

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

response_context

ResponseContext · object

required

Show child attributes

response_context.correlation_id

string

required

response_context.request_status

enum<string>

required

The RequestStatus class is an enumeration that defines the possible statuses of a request.

This enum is used to indicate whether a request was successful, missed, or failed. It ensures consistent handling of request statuses across the application.

Attributes: SUCCESS: Indicates that the request was successfully processed. MISS: Indicates that the request did not find any matching data. FAILURE: Indicates that the request encountered an error or failure.

Available options:

success,

miss,

failure

response_context.time_took_in_seconds

number

required

data

ContactsInformationOutputSchema · object

ContactsInformationOutputSchema · object
ContactsInformationOutputSchema · object[]

Show child attributes

data.emails

Emails · object[]

Show child attributes

data.emails.{key}

string

data.professions_email

string<email>

data.professional_email_status

enum<string>

The EmailValidationStatus class is an enumeration that represents the validation status of an email address.

This enum is used to categorize email addresses based on their validation results, such as:

VALID: The email address is valid and deliverable.
CATCH_ALL: The email address is part of a catch-all domain, meaning it may or may not be deliverable.
INVALID: The email address is invalid and undeliverable.

These statuses are used to ensure consistent handling of email validation results across the application.

Available options:

valid,

catch-all,

invalid

data.phone_numbers

Phone Numbers · object[]

Show child attributes

data.phone_numbers.{key}

string

data.mobile_phone

string

entity_id

Explorium AgentSource

Partners

Introduction

Endpoint: `POST /prospects/contacts_information/enrich`

Body Params - Try Me Example

Authorizations

Body

Response

Explorium AgentSource

Partners

​Introduction

​Endpoint: POST /prospects/contacts_information/enrich

​Body Params - Try Me Example

Authorizations

Body

Response

Introduction

Endpoint: `POST /prospects/contacts_information/enrich`

Body Params - Try Me Example