How to Find a General Counsel's Email Address (2026)

The fastest way to find a General Counsel's email is to look it up in a contact database, not to guess it. Search by company domain and the Legal function, enrich the person, then read the email status before you send. This guide does that against LeadOcean with curl and spends 3 records.

Examples use placeholders (Acme, acme.com, Jane Doe). Swap in your own domain.

TL;DR

• General Counsel emails come from three places: a database lookup, a pattern guess at the company domain, or the company's own filings and press pages. Only the first gives you a deliverability status.
• Filter by title General Counsel and the Legal function, enrich with reveal_email, and send only to verified or catch_all_valid addresses.
• Takes about 10 minutes and spends 3 of the 1,000 free records. Sizing the audience first costs nothing.

Prerequisites

• A LeadOcean account. The free plan gives 1,000 records one-off, no card: register here.
• An API key from the app, exported as $LEADOCEAN_API_KEY.
• curl and jq.

export LEADOCEAN_API_KEY="paste-your-key-here"

Every request goes to https://api.leadocean.io with the header x-api-key. A free key has both scopes, search and enrich, and runs at 5 requests a second.

Step 1: Size the General Counsel list before you pull it

Send count=true and limit=1 as query parameters and the call returns a total without spending a record. Filters go in a flat JSON body, and every filter is an array of strings.

curl -s -X POST "https://api.leadocean.io/v1/people/search?count=true&limit=1" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": ["General Counsel"],
    "jobFunction": ["Legal"],
    "salesRegion": ["NORAM"]
  }' | jq '.meta'

Titles vary: "General Counsel", "Chief Legal Officer", "Head of Legal", "VP, Legal". A title keyword catches only the wording you typed. The Legal function catches the whole department, so use it alone when you want every legal leader.

meta.total is capped at 100,000, and meta.totalIsExact tells you whether it is a floor. Enum values are exact strings: Legal works, Law is not a value.

Step 2: Search for the General Counsel at one company

Add the company's domain to find the General Counsel at that account. Each person returned costs one record, so keep limit small.

curl -s -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"],
    "title": ["General Counsel"],
    "jobFunction": ["Legal"],
    "limit": 2
  }' > gcs.json

jq '.data | length' gcs.json

Search rows are thin: they carry has_email and has_phone flags, not the address itself. Read the titles in the rows before you spend a record on enrichment. The keyword also matches "Deputy General Counsel" and "Assistant General Counsel", and you want the one who owns the buying decision.

A small company often has no General Counsel at all. Try "title": ["Head of Legal"], or drop the title and use "jobLevel": ["C-Team"] with the Legal function.

Step 3: Enrich the person to get the email

Each search row carries an id at meta.source_ids.person_id. Send it back to enrich that exact person. Enrich takes exactly one of linkedin_url, email, phone or person_id.

PID=$(jq -r '.data[0].meta.source_ids.person_id' gcs.json)

curl -s -X POST "https://api.leadocean.io/v1/people/enrich" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"person_id\": \"$PID\", \"reveal_email\": true}" > person.json

This costs one record. reveal_email costs nothing extra and returns every email we hold for that person. If we hold nothing, you get a 404 and no charge. There is no lookup by name plus domain: search first, then enrich by person_id.

Step 4: Verify before you send

Read email_status and send only to addresses worth sending to. A verified or catch_all_valid status is safe. A catch_all status means the domain accepts everything, so the mailbox may not exist.

jq -r '.data.contact_data.contact_emails[]
  | select(.status == "verified" or .status == "catch_all_valid")
  | .email' person.json

Bounced emails are not refunded, so treat every other status as a no-send. The full list of statuses is verified, catch_all_valid, catch_all, risky, unknown, untested, invalid, role, disposable, spam_trap, abuse, derived and none.

Step 5: Use a pattern only when the lookup finds nothing

When the General Counsel is not in the data, guess at the company domain, then verify the guess before you send. Four common patterns:

first.last@acme.com    jane.doe@acme.com
flast@acme.com         jdoe@acme.com
first@acme.com         jane@acme.com
firstl@acme.com        janed@acme.com

Find the pattern from any other address you already hold at that domain, then apply it to the General Counsel's name. Never send to a guessed address that has not been verified. A guess at a catch-all domain always looks valid and tells you nothing.

Keep the first email short, name one legal problem you solve, and ask one question. A shared address such as legal@ goes to a team queue, not the person, so skip it.

Step 6: Pull the whole list as a CSV

For a list rather than one person, start an export. POST /v1/exports takes up to 50,000 rows a request and 500,000 a day. Each row costs one record. Bulk CSV export is not on the Free plan.

curl -s -X POST "https://api.leadocean.io/v1/exports" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "general-counsel-noram",
    "filters": {
      "title": ["General Counsel"],
      "jobFunction": ["Legal"],
      "salesRegion": ["NORAM"]
    },
    "limit": 1000,
    "preset": "full"
  }'

Poll GET /v1/exports/{id}, then download from GET /v1/exports/{id}/download. The app's Exports page does the same with a filter builder, a column picker and the record price before you start. It needs no code.

What you get

The Step 1 count is free. The free MCP tool leadocean_count_leads ran these filters on 2026-10-21: title General Counsel, jobFunction Legal, split by salesRegion. It counts people with a verified, catch_all_valid or catch_all email by default, so these are mailable counts.

The four regions sum to 68,070, less than the worldwide figure, because some people carry no region. The worldwide set spans 28,535 distinct companies. Without the email filter the same worldwide filters match 196,375 people, so about 4 in 10 of them have an address worth sending to. Each call returned totalIsExact: true and credits: 0.

The title keyword also matches deputy and assistant roles. In the worldwide set, 45,285 people sit in the c_suite band, 29,194 in director and 4,865 in vp. Add a seniority filter if you want only the top of the department.

A record-level response has the shape below (response shape from the API reference, placeholder values):

{
  "success": true,
  "data": {
    "profile_data": { "name": "Jane Doe", "title": "General Counsel", "company": "Acme" },
    "contact_data": {
      "has_email": true,
      "email_status": "verified",
      "contact_emails": [
        { "email": "jane.doe@acme.com", "type": "work", "status": "verified" }
      ]
    }
  },
  "meta": { "source": "leadocean" }
}

Each record carries its own fetched_at date, and the dataset refreshes monthly. Check the date on anything you plan to act on.

Troubleshooting

FAQ