Skip to main content
BYOK lets a workspace use a provider key that you own. The provider charges your provider account for operations that use this key. Deepline does not charge Deepline credits for those provider operations. Other Deepline or provider charges can still apply. Use the current pricing page for Deepline prices. Use each provider’s account and documentation for provider prices and quotas.

​
What BYOK means for your GTM budget

Not every team should use BYOK. Here is a straight breakdown of who benefits most and who should skip it. Best for teams with existing provider contracts. If you already pay Apollo, Crustdata, Hunter, or People Data Labs directly, BYOK lets you route those same keys through Deepline without double-paying. You keep your negotiated rates, your existing usage dashboards, and your billing relationship. Deepline adds waterfall logic and unified output schemas on top — nothing changes on the provider side. Best for testing multiple providers side-by-side. When you are evaluating whether Crustdata or People Data Labs returns better company data for your ICP, BYOK lets you run both through the same waterfall and compare hit rates without committing to either vendor’s annual contract. Connect free-tier keys from each, run a sample batch, and measure coverage before you buy. Not ideal if you have no provider accounts. Use managed credits for an action when Deepline offers managed access. You can add a provider key later.

​
Supported providers

API-key providers listed below accept BYOK connections. Connect any combination. Apollo also accepts customer-owned keys, but it must be connected in the Deepline dashboard and is not available through platform-managed env fallback.

​
Enrichment and prospecting

Versium offers managed access for actions with published match-credit pricing. Contact Append and Predictive Scores require a connected workspace key because Versium’s supplied pricing table does not fully price those actions.

​
Outbound sequencing

​
CRM (OAuth)

These 3 providers use OAuth instead of API keys. Connect them through the Deepline dashboard.

​
Internal

​
How to connect a key

Open the dashboard, pick the provider, paste your API key, and save. The key is encrypted at rest and scoped to your workspace. Repeat for each provider you want to connect. After saving, enrichment calls to that provider use your key automatically.

​
Option 2: API

Set a key programmatically via the REST API. This endpoint requires an organization-admin session or API key:

​
Option 3: Environment variable

For local development or self-hosted deployments, set supported provider env vars directly. Apollo is excluded from env fallback; connect Apollo in the Deepline dashboard instead.
The env var names match the table above exactly. When Deepline detects a provider env var, it uses that key automatically — no additional configuration needed.

​
Connecting multiple providers

Connect as many providers as you need. Each key is stored independently. Add each provider in the dashboard at https://code.deepline.com/dashboard/keys:
  • Apollo
  • Hunter
  • LeadMagic
  • ZeroBounce
All 4 keys are now available for waterfall enrichment. When you run a name_and_domain_to_email_waterfall, Deepline queries each connected provider in sequence and returns the first verified hit.

​
Mix and match: BYOK + managed credits

You do not have to choose one model for all providers. Deepline supports mixing BYOK and managed credits at the provider level within the same workspace. Example setup: This example waterfall can use different billing modes for different providers. Check the available billing details before you run a large input. After you add or remove a key, inspect the provider action before the next run. The action shows whether it can use a provider key or managed access.

​
Key storage and security

Deepline encrypts stored provider credentials. Credential-list responses redact the secret value. Access checks bind a stored credential to its workspace. Remove a credential in the dashboard when the workspace must stop using it.

​
Frequently asked questions

Retry behavior depends on the action and error type. Inspect the run error and provider quota. Follow the returned retry guidance before you start the operation again.
No. For a given provider, your workspace uses either your BYOK key or managed credits — not both simultaneously. If you connect a BYOK key for Apollo, all Apollo calls use your key. Removing the Apollo key disables Apollo calls until a personal key is reconnected; Deepline cannot provide platform-managed Apollo access. For other supported providers, removing your key can fall back to managed credits when platform-managed access is available. This prevents ambiguous billing where you cannot tell which key was charged.
No. Waterfall enrichment works with managed credits, BYOK keys, or any combination. The waterfall engine is agnostic to how each provider is authenticated. If you have zero keys connected, managed credits handle everything. If you have 3 BYOK keys and 2 managed-credit providers, the waterfall uses all 5 in the configured priority order.
Review the run details and your provider usage dashboard. The available billing fields depend on the action and provider.

Quick Start

Install Deepline and run your first enrichment in 60 seconds.

Pricing Schedule

Full per-endpoint pricing for managed credits across all providers.

API Reference

REST API documentation for keys, enrichment, and waterfall endpoints.

Waterfall Enrichment

How multi-provider waterfall logic works under the hood.