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

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

TL;DR

• Filter VPs in Advertising & Marketing with hasPhone: true, size the list for 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 a direct dial over a switchboard

A main line rings reception. A direct dial or mobile rings the person. The main line rarely gets you through to a VP.

LeadOcean returns each number with a type, such as mobile, direct or office. Call 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. A mobile carries the strictest calling rules (see Step 5).

Two filters define the target. jobLevel is VP, and jobFunction is Advertising & Marketing. Enum values are exact strings, so check them with leadocean_list_enum_values before you search.

Three habits keep the spend low. Pull a number only for VPs you will call this week. Narrow by employeeRange so you call companies that fit your offer. Read the title column before you dial, because a VP of Marketing and a VP of Brand are different buyers.

Step 2: Size the VP list for free

Count before you spend. A count costs 0 records. Use 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": ["Advertising & Marketing"],
    "country": ["US"],
    "hasPhone": true
  }'

meta.total is capped at 100,000 on this call. Narrow by country or employeeRange when a list runs past it.

Step 3: Search for VPs with a phone on file

Search returns people, one record per row. The body is flat JSON, filters are arrays, 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": ["Advertising & Marketing"],
    "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 Marketing, add "domain": ["acme.com"] to the same search.

Step 4: Pull the direct dial

Spend records last. Each phone pull costs 1 record per call, including a call that finds nothing. A 25-person test batch costs 25 records.

Take the person id from meta.source_ids.person_id on a search row and ask for the phone.

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, and best points at the top one.

For a list over a few hundred people, skip the loop. Start an export with POST /v1/exports and the full preset, which includes phone_1_number and phone_2_number. 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-marketing-with-phone",
    "filters": { "jobLevel": ["VP"], "jobFunction": ["Advertising & Marketing"], "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 permission to call it. Rules differ by country, by whether the line is a mobile, and by whether you use an autodialer or a recorded message.

• The phone endpoint returns no do-not-call flag. Its absence is not clearance.
• Run your 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's personal mobile can carry stricter rules than a business line. Ask your counsel, and keep a suppression list.

This is not legal advice.

What you get

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

A free count run on 2026-10-21 with leadocean_count_leads (job level VP, job function Advertising & Marketing, hasPhone true). It is a phone-flag count worldwide, not a verified-number count.

{
  "total": 171126,
  "totalIsExact": true,
  "distinctCompanies": 88008,
  "facets": {
    "country": [
      { "value": "US", "count": 100475 },
      { "value": "CA", "count": 3101 },
      { "value": "IN", "count": 2425 }
    ],
    "industry": [
      { "value": "Financial Services", "count": 11962 },
      { "value": "Software Development", "count": 9532 },
      { "value": "Banking", "count": 8614 }
    ]
  }
}

Financial services, software and banking lead the list, so split by industry before you write a call script. 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" }
    ],
    "best": { "phone": "+1 415 555 0133", "type": "direct" }
  }
}

Troubleshooting

FAQ