LeadOcean + Reply.io: Import Verified Leads Into Sequences

You get a three-part pipeline: a LeadOcean export, split by email_status, imported into Reply.io and enrolled in two sequences. Verified addresses go to your main sequence. Catch-all addresses go to a second one, so a bad domain cannot drag down the first. Both sides are plain REST with a key.

Split the lists because the status decides the risk. A verified address has been checked against the mailbox. A catch-all domain accepts everything, so a catch-all address may still bounce. LeadOcean marks it in email_status.

Related: the LeadOcean integrations hub, the Smartlead recipe, the Salesloft recipe, the Outreach recipe and pricing.

How it works

Six steps. Reply.io's import endpoint takes up to 1,000 items per request and enrolls the contacts in a sequence you name (source: Reply import guide, September 2026).

1. Get both keys. Sign up at app.leadocean.io and copy a key from the API keys page. In Reply.io open Settings, then API Key, and create a key with the contacts:write scope.
2. Size the list. Run a free count before you spend records. A search with count=true and limit=1 costs nothing, and meta.total is capped at 100,000.
3. Export verified. POST your filters to /v1/exports with emailStatus set to verified.
4. Export catch-all. Repeat with catch_all_valid and catch_all. Same filters, a second file.
5. Create two sequences in Reply.io. One for verified, one for catch-all. Note both sequence ids.
6. Import each CSV. Send 1,000 rows at a time to POST /v3/contacts/import with the matching sequenceId.

Run a small test first. Free has no bulk CSV export, so on Free search with POST /v1/people/search, then call POST /v1/people/enrich with reveal_email set to true for each person to get the address. Each person returned costs one record. Check one contact in Reply.io before you send the rest.

Prefer to click? The LeadOcean app has an Exports page with a filter builder, a column picker, the record price before you start and a Download button. Reply.io's docs say CSV import is available in the product, and the API guide says the API itself takes JSON, not CSV (source: Reply import guide, September 2026).

Configuration

Steps 3 and 4, the exports. Several values in one filter join with OR.

curl -X POST https://api.leadocean.io/v1/exports \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"reply verified","filters":{"jobLevel":["VP"],"jobFunction":["Sales & Business Development"],"country":["CA"],"emailStatus":["verified"],"emailType":["work"]},"limit":10000,"columns":["profile_first_name","profile_last_name","current_job_title","current_company_name","current_company_domain","email_N_address","email_N_status"]}'

curl -H "x-api-key: $LEADOCEAN_API_KEY" https://api.leadocean.io/v1/exports/EXPORT_ID
curl -H "x-api-key: $LEADOCEAN_API_KEY" -o verified.csv https://api.leadocean.io/v1/exports/EXPORT_ID/download

For the second file, change emailStatus to ["catch_all_valid","catch_all"] and download to catchall.csv. Contact columns need a key with the enrich scope.

Step 6, the import. Reply.io uses a bearer token on api.reply.io. Every item needs firstName, or it comes back failed with the error "Invalid data" while the HTTP status stays 200 (source: Reply import endpoint, September 2026).

import csv, os, sys, time, requests

URL = "https://api.reply.io/v3/contacts/import"
HEAD = {"Authorization": f"Bearer {os.environ['REPLY_API_KEY']}"}
path, sequence_id = sys.argv[1], int(sys.argv[2])

items = [{
    "email": r["email_1_address"],
    "firstName": r["profile_first_name"],
    "lastName": r["profile_last_name"],
    "company": r["current_company_name"],
    "title": r["current_job_title"],
    "customFields": [{"name": "email_status", "value": r["email_1_status"]}],
} for r in csv.DictReader(open(path))
  if r["email_1_address"] and r["profile_first_name"]]

for i in range(0, len(items), 1000):
    body = {"items": items[i:i+1000],
            "options": {"skipExisting": True, "sequenceId": sequence_id}}
    res = requests.post(URL, headers=HEAD, json=body)
    print(res.status_code, {k: v for k, v in res.json().items() if k != "items"})
    time.sleep(1)

Reply.io limits each user to 100 requests a minute, 3,000 an hour and 150,000 a week. Above that it answers 429 with a Retry-After header (source: Reply API introduction, September 2026). A 10,000-row file is 10 requests, so the limit does not bite here.

Run it twice: python push.py verified.csv VERIFIED_SEQUENCE_ID and python push.py catchall.csv CATCHALL_SEQUENCE_ID. The response reports added, updated, skipped and failed, plus a per-item outcome.

Field mapping

Map the status as well as the address. Reply.io does not know which contacts came from a catch-all domain, so write email_status into a custom field and you can report on it later. The import body takes email, firstName, lastName, phone, title, company, industry, city, state, country, linkedInUrl and customFields. A custom field is addressed by id or name (source: Reply API spec, September 2026).

Column ids come from GET /v1/exports/columns, which needs no key.

Cost at 10,000 rows

A 10,000-row run needs LeadOcean Solo at $97 a month, because bulk CSV export is not on Free. Reply.io's plan price is not quoted here; read it on reply.io/pricing for your plan.

Reply.io's billing schemas count active contacts, meaning contacts first touched in a billing month (source: Reply API, billing schemas, September 2026). Importing 10,000 contacts is not the same as activating 10,000. That reading is ours.

Troubleshooting

FAQ