KoldReach Guide
How to Add an Enrichment API Key to KoldReach
What you'll accomplish
KoldReach currently supports enrichment providers Prospeo, Apollo, and Hunter. Their keys are managed in Settings → Contact enrichment. Keys saved in Settings are encrypted in the profile and act as per-user overrides; environment variables can remain a fallback in managed deployments.
Before you begin
- A key for Prospeo, Apollo, or Hunter
- Permission to use that provider
- A private browser session
Step-by-step instructions
- 1
Open Contact enrichment
Open Settings and locate Contact enrichment. Review the provider cards and their current status before changing anything.
- 2
Select the provider
Choose the provider that issued your key: Prospeo, Apollo, or Hunter. Use the provider’s own dashboard to create or copy a key; KoldReach does not generate provider credentials.
- 3
Paste the key into the password field
In the provider card, use Add API key or Replace API key. Paste the key into the password-type field and select Save key. The interface should show Key saved when the action succeeds.
- 4
Set provider priority
Use the Primary, Secondary, and Fallback selectors. KoldReach stops when a provider returns a usable email, so put the provider you want to try first in Primary and select Save priority.
- 5
Verify without exposing the key
Confirm the card shows a connected state or saved-key source, then run one permitted LinkedIn lookup from Add Person. Never paste the key into a sequence, browser-visible source code, issue, or log.
Tips and troubleshooting
Wrong integration
The current Settings UI names Prospeo, Apollo, and Hunter. Do not document or paste keys for an unlisted provider.
Key is exposed
If a real key is exposed, revoke it at the provider immediately and create a replacement. Do not continue using a key that may have been copied.
Assuming a saved key changes everyone’s settings
Saved keys are encrypted per-user overrides. Managed environment-variable fallbacks are a separate deployment concern.
Completion checklist
- □ Provider is one of the supported three
- □ Key was obtained privately
- □ Save key returned success
- □ Priority was reviewed and saved
- □ A lookup was tested without revealing the key