How to Find a VP of Sales's Phone Number (2026)

The fastest way to find a VP of Sales's phone number is to search a people database for VPs in sales, keep the ones flagged with a phone, then pull the direct dial by person id. A switchboard gets you a gatekeeper. A direct dial or mobile gets you the VP.

TL;DR

• Search with jobLevel: VP, jobFunction: Sales & Business Development and hasPhone: true. Size the list free, then pull numbers only for people you will call.
• Time: about 15 minutes for one VP, about 30 for a list of 500. Cost: 1 LeadOcean record per number pulled.
• Check the calling rules first. The API returns a number, not permission to dial it.

Prerequisites

• A LeadOcean account on the free plan: app.leadocean.io/register. Free gives you 1,000 records for life, every feature and 5 requests a second.
• An API key from the app, exported as $LEADOCEAN_API_KEY.
• curl and jq.
• A target: a company domain for one VP, or a filter set for a list.

Step 1: Pick the right VP and the right kind of number

"VP of Sales" is a title, not a level. Some companies say VP Sales, Vice President of Sales or VP Revenue. Filtering on the level VP plus the function Sales & Business Development catches all of them in one pass.

A main line rings reception. A direct dial or mobile rings the person. The main line sends you to a queue.

LeadOcean returns each number with a type: mobile, direct or office. Take mobile and direct first. Treat office as a fallback. The type is the source's own label, not a closed list. Read a value you do not recognize, such as switchboard or unknown, as a line of unknown kind, not as an error.

Step 2: Size the VP list for free

Count before you spend. A count costs 0 records. Ask the MCP tool leadocean_count_leads, or send count=true with limit=1 as query parameters on the search endpoint.

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 '{
    "jobLevel": ["VP"],
    "jobFunction": ["Sales & Business Development"],
    "country": ["US"],
    "hasPhone": true
  }'

meta.total is capped at 100,000 on this call. Enum values are exact strings, so check them with leadocean_list_enum_values before you filter.

Step 3: Search for VPs who have a phone on file

Search returns people, one record per row. Filters are arrays, the body is flat JSON, and limit runs 1 to 100.

curl -s -X POST "https://api.leadocean.io/v1/people/search" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jobLevel": ["VP"],
    "jobFunction": ["Sales & Business Development"],
    "country": ["US"],
    "employeeRange": ["51-200"],
    "hasPhone": true,
    "limit": 25
  }' | jq '.meta, (.data | length)'

Page on with meta.nextCursor. One search stops at 10,000 rows (meta.depthCapped), so narrow by industry or headcount instead of paging deeper. To find one named company's VP of Sales, add "domain": ["acme.com"] to the same search.

Step 4: Pull the direct dial

Spend records last. Each phone pull is one record, so a 25-person test batch costs 25 records on the free plan.

Take the person id from meta.source_ids.person_id on a search row and ask for the phone. This costs 1 record per call, including a call that finds nothing.

curl -s "https://api.leadocean.io/v2/people/phone?person_id=1234567" \
  -H "x-api-key: $LEADOCEAN_API_KEY" | jq

Numbers come back best first. In Claude or any MCP client, the tool leadocean_find_phone does the same job.

For a list over a few hundred people, skip the loop. Start an export with POST /v1/exports. One export takes up to 50,000 rows, and an account gets 500,000 a day. Bulk CSV export is not on Free: it comes with Solo ($97 a month) and Agency ($497 a month, 50k rows a file).

curl -s -X POST "https://api.leadocean.io/v1/exports" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "us-vp-sales-with-phone",
    "filters": {
      "jobLevel": ["VP"],
      "jobFunction": ["Sales & Business Development"],
      "country": ["US"],
      "hasPhone": true
    },
    "limit": 500,
    "preset": "full",
    "reveal": "email_phone"
  }'

Poll GET /v1/exports/{id}, then fetch GET /v1/exports/{id}/download. You can build the same export in the app: filter builder, column picker, price preview, then download.

Step 5: Check what you may call before you dial

Having a number is not the same as being allowed to call it. The rules differ by country, by whether the line is a mobile, and by whether you use an autodialer or a recorded message.

• The API does not return a usable do-not-call flag. The v2 phone endpoint omits dnc because the field is unpopulated at source. Its absence is not clearance.
• Run your own list through the registries that apply to you before a campaign.
• In the US, check whether the Telemarketing Sales Rule and the National Do Not Call Registry apply to your calls before you start.
• A VP at a small firm may give out a personal mobile as the business line. Ask your counsel, and keep a suppression list.

This is not legal advice.

What you get

Expect a short list, not a dump. Every row has a number on file because of hasPhone, but some numbers will be an office line. Sort by type and call direct and mobile first.

A free count run on 2026-10-21 with leadocean_count_leads (jobLevel VP, jobFunction Sales & Business Development, country US, hasPhone true, no email filter). It is a phone-flag count. It is not a verified-number count.

{
  "total": 275259,
  "totalIsExact": true,
  "distinctCompanies": 135386,
  "facets": {
    "country": [{ "value": "US", "count": 275259 }],
    "industry": [
      { "value": "Financial Services", "count": 20673 },
      { "value": "Software Development", "count": 17550 },
      { "value": "Banking", "count": 12574 }
    ],
    "company_size": [
      { "value": "11-50", "count": 56082 },
      { "value": "51-200", "count": 49715 },
      { "value": "1-10", "count": 42455 }
    ]
  }
}

The phone call returns this shape. It is the response shape from the API reference, with placeholder values.

{
  "success": true,
  "data": {
    "found": true,
    "phones": [
      { "phone": "+1 415 555 0133", "type": "direct" },
      { "phone": "+1 415 555 0134", "type": "office" }
    ]
  }
}

The function filter is a classification, so a few rows will be a VP of customer success or partnerships. Read the title column before you dial.

Troubleshooting

FAQ