Apollo.io Integration
BetaNative connector
Verify Apollo contacts and record the result in custom fields or as a list label.
Connect Apollo.io
Dashboard → Integrations → Apollo.io
DashboardBounce guarantee
Connect your sending provider and bounced "deliverable" addresses are refunded automatically
How it worksConnect with
API key
Category
Cold Outreach
Write-back
Fields + tags
Auto-verify new
No
How to Connect
In RocketVerifier open Dashboard → Integrations → Apollo.io, paste the credentials below (an Apollo master API key) and click Connect. They are validated against the platform before anything is saved.
Pick the source to sync, the schedule and the write-back options in the integration settings, then click Sync now or wait for the schedule.
| Field | Required | Where to find it |
|---|---|---|
| API key | Required | An Apollo API key created as a master key; a master key is required to update contacts. |
Credentials are stored encrypted and are only ever sent to the platform's own API hosts.
What It Syncs
Sources
All contacts or any contact list.
Incremental syncs
Contacts updated since the last sync. Apollo caps one search at 50,000 records.
Schedules & Credits
- Schedule: Manual only, Daily, Weekly or Monthly. Each run syncs the source chosen in the settings; Sync now starts one immediately. Only one sync runs per integration at a time.
- Mode: Full re-checks every contact in the source except those verified in the last N days (default 30, 0-365); Incremental only checks contacts changed since the last sync.
- Each sync creates a regular verification job: 1 credit per unique address, and
unknownresults are refunded when it completes. If the balance is too low the sync stops withinsufficient_creditsbefore anything is charged. - Results are written back when the job completes; the sync history in the dashboard shows updated, failed and skipped counts per run.
Write-back
Fields ("Write status fields")
rv_email_statusrv_email_sub_statusrv_email_scorerv_verified_at
Written only if you created typed custom fields with these names (or RV Email Status, ...) in Apollo; Apollo has no API to create them.
Tags ("Tag contacts with their status")
Without those fields the status is written as the list label rv-status:<status>; the contact's existing lists are kept.
Status values are deliverable, undeliverable, risky and unknown (disposable addresses are undeliverable, catch-all addresses unknown). Sub-status is a sub_status value (none when there is no extra detail), score is 0-100 and verified-at is an ISO 8601 UTC timestamp.
Action Rules
In the integration settings, pick an action per result: Invalid, Disposable, Risky, Catch-all, Unknown or Valid. Actions run after the field/tag write-back.
Add tag
Adds the action label.
Beta: the Apollo.io connector is new. Sync reports list every contact that could not be updated; please tell us if something looks wrong.
Need Help?
Having trouble connecting Apollo.io? We're here to help.
