LeadOcean + Salesforce: enrich Contacts on a schedule

You get a job that finds Salesforce Contacts with a blank email, phone or title, enriches each one through LeadOcean, and writes the answers back. It runs outside Salesforce, so it needs no package and no Apex. It talks to Salesforce through Bulk API 2.0 and to LeadOcean through https://api.leadocean.io. LeadOcean has no Salesforce app. This is a plain HTTP recipe.

How it works

Bulk API 2.0 suits this job. Salesforce says any operation over 2,000 records is a good candidate for it, and in Bulk API 2.0 only ingest jobs consume batches, not query jobs (Salesforce, September 2026).

1. Add two Contact fields. Create a date field LeadOcean_Enriched_On__c and a text field LeadOcean_Email_Status__c. The date is your dedupe flag.
2. Get a LeadOcean key. Sign up at app.leadocean.io/register, no card. Export it as LEADOCEAN_API_KEY.
3. Query the gap. POST /services/data/vXX.X/jobs/query with a SOQL string. Results come back as CSV (Salesforce, September 2026).
4. Enrich each row. For every distinct email in the CSV, call POST /v1/people/enrich. Send linkedin_url instead when the Contact has one and no email.
5. Write back. Build a CSV keyed on the Contact Id and create a Bulk API 2.0 ingest job with operation update. Upload it, then set the state to UploadComplete (Salesforce, September 2026).
6. Schedule it. Run the script from cron or any CI scheduler, daily or weekly. The date filter in step 3 means each run only touches new gaps.

Keep the first run small. Add LIMIT 100 to the SOQL, run the whole loop, and open five Contacts in Salesforce to check the values. Then raise the limit. A sandbox is the safest place for that first pass.

Use update, not upsert. Every row already exists in Salesforce, so write by Id. Upsert needs an external ID field and suits loads where records may be new (Salesforce, September 2026). Writing by Id also means the job never creates a duplicate Contact.

Configuration

The SOQL in step 3. It picks Contacts that have a LinkedIn URL or email, are missing data, and were never enriched:

{
  "operation": "query",
  "query": "SELECT Id, Email, Phone, Title, LinkedIn_URL__c FROM Contact WHERE LeadOcean_Enriched_On__c = NULL AND (Email = NULL OR Phone = NULL OR Title = NULL) AND (Email != NULL OR LinkedIn_URL__c != NULL) LIMIT 10000"
}

LinkedIn_URL__c is a custom field name. Use whatever yours is called. The enrich call in step 4, with a placeholder email:

curl -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","reveal_email":true}'

Send exactly one of linkedin_url, email, phone or person_id. reveal_email costs no extra record, and phones only come back when it is true. A person LeadOcean holds nothing for is a 404 and costs nothing. Stamp those Contacts with today's date anyway, so they are not retried every run.

The ingest job body for step 5:

{ "object": "Contact", "operation": "update", "contentType": "CSV", "lineEnding": "LF" }

Field mapping

The enrich response is one leadocean.person.v1 object under data, with profile_data, contact_data and resume_data (LeadOcean OpenAPI, October 2026). Paths below start inside data.

Dedupe in three places. The date field stops reruns. Calling LeadOcean once per distinct email stops paying twice for duplicate Contacts. Writing by Id creates no new records.

Past roles come back too. Since October 2026 the response carries resume_data.experiences[] with title, company name and dates for each past role LeadOcean holds. Past employers have no company id yet. Write them to a long text field if your reps use job history.

Cost at 10,000 rows

Enriching 10,000 Contacts costs 10,000 records on LeadOcean, which fits Solo at $97 a month. Solo allows 10k enrichments every 5 hours and 50k a week, at 50 requests a second. Free holds 1,000 records for life, enough to test one slice. Agency is $497 a month if a team shares the pace.

Salesforce sets the daily API total per org. Enterprise Edition gets 100,000 plus per-license calls plus purchased add-ons, and API calls from Bulk API 2.0 count toward it (Salesforce, September 2026). Bulk jobs are limited to 15,000 batches per rolling 24 hours, and a batch holds up to 10,000 records. One 10,000-row update job is about one batch. Query jobs consume none.

At 50 requests a second, 10,000 enrich calls take about 200 seconds. See pricing.

Troubleshooting

FAQ