Bulk & Prospecting
Most email work isn't one address at a time. When you have a whole list to verify or a batch of people to find, hand off the list and collect results as they land. And when you want to start from a company rather than a person, pull the contacts already known for its domain.
Working a whole list at once
Both verification and finding run at list scale. Submit up to a thousand items in a single request instead of firing a thousand calls, and Renidly works through them in the background at a controlled pace. It's the same pattern as batch enrichment elsewhere in Renidly:
| Step | What you do | What you get back |
|---|---|---|
| 1 · Submit | Hand off your list of addresses (to verify) or people (to find) in one request. | The list is accepted and queued; the call returns right away. |
| 2 · Track | Check back on the job. | Live progress — how many are resolved so far, and whether it’s still running or done. |
| 3 · Collect | Read results off the job as they become available. | Verdicts or discovered emails, streaming in as they land — you don’t wait for the whole list. |
Results stream, so you can start writing rows to your own store while the tail of the list is still resolving. A job and its results stay available for a few hours after you submit — long enough to collect everything without holding a connection open.
Prospecting from a company domain
Bulk verify and find both start from something you already have — an address, or a person. Prospecting starts from just a company domain and returns the contacts Renidly already holds for it, so you can build an account's contact list without knowing any names up front.
It comes in two modes, depending on whether you want breadth or certainty:
| Mode | What you get | Best for |
|---|---|---|
| All known contacts | Every email on file for the domain, without a deliverability check. | Casting a wide net; you verify the ones you’ll actually use. |
| Verified only | Only the addresses already confirmed deliverable. | A ready-to-send list with the risk already removed. |
Contacts come back a page at a time, so you can pull as many or as few as you need and stop when you have enough.
Where it earns its keep
- List cleaning at scale. Push an entire list through verification in one job and get a clean list back.
- Prospecting backfills. Find work emails for a large set of names and companies overnight, not one call at a time.
- Account contact building. Start from a target account's domain and pull the people already on file for it.
- Scheduled refreshes. Re-verify a mailing list on a cron so it stays deliverable between sends.
Bulk vs. single calls
| Reach for a single call when… | Reach for a bulk job when… |
|---|---|
| A user is waiting on the answer right now. | The work is a list, and nothing is blocked on any one row. |
| You have one address or person, or a few. | You have hundreds, thousands, or a whole file. |
| You need the result inline, synchronously. | You can hand off the list and collect results later. |