LeadOcean + Clay: find champions at target accounts from only a website domain

You paste a column of website domains into Clay. Two HTTP API columns return the company facts LeadOcean holds and the people in champion-type roles at each account. Clay's own template also finds revenue and customers and drafts an email (Clay template, September 2026). This recipe covers the data half with LeadOcean and leaves the email to you.

A champion is the person who will push your product internally. LeadOcean has no "champion" flag. You define the role by title and job function, then search for it. The HTTP API column needs Clay Growth or higher (Clay pricing, September 2026).

How it works

1. Get a free key. Sign up at app.leadocean.io/register. No card, 1,000 records.
2. Paste the domains. One bare domain per row, such as acme.com.
3. Add a company column. HTTP API, POST to /v1/companies/enrich with the domain. It returns firmographics.
4. Add a champions column. HTTP API, POST to /v1/people/search with the domain and the titles you call champions.
5. Run five rows first. Check both columns fill, then run the table.
6. Get emails for the keepers. Send the person_id of each champion you want to POST /v1/people/enrich.

Define the champion before step 4. A common choice is a Director or Manager in the function that uses your product. Check the exact enum strings free with leadocean_list_enum_values. To size a target list first, see find target accounts and what a target account list is.

Configuration

/Domain is Clay's column reference. Enum values are exact strings.

Column 1 (company)
Method:   POST
URL:      https://api.leadocean.io/v1/companies/enrich
Headers:  x-api-key: <your LeadOcean key>
          content-type: application/json
Body:     { "domain": "/Domain" }

Column 2 (champions)
Method:   POST
URL:      https://api.leadocean.io/v1/people/search
Headers:  x-api-key: <your LeadOcean key>
          content-type: application/json
Body:     {
            "domain": ["/Domain"],
            "jobLevel": ["Director", "Manager"],
            "jobFunction": ["Sales & Business Development"],
            "limit": 3
          }
Field paths to return:
          data
          meta.total

Test the same two calls in a terminal first.

curl -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"}'

curl -X POST "https://api.leadocean.io/v1/people/search" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "content-type: application/json" \
  -d '{"domain":["acme.com"],"jobLevel":["Director","Manager"],"jobFunction":["Sales & Business Development"],"limit":3}'

Clay shows data as one list in one cell. One row per person needs a second step in Clay.

Field mapping

The company record has no customers field (LeadOcean docs, October 2026). Clay's template finds customers with another source.

Cost at 10,000 rows

10,000 domains, one company lookup each and three champions each, come to about 40,000 records. LeadOcean's Free plan holds 1,000 records for life, so it covers about 250 domains. Solo at $97 a month covers 100k search records every 5 hours and 10k enrichments every 5 hours, so one run fits (LeadOcean pricing). A lookup that finds nothing costs nothing.

Clay uses one Action per HTTP call. Two columns over 10,000 rows is 20,000 Actions. Growth starts at $495 a month billed monthly, or $446 billed yearly, and includes 40,000 Actions (Clay pricing, September 2026). The enrich column adds more Actions per keeper.

Size the people first. A count is free, and meta.distinctCompanies shows how many employers a filter spans.

Troubleshooting

FAQ