Introducing Bring Your Own Key (BYOK)
We're thrilled to announce the launch of . This is the first phase of our BYOK initiative, designed to provide greater flexibility, cost control, and customization options for your data enrichment needs.
What Is BYOK?
Bring Your Own Key allows you to integrate your existing third-party data provider subscriptions directly into our platform. Instead of relying solely on our built-in enrichment sources, you can now leverage your own API keys from providers you already trust and pay for separately.
This means:
Use your existing subscriptions – no double-paying for data
Maintain your provider relationships – keep your negotiated rates and terms
Greater transparency – track usage directly with your providers
Enhanced control – manage your data sources according to your preferences
What's Included in This Release
In this initial phase, we're introducing support for two industry-leading enrichment providers:
1. Apollo
Enrichment Capabilities: Email addresses and phone numbers
Use Case: Ideal for B2B contact enrichment with extensive database coverage
What You Need: An active Apollo API key
2. Lusha
Enrichment Capabilities: Email addresses and phone numbers
Use Case: Excellent for accurate direct dial phone numbers and verified emails
What You Need: An active Lusha API key
How to Set Up BYOK
Step 1: Obtain Your API Keys
Before you begin, make sure you have valid API keys from Apollo and/or Lusha. You can obtain these from:
Apollo: Your Apollo account settings or dashboard
Lusha: Your Lusha account settings or API section
Step 2: Navigate to Settings in Sprouts
Click on Settings in the main navigation
Select Integrations from the settings menu
Step 3: Configure Your API Key
Choose the provider you want to add (Apollo or Lusha)
Click Add API Key or Configure
Enter your API key in the provided field.
Step 4: Test Your Connection
Click Test Connection to verify your API key
Wait for the validation process to complete
You'll see a success message if the connection is valid
If the test fails, double-check your API key and try again
Step 5: Start Enriching
Once your connection is successfully tested, your new provider(s) will automatically become available as enrichment sources in your waterfall configuration.
How BYOK Works with Your Enrichment Waterfall
The Process Remains Familiar
The good news? Your existing enrichment workflow doesn't change. We've designed BYOK to integrate seamlessly into your current processes.
Setting Up Your Waterfall
For Email / PhoneEnrichment:
Navigate to your contact enrichment settings
Select the Email/ phone Enrichment tile
You'll now see Apollo and/or Lusha (depending on which keys you've added) as available sources alongside your existing options
Drag and drop sources to arrange them in your preferred priority order
Save your configuration
How the Waterfall Works
When you enrich a contact:
The system attempts enrichment using the first source in your waterfall
If the first source doesn't return data, it automatically moves to the second source
This continues down the waterfall until data is found or all sources are exhausted
BYOK sources work exactly like native sources – no special handling required
Key Benefits
Enhanced Control
Source prioritization: Decide which providers to use first in your waterfall
Provider selection: Choose providers that align with your data quality standards
Easy management: Add, remove, or update API keys anytime in Settings
Better Data Coverage
Multiple sources: Combine BYOK providers with our native sources for maximum coverage
Redundancy: If one source doesn't have data, automatically fall back to the next
Higher match rates: More sources = better chance of finding the data you need
Use Cases
Scenario 1: Existing Apollo Customer
You already have an enterprise Apollo subscription with significant API credits. Now you can:
Add your Apollo API key to our platform
Set Apollo as your primary enrichment source
Maximize ROI on your existing Apollo investment
Use our native sources as backup
Scenario 2: Multi-Provider Strategy
You use different providers for different data types:
Use Lusha (known for phone accuracy) for phone enrichment
Use Apollo (known for email coverage) for email enrichment
Create optimized waterfalls for each data type
Scenario 3: Cost Optimization
You want to control enrichment costs:
Use BYOK providers first (your existing subscription)
Fall back to native sources only when BYOK sources don't return data
Track usage across all providers
Important Notes
API Key Management
You can update or remove API keys at any time
Removing an API key will immediately remove that source from your waterfall
Always test your connection after updating an API key
Usage and Billing
Usage through BYOK sources is billed directly by your provider (Apollo/Lusha)
Check your provider's dashboard for consumption tracking
Make sure your API keys have sufficient credits/quota
Source Availability
BYOK sources only appear if you've successfully configured the corresponding API key
If you remove an API key, that source disappears from your waterfall options
You can have both Apollo and Lusha configured simultaneously
What's Next
This is just the beginning of our BYOK initiative. In future releases, we plan to:
Add support for additional enrichment providers
Introduce BYOK for company-level enrichment
Provide usage analytics within our platform
Enable advanced routing rules and conditions
We want your feedback! Let us know which providers you'd like to see next and how we can make BYOK even better.
Summary
BYOK represents a significant step forward in giving you control over your enrichment strategy. By allowing you to use your own Apollo and Lusha API keys, we're enabling you to:
Maximize your existing provider investments
Increase data coverage with multiple sources
Maintain familiar workflows
Optimize costs and performance
Ready to get started? Head over to Settings → Integrations and configure your first BYOK source today!