Reveal emails and phone numbers with Contact Enrichment

Contact enrichment reveals work emails, personal emails, and phone numbers for your prospects. Descovo provides three methods depending on how many contacts you need to enrich and how you want to manage the workflow. Use sync enrichment for one-off lookups, batch enrichment when you have a list of LinkedIn URLs, and the audience workflow when you want to enrich an entire filtered segment.

Credits are charged when enrichment runs. Always confirm the contact types you intend to request — work email, personal email, and phone number are each billed separately.

Choose your method

Sync (single contact)
Batch (many contacts)
Audience-based

Sync enrichment returns results immediately for a single LinkedIn profile. Use this when you need contact data for one to five people in an interactive context.Endpoint: POST /v1/individual-reveal/syncCredits are charged per successful enrichment, per data type requested.

Request parameters

apiKey

string

required

Your Descovo API key.

linkedinUrl

string

required

Full LinkedIn profile URL of the person to enrich, e.g. https://www.linkedin.com/in/example-profile/.

enrichmentTypes

object

required

Specify which contact types to retrieve. Set each to true or false.

getWorkEmails — professional email addresses
getPersonalEmails — personal email addresses
getPhoneNumbers — phone numbers

Example

{
  "apiKey": "sk_live_xxx",
  "linkedinUrl": "https://www.linkedin.com/in/example-profile/",
  "enrichmentTypes": {
    "getWorkEmails": true,
    "getPersonalEmails": false,
    "getPhoneNumbers": true
  }
}

Some profiles will not have any emails or phone numbers on file. When the response arrays are empty, no credits are charged for that data type.

Batch enrichment handles up to 10,000 LinkedIn profiles in a single asynchronous job. The workflow has two steps: start the batch to enqueue profiles and charge credits upfront, then poll until results are ready.Credits are charged upfront for all unique profiles after deduplication.

Step 1: Start the batch

Endpoint: POST /v1/contact-enrich/batch/start

apiKey

string

required

Your Descovo API key.

enrichmentTypes

object

required

Which contact types to retrieve (getWorkEmails, getPersonalEmails, getPhoneNumbers).

personDetails

object[]

required

Array of people to enrich. Each entry requires at minimum a linkedinUrl.

[
  { "linkedinUrl": "https://www.linkedin.com/in/example-1/" },
  { "linkedinUrl": "https://www.linkedin.com/in/example-2/" }
]

{
  "apiKey": "sk_live_xxx",
  "enrichmentTypes": {
    "getWorkEmails": true,
    "getPersonalEmails": true,
    "getPhoneNumbers": false
  },
  "personDetails": [
    { "linkedinUrl": "https://www.linkedin.com/in/example-1/" },
    { "linkedinUrl": "https://www.linkedin.com/in/example-2/" }
  ]
}

Save the taskId — you need it to poll for results.

Step 2: Poll for results

Endpoint: POST /v1/contact-enrich/batch/pollPoll every 30–60 seconds until done is true. Use nextCursor to page through results when the batch is large.

apiKey

string

required

Your Descovo API key.

taskId

string

required

The taskId returned when you started the batch.

take

number

default:"100"

Number of completed results to return per poll request.

cursor

string

Pagination cursor. Pass null for the first poll, then the nextCursor from each response.

{
  "apiKey": "sk_live_xxx",
  "taskId": "aud_abc123",
  "take": 100,
  "cursor": null
}

Response

{
  "output": {
    "overallStats": {
      "totalPeopleToFetch": 200,
      "numCompleted": 120,
      "numRemaining": 80,
      "numRejected": 5,
      "numDuplicates": 10
    },
    "done": false,
    "pageResults": [
      {
        "inputs": {
          "linkedinUrl": {
            "value": "https://www.linkedin.com/in/example-1/"
          }
        },
        "outputs": {
          "emails": [
            "person@company.com"
          ],
          "phoneNumbers": [
            "+1-555-123-4567"
          ]
        }
      }
    ],
    "nextCursor": "encrypted_cursor_here"
  },
  "chargeInfo": {
    "method": "charged-for-async-process",
    "creditsCharged": 0,
    "message": "Credits were already charged when the batch was started."
  }
}

Use overallStats to track progress. Continue polling until done is true, then page through remaining results using nextCursor until it becomes null.

When you have a filtered segment of prospects already saved in an audience, you can run enrichment over the entire audience at once. This is the most powerful method for large-scale prospecting because you can combine company and people filters, estimate costs before committing, and export enriched results to CSV.The full sequence for audience-based enrichment:

Build an audience — see the audience workflow guide
Estimate enrichment cost: POST /v1/audiences/{audienceId}/enrichment/estimate
Trigger enrichment: POST /v1/audiences/{audienceId}/enrich
Poll status: GET /v1/audiences/{audienceId}/enrichment/status
Export results: POST /v1/audiences/{audienceId}/export/prospects

When exporting, set onlyWithContacts: true to limit the CSV to prospects where at least one contact detail was found.

{
  "apiKey": "sk_live_xxx",
  "format": "PROSPECT_GENERIC_CSV",
  "onlyWithContacts": true,
  "maxRowsToExport": 10000,
  "userEmail": "you@example.com"
}

Always call the estimate endpoint before triggering audience enrichment. The estimate is free and shows you the total credit cost and an estimated completion time before you commit.

Credit costs

Enrichment is billed per operation per person. Typical credit costs are:

Operation	Credits (typical)
Work email reveal	2
Personal email reveal	2
Phone number reveal	3

For audience enrichment, waterfall pricing applies — a combined enrichment pass can be cheaper than requesting each contact type independently. Check the estimate endpoint for a full breakdown before you trigger enrichment.

You can check your current credit balance at any time with GET /v1/credits?apiKey=sk_live_xxx.

Get Started

Guides

AI & MCP

Reveal emails and phone numbers with Contact Enrichment

Choose your method

Request parameters

Example

Step 1: Start the batch

Step 2: Poll for results

Credit costs

Get Started

Guides

AI & MCP

Documentation Index

​Choose your method

​Request parameters

​Example

​Step 1: Start the batch

​Step 2: Poll for results

​Credit costs

Choose your method

Request parameters

Example

Step 1: Start the batch

Step 2: Poll for results

Credit costs