RocketVerifier
Docs/Integrations/Reply.io
↩️

Reply.io Integration

Beta

Native connector

Verify Reply.io contacts and finish or opt out bad addresses from your sequences.

Connect Reply.io

Dashboard → Integrations → Reply.io

Dashboard

Bounce guarantee

Connect your sending provider and bounced "deliverable" addresses are refunded automatically

How it works

Connect with

API key

Category

Cold Outreach

Write-back

Fields

Auto-verify new

No

How to Connect

1

In RocketVerifier open Dashboard → Integrations → Reply.io, paste the credentials below (your Reply.io API key) and click Connect. They are validated against the platform before anything is saved.

2

Create the contact custom fields below in Reply (Settings → Custom fields); Reply ignores unknown keys.

3

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.

FieldRequiredWhere to find it
API keyRequiredYour Reply.io API key (from Reply's API settings).

Credentials are stored encrypted and are only ever sent to the platform's own API hosts.

What It Syncs

Sources

All contacts or any campaign.

Incremental syncs

Reply.io has no change filter, so an incremental sync reads the whole source; contacts verified within the skip window are still skipped.

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 unknown results are refunded when it completes. If the balance is too low the sync stops with insufficient_credits before 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_status
  • rv_email_sub_status
  • rv_email_score
  • rv_verified_at

Contact custom fields (create them in Reply first).

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.

Pause in campaigns

Marks the contact as finished in all sequences.

Unsubscribe

Opts the contact out.

Beta: the Reply.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 Reply.io? We're here to help.

Contact SupportAll Integrations