Introducing Work Email Data (+ other QOL improvements) Learn more

Introducing Work Email Data (+ other QOL improvements)
Introducing Work Email Endpoint
ninjapear

Introducing Work Email Data (+ other QOL improvements)

I am happy to introduce to you today a new NinjaPear API Endpoint—the Work Email Endpoint. The Work Email Endpoint takes in a person's name and the company where they work, for which a work email is returned on a best-effort basis.

This API Endpoint takes special care not to read from private or proprietary datasets, and only from public sources, while doing its best to return a valid work email address. We do so as not to violate privacy laws or breach the Terms of Use or User Agreement of any sites.

That said, let me put it out there first: there are better contact enrichment services out there. But read on to find out the narrow use cases for which you should use NinjaPear's.

How well does it work?

To give you a transparent look at what to expect, we ran a fulfillment test across 20 diverse profiles. Our goal wasn't just to see if the API returns data, but to see how it handles real-world scenarios, including obscure domains and legacy companies.

Performance Summary

  • Fulfillment Rate: 65% (13/20)
  • Reliability: 100% (All 20 calls returned HTTP 200; no technical errors)
  • Average Latency: ~9.3 seconds

Fulfillment Test Results (n=20)

# Name Domain Result Latency
1 Matt Aitken residencesontheavenue.com MISS 10.0 s
2 Christian Floisand helcim.com c********@helcim.com 10.6 s
3 Michael Komosinski amplify.com m**********@amplify.com 11.2 s
4 Pradeep Baliga paypal.com p******@paypal.com 8.7 s
5 Chuck Anthony silverbullet.ac MISS 8.6 s
6 Ryan Huber defined.net r***@defined.net 10.8 s
7 Pieter van der Does adyen.com p**********@adyen.com 8.6 s
8 Ravi Hubbly exploredigits.com r*******@exploredigits.com 8.8 s
9 Mihai Chiorean cash.app m********@cash.app 11.6 s
10 Dave Wiskus standard.com MISS 11.3 s
11 Robert Bollinger robertbollinger.com r*****@robertbollinger.com 9.0 s
12 Mark Frohnmayer badhabit.com MISS 7.8 s
13 Sergio Buniac boozallen.com MISS 8.9 s
14 Mo Hessabi metrostar.com m*******@metrostar.com 9.7 s
15 Steven Goh nubela.co s*****@nubela.co 0.3 s (Cache)
16 Tim Beard silverbullet.md MISS 12.2 s
17 Lucas Salisbury fastspring.com l*********@fastspring.com 9.0 s
18 Charles Cao ibm.com c**********@ibm.com 9.7 s
19 Ignacio Llorente sun.com MISS 9.5 s
20 David Nachman fastspring.com d*******@fastspring.com 9.5 s

There are other, better tools out there for contact enrichment

I'm going to be honest: Apollo or Clay will be infinitely better contact enrichment tools. NinjaPear isn't trying to be a contact enrichment product. We built the Work Email Endpoint simply because it is convenient for our users, and for those who want contact data strictly via public sources and not fished out from Chrome Extensions hooking into private Gmail accounts, like what Clearbit used to do.

In other words, use the Work Email Endpoint only if you do not already have access to better enrichment tools and you want 100% kosher contact data so that when a contact asks how you got their email, you can confidently say:

Hey, I found your email on the public web. You had either posted it somewhere in cleartext or your company has a known email pattern.

That said, honest to goodness: I built this because we are building out our AI agentic outbound sales / cold email pipeline and this was a missing piece. In fact, if you see our Competitors Listing Endpoint and Similar People Endpoint, you can see how we are gradually building out our own prospecting capabilities for our agentic pipelines ;)

How much does the Work Email Endpoint cost?

It costs 2 credits on a successful lookup—whenever we actually return something useful—and 0.5 credits if we return nothing. We charge a token amount to prevent denial-of-service attacks and also to cover our costs because we are performing live scraping and LLM calls on every API call. (See, we do not read from a contact database like the other guys).

Look up companies by name instead of website

A lot of customers have reached out asking if they can use a company name because they do not have the company website to perform various API calls. Well, as of today, yes you can!

For most API endpoints that take a company website, you can now provide a company name instead, whereby we will automagically look up the company's website. However, we still very much prefer that you use a website instead simply because it is more precise. There are many companies with the same or similar names globally, and NinjaPear works worldwide!

These are the API endpoints that now accept company names instead of a company website input:

What is on the horizon

We have recently started mapping every damn product and service of all businesses worldwide into a giant database that you can look up. In other words, I want you to know that product data is coming soon, amongst others. I will keep you posted. I'm excited about this.

Because just think about it: short of a Google search and doing it manually, how can you find a "CRM that has OAuth and Gmail integration, with PAYG options" instantly? There exists AI deep research which will send an agent to make a web search and trawl the sites, but it will still only perform a top N SERP result crawl and not go deeper. I'm excited about this!

On top of that, there is something we're doing on the B2C front that will be a multi-year endeavor. I'll keep you posted on this too.

Questions? Send us an email at [email protected]!

Steven Goh | CEO
World's laziest CEO. CEO of NinjaPear. Ex-Founder of Proxycurl (10+M), Steven founded 5 other startups: Gom VPN, Kloudsec, SilvrBullet, NuMoney, and SharedHere.

Featured Articles

Here's what we've been up to recently.

I dismissed someone, and it was not because of COVID19

The cadence of delivery. Last month, I dismissed the employment of a software developer who oversold himself during the interview phase. He turned out to be on the lowest rung of the software engineers in my company. Not being good enough is not a reason to be dismissed. But not

sharedhere

I got blocked from posting on Facebook

I tried sharing some news on Facebook today, and I got blocked from posting in other groups. I had figured that I needed a better growth engine instead of over-sharing on Facebook, so I spent the morning planning the new growth engine. Growth Hacking I term what I do in