How to See What CRM Enrichment Adds to Your Sales Data (With the LeadOcean API)

TL;DR

• Enrichment adds four kinds of fields to a CRM record: person (title, seniority, contact data), company (size, industry, location), technology, and career history.
• The test takes about 30 minutes and spends up to 50 records: 25 people and 25 companies, all inside the Free plan's 1,000.
• You diff the output against your CRM and write back only the fields that change a routing or scoring rule.

Most CRM records start as a name, an email and a domain. That is enough to create a contact. It is not enough to route a lead, score fit or write a relevant first line.

This guide shows what an enrichment API adds to such a record. Try it on a small sample before you pay for anything.

Prerequisites

• A LeadOcean API key from the free plan, stored as $LEADOCEAN_API_KEY. No card needed. Free gives 1,000 records for life and 5 requests a second.
• A CSV export of 25 CRM contacts with email and domain columns.
• curl and jq.

Step 1: Size the gap before you spend anything

Count how many people you could reach for your target profile. The count is free and spends no records.

The MCP tool leadocean_count_leads takes the same filters as search. Here is a run from 21 October 2026:

{
  "jobLevel": ["VP"],
  "jobFunction": ["Sales & Business Development"],
  "country": ["CA"]
}

{
  "total": 5574,
  "totalIsExact": true,
  "totalAll": 18800,
  "distinctCompanies": 3873
}

total counts people with a verified, catch_all_valid or catch_all email. totalAll is the same filters with no email condition. For companies, GET /v1/companies/count is the free equivalent.

Step 2: Enrich one person by email

Enrichment takes exactly one of linkedin_url, email, phone or person_id. Add reveal_email only if you need the address back.

curl -s -X POST https://api.leadocean.io/v1/people/enrich \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "jane.doe@acme.com"}'

A person we hold nothing for returns 404 and costs nothing. A hit costs one record.

Step 3: Look up the company by domain

Company enrich takes a domain (or a company linkedin_url).

curl -s -X POST https://api.leadocean.io/v1/companies/enrich \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain": "acme.com"}'

The response has three parts: company_data (firmographics), company_detected_technologies and company_metrics. A hit costs one record. A domain we hold nothing for is a 404 and costs nothing.

Tech data covers about 7.8M crawled sites, so an empty tech block can mean "not crawled", not "not used". To target by stack, search with technologyCategories (for example ["CRM"]) or technologies.

Step 4: Run the 25-contact sample

Loop over your CSV and save every response. Stay under 5 requests a second on Free.

tail -n +2 sample.csv | while IFS=, read -r email domain; do
  curl -s -X POST https://api.leadocean.io/v1/people/enrich \
    -H "x-api-key: $LEADOCEAN_API_KEY" -H "Content-Type: application/json" \
    -d "{\"email\": \"$email\"}" > "out/person_$email.json"
  curl -s -X POST https://api.leadocean.io/v1/companies/enrich \
    -H "x-api-key: $LEADOCEAN_API_KEY" -H "Content-Type: application/json" \
    -d "{\"domain\": \"$domain\"}" > "out/company_$domain.json"
  sleep 0.5
done

Misses are free for people and companies. Check GET /v1/usage afterwards to see what the run spent.

Step 5: Diff against the CRM and pick what to write back

Count the fields that were empty in your CRM and filled by the response.

for f in out/person_*.json; do
  jq -r '[input_filename,
    (.data.contact_data.contact_current_experiences[0] != null),
    ((.data.resume_data.experiences // []) | length)] | @csv' "$f"
done

Write back a field only if a rule reads it. Seniority and job function feed routing. Headcount and industry feed ICP scoring. Career history feeds personalization, not routing.

What you get

Enrichment adds four groups of fields. This is the response shape from the API reference, abbreviated, with placeholder values:

{
  "success": true,
  "data": {
    "profile_data": { "profile_full_name": "Jane Doe" },
    "contact_data": {
      "has_email": true,
      "has_phone": true,
      "email_status": "verified",
      "contact_current_experiences": [
        { "job_title": "VP Sales", "company_name": "Acme", "company_domain": "acme.com" }
      ]
    },
    "resume_data": {
      "experiences": [
        { "job_title": "Director of Sales", "company_name": "Example Co" }
      ],
      "educations": [],
      "certifications": []
    },
    "meta": { "fetched_at": "2026-10-01" }
  }
}

contact_emails[] and contact_phones[] appear inside contact_data only when you send reveal_email.

Past employers carry no company_id yet, so you cannot join career history to company records.

The dataset is refreshed monthly, with a fetched_at date on each record. Check that date before you overwrite a CRM field that a rep edited by hand.

Troubleshooting

FAQ