LeadOcean + Clay: LinkedIn profile lookalikes to an enriched outreach list

You give a Clay table one LinkedIn URL of someone who already bought. You get back a list of people with the same title, level, function and country, each with a work email. LeadOcean does the data work in three HTTP calls, and Clay holds the rows. The same recipe runs from a script if you have no Clay seat.

How it works

1. Trigger. Add a column with the seed URL, for example https://www.linkedin.com/in/jane-doe-example. One seed per row.

1. Read the persona. Add an HTTP API column that calls POST /v1/people/enrich with linkedin_url. The current role is in contact_current_experiences[], with job_title and job_functions[]; the country is in the profile_data address. A miss is a 404 and costs nothing.

1. Size the list. Call /v1/people/search?count=true with limit 1 and the persona as filters. It is free, and meta.total caps at 100,000.
2. Pull the lookalikes into a new table. Start a second table from the source "Import data from an HTTP API" with GET /v1/people/search and the persona filters. Set the results path to data and paginate on the cursor query parameter with meta.nextCursor (Clay docs, October 2026). Each person becomes a row. One search pages to 10,000 rows.

1. Enrich each row. Add an HTTP API column on POST /v1/people/enrich with the row's meta.source_ids.person_id and reveal_email: true. Reveal costs no extra record.
2. Send it on. Filter on email_status, then push the rows to your CRM or sequencer.

Clay's HTTP API column lets you set a rate limit and a conditional run per column (Clay docs, October 2026). Set 5 requests a second on Free and 50 on Solo, and run only when the URL cell is filled.

Configuration

The enrich call from step 2, as the HTTP column sends it:

curl -X POST https://api.leadocean.io/v1/people/enrich \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"linkedin_url": "https://www.linkedin.com/in/jane-doe-example"}'

The search call from step 4. Values are placeholders for what step 2 returned. In the Clay source, send the same filters as query parameters, comma-separated:

curl -X POST https://api.leadocean.io/v1/people/search \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title": ["Head of Growth"], "jobLevel": ["Director"],
       "jobFunction": ["Sales & Business Development"],
       "country": ["US"], "limit": 100}'

Enum values are exact strings. Check them with list_enum_values before you map anything.

Field mapping

Cost at 10,000 rows

On LeadOcean, 10,000 lookalikes plus the seed is 10,001 records. Enriching each row for its email adds 10,000, so 20,001 in total. Free holds 1,000 records for life, enough to prove the recipe. Solo at $97 a month covers the volume, with bulk CSV included. See pricing.

Clay's HTTP API column starts on Growth: $495 a month billed monthly, $446 billed yearly. Each call uses one Action (Clay pricing, September 2026). The enrich column on 10,000 rows is 10,000 Actions, inside Growth's 40,000.

The FullEnrich template does the same job with its own search and email credits. Search costs 0.25 credits per person and a work email 1 credit (FullEnrich docs, September 2026). That is 12,500 credits for 10,000 rows. The 15,000-credit tier is $720 a month, or $655 a month billed yearly (FullEnrich pricing, September 2026).

Troubleshooting

FAQ