How to Find a CRO's Email Address (2026)

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

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

TL;DR

• CRO emails come from three places: a database lookup, a pattern guess at the company domain, or the company's own press pages. Only the first gives you a deliverability status.
• Search by domain and the full title, enrich with reveal_email, and send only to verified or catch_all_valid addresses.
• Takes about 10 minutes and spends 4 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.

Step 1: Size the CRO 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": ["Chief Revenue Officer"],
    "jobLevel": ["C-Team"],
    "salesRegion": ["NORAM"]
  }' | jq '.meta'

Use the full title, not CRO. In finance and security, CRO also means Chief Risk Officer, and a bare CRO keyword pulls those people in. meta.total is capped at 100,000, and meta.totalIsExact tells you whether it is a floor.

Enum values are exact strings: C-Team works, c-level returns nothing. The regions are NORAM, LATAM, EMEA and APAC.

Step 2: Search for the CRO at one company

Add the company's domain to find the CRO 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": ["Chief Revenue Officer"],
    "limit": 3
  }' > cro.json

jq '.data | length' cro.json

Title values are keywords. Wrap one in square brackets, such as ["[Chief Revenue Officer]"], for an exact match. Search rows are thin: they carry has_email and has_phone flags, not the address itself.

If the company has no CRO, the revenue leader may sit under another title, such as Chief Commercial Officer or Chief Growth Officer. Add those as extra title values and read the rows before you enrich.

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' cro.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 a CRO is not in the data, guess at the company domain, then verify the guess before you send. Four patterns cover most corporate mail setups:

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 CRO'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.

A CRO owns the number for sales, marketing and customer success, so the inbox is crowded. Keep the first email to four lines, name one pipeline problem, and ask one question. A role address such as sales@ carries the role status and is not a personal mailbox, 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 Free: it is included on Solo ($97 a month) and Agency ($497 a month).

curl -s -X POST "https://api.leadocean.io/v1/exports" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "cros-noram",
    "filters": {
      "title": ["Chief Revenue Officer"],
      "jobLevel": ["C-Team"],
      "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-01: title keyword Chief Revenue Officer, jobLevel C-Team, 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 7,390, less than the worldwide figure, because some people carry no region. Each call returned totalIsExact: true and credits: 0. Of the worldwide total, 5,195 are in the US. Title keywords match any title containing those words, so read a sample before you build a campaign on the total.

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": "Chief Revenue Officer", "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