Why do the Lookup Endpoints return incorrect results sometimes?

This post applies to the following API endpoints:

Occasionally, our Lookup API endpoints return the wrong results. False positives, to be precise. This happens because our Lookup Endpoints is a search function. Even Google gets search results wrong.

There are two reasons why this happens:

If you look up a person and the target person does not have a public Professional Social Network profile, our Lookup API will return the next closest match.
Our search is not good enough.

We are constantly working on improving #2. However, for #1, there is just nothing much we can do because the profile is not available to us to return.

Featured Articles

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

View all

profile api

Ultimate Guide To The Professional Social Network API: People Profile API (with Python Examples)

Learn all about the Professional Social Network API, with comprehensive Python code demos. Dive into the world of Professional Social Network APIs, official and third-party alternatives, and understand how to access and utilize Professional Social Network profile data through Python code examples.

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