Prospeo

Create Your Prospeo Account and Retrieve Your API Key

Navigate to prospeo.io and sign up for an account. After verifying your email, log in to the Prospeo dashboard. Go to Settings → API Key to generate your unique API key. This key is used to authenticate all API requests and to connect Prospeo with third-party platforms like Clay, Make, Zapier, and Maestro. Copy your API key and store it securely — treat it like a password. Note that your API key is tied to your credit balance, so any platform using this key will draw from your account's credits. If you plan to use Prospeo in Clay's BYO API key mode, this is the key you'll paste into Clay's integration settings.

# Store your API key as an environment variable
export PROSPEO_API_KEY='your_api_key_here'

# Verify the key works with a simple curl test
curl -X GET 'https://api.prospeo.io/v1/account' \
  -H 'X-KEY: your_api_key_here'

Connect Prospeo to Clay (BYO API Key Mode)

In Clay, open any Table and add a new enrichment column. Search for 'Prospeo' in the enrichment provider list. When prompted, select 'Use my own API key' rather than the Clay-managed option. Paste your Prospeo API key into the provided field and click Connect. Once connected, Clay will route Prospeo enrichment requests through your Prospeo account, consuming your Prospeo credits directly rather than Clay credits. This is the recommended setup for teams running high enrichment volumes, as BYO API key mode is typically more cost-effective than Clay-managed Prospeo access. Map your input columns (first name, last name, company/domain) to the Prospeo action fields, then save and run the enrichment.

// Clay Table Column Configuration (conceptual)
{
  "enrichment_provider": "Prospeo",
  "auth_mode": "byo_api_key",
  "api_key": "{{env.PROSPEO_API_KEY}}",
  "action": "find_email",
  "input_mapping": {
    "first_name": "{{row.first_name}}",
    "last_name": "{{row.last_name}}",
    "company": "{{row.company_name}}"
  },
  "output_mapping": {
    "email": "{{result.email}}",
    "email_status": "{{result.verification_status}}"
  }
}

Set Up Waterfall Enrichment in Clay for Maximum Email Coverage

To maximize email coverage, configure a waterfall enrichment sequence in Clay where Prospeo acts as a secondary or tertiary provider. In your Clay Table, add your primary email enrichment column (e.g., Apollo or Hunter.io). Then add a second enrichment column that uses Prospeo's Email Finder, but set the 'Only run if' condition to trigger only when the previous enrichment column returns empty or an invalid status. This ensures Prospeo credits are only consumed when the primary source fails, reducing cost while maximizing coverage. Add a final consolidation formula column that selects the first non-empty, valid email across all enrichment columns. This waterfall approach is referenced in Clay's documentation but rarely explained with full configuration context.

// Waterfall logic formula in Clay (pseudo-formula)
=IF(NOT(ISEMPTY(apollo_email)) AND apollo_email_status = 'valid', 
   apollo_email,
   IF(NOT(ISEMPTY(prospeo_email)) AND prospeo_email_status = 'valid',
      prospeo_email,
      hunter_email
   )
)

Install the Prospeo Chrome Extension for LinkedIn Prospecting

Go to the Chrome Web Store and search for 'Prospeo Email Finder' or visit the extension download link from your Prospeo dashboard under Tools → Chrome Extension. Click 'Add to Chrome' and confirm the installation. Once installed, navigate to any LinkedIn profile or Sales Navigator search results page. The Prospeo extension will appear as a sidebar button. Click it to reveal the verified email and phone number for the profile you're viewing, or use the bulk extraction mode on Sales Navigator list pages to export multiple contacts at once. For Sales Navigator exports, Prospeo's integration automatically validates compliance with LinkedIn's 2025 data export policies, flagging records that should be excluded from your outreach list.

Integrate Prospeo with Maestro for Automated Lead Enrichment

In Maestro, navigate to Integrations → Data Enrichment and select Prospeo from the available providers. Enter your Prospeo API key and configure which enrichment actions to trigger and when. A recommended configuration is to trigger the Email Finder action whenever a new lead record enters a Maestro workflow with a name and company present but no verified email. You can also configure Maestro to trigger the Email Verification action on aged records (e.g., leads older than 90 days) to refresh deliverability status before re-engaging them. Set minimum verification status thresholds — for example, only pass leads with a 'valid' or 'accept_all' Prospeo status into active email sequences, and route 'invalid' status leads to a phone-first or LinkedIn sequence instead.

// Maestro workflow trigger configuration (conceptual JSON)
{
  "trigger": "new_lead_created",
  "conditions": [
    { "field": "email", "operator": "is_empty" },
    { "field": "first_name", "operator": "is_not_empty" },
    { "field": "company", "operator": "is_not_empty" }
  ],
  "actions": [
    {
      "type": "enrich",
      "provider": "prospeo",
      "action": "find_email",
      "input": {
        "first_name": "{{lead.first_name}}",
        "last_name": "{{lead.last_name}}",
        "company": "{{lead.company}}"
      },
      "output": {
        "email": "{{lead.email}}",
        "email_status": "{{lead.email_verification_status}}"
      }
    }
  ]
}

Configure the Apollo + Prospeo Verification Workflow

Export your Apollo.io contact list as a CSV, ensuring the export includes first name, last name, company name, and any Apollo-sourced emails. Import this CSV into Prospeo's Bulk Enrichment tool or into a Clay Table configured with Prospeo as the enrichment provider. Map the Apollo email field to a 'verify existing email' action in Prospeo, and map the name/company fields to a 'find email' action as a fallback for records where Apollo returned no email. Prospeo will verify Apollo's emails for deliverability and find missing emails using its own database. Filter the output to retain only records with a Prospeo verification status of 'valid' or 'risky' (depending on your bounce rate tolerance), then import the cleaned list into your sequencing tool. This workflow is endorsed by practitioners including those cited by [ApexAI on LinkedIn](https://www.linkedin.com/posts/apexai-estate_most-agents-think-they-have-a-lead-problem-activity-7387242668940087296-Et04) as a high-performance outreach stack.

# Bulk verification via Prospeo API
curl -X POST 'https://api.prospeo.io/v1/email-verifier' \
  -H 'X-KEY: your_api_key_here' \
  -H 'Content-Type: application/json' \
  -d '{
    "email": "john.doe@company.com"
  }'

# Response
{
  "email": "john.doe@company.com",
  "status": "valid",
  "mx_found": true,
  "smtp_check": true,
  "catch_all": false
}