LeadOcean + Close: enrich contacts on a schedule

You get a script that finds Close contacts nobody has enriched, sends each one to LeadOcean, and writes the work email, phone and job title back. Close has no LeadOcean app, so the recipe uses two plain HTTP APIs: https://api.close.com/api/v1 and https://api.leadocean.io. Run it from cron, a CI job or any scheduler you already own. The screenshots below show the recipe running.

How it works

The script makes three calls per contact: find, enrich, update. A custom field on the contact records when it was enriched, so the next run skips it.

1. Create a LeadOcean key. Sign up at app.leadocean.io/register. The free plan needs no card and gives 1,000 records.
2. Create a Close API key. In Close go to Settings, Developer, API Keys (Close docs, September 2026). The key is scoped to one user and organization.
3. Add a contact custom field. Create a datetime field named "LeadOcean enriched at" with POST /custom_field/contact/ (Close docs, September 2026). Note its cf_ id.
4. Find contacts to enrich. Call POST /api/v1/data/search/ with an object_type of contact. The Advanced Filtering API returns contact ids and a cursor (Close docs, September 2026). Skip any contact whose stamp field is set.
5. Enrich each contact. Send the contact's email, or its LinkedIn URL when it has no email, to POST /v1/people/enrich. Send one identifier only.
6. Write back and stamp. PUT /api/v1/contact/{id}/ with the new email, phone and title, plus the stamp field (Close docs, September 2026).
7. Schedule it. Run the script hourly or nightly. For near-live enrichment, subscribe a webhook to the Close contact created event. Run the same enrich step from your endpoint (Close docs, September 2026).

For a one-off list, use the Exports page in the LeadOcean app. It has a filter builder, column picker and price preview, and gives you a CSV to import into Close.

Configuration

The Close API uses HTTP Basic auth: the API key is the username and the password is empty (Close docs, September 2026). Keep both keys in environment variables.

Enrich one contact:

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@acme.com","reveal_email":true}'

Write the result back to Close. Send the complete, merged email and phone lists, not a single new entry. Close's update docs do not say whether a list is merged or replaced, so sending the full list is the safe choice.

curl -X PUT "https://api.close.com/api/v1/contact/cont_ACME123/" \
  -u "$CLOSE_API_KEY:" \
  -H "content-type: application/json" \
  -d '{
    "title": "VP Sales",
    "emails": [
      {"email": "jane@acme.com", "type": "office"}
    ],
    "phones": [
      {"phone": "+14155550133", "type": "mobile"}
    ],
    "custom.cf_YOUR_FIELD_ID": "2026-10-21T09:00:00+00:00"
  }'

Send exactly one identifier per LeadOcean call. Two identifiers return a 400 (LeadOcean docs, September 2026). reveal_email costs no extra record, and phones only come back when it is true. Close expects phones in E.164 format (Close docs, September 2026), so normalise before you write.

Field mapping

The enrich response is one leadocean.person.v1 object. Contact points sit under contact_data (LeadOcean docs, September 2026).

Three dedupe rules keep the CRM clean:

• Stamp first. Select only contacts where the stamp field is empty. A rerun after a crash then costs nothing for contacts already done.
• Merge, do not replace. Read the contact's current emails and phones, add what LeadOcean found, drop exact duplicates, and send the merged list.
• Gate on status. An address that fails the status check never reaches Close. LeadOcean gives no refund for bounces, so read email_status before you send (LeadOcean docs, September 2026).

A person LeadOcean holds nothing for is a 404 and costs nothing. Stamp those contacts anyway, with a note field if you want, so the script does not retry them every night.

Cost at 10,000 rows

10,000 contacts cost $97 on LeadOcean Solo. Close's built-in Enrichment would cost about $750 for one field, on top of your CRM plan.

The Close side comes from Close's own rules. An enrichment action is one field on one record, and it uses 6 credits (Close help, October 2026). The AI credit tiers are $750 for 72,000 credits and $2,000 for 200,000 credits (Close help, October 2026). Included credits reduce the tier you need, for example 15,000 on Growth at ten users. Credits reset monthly and do not roll over.

The two products do different jobs. Close Enrichment uses AI to fill custom fields from the web. LeadOcean returns emails and phones, each with a status, from its own database of 693M people. Use LeadOcean for emails and phones, and Close Enrichment for free-text fields like a company description.

The first 1,000 contacts run on LeadOcean Free. Your Close plan price is separate and unchanged. See pricing for what each LeadOcean plan includes. If you also keep contacts in other tools, the same pattern works in Retool, Notion and Folk.

Troubleshooting

FAQ