Show HN: Contactive API – Turn telephone numbers into full profiles
developer.contactive.com
developer.contactive.com
Also what does "big data logic" mean?
As with everything, I'll assume nothing is free unless I'm the product.
What use case is your product addressing?
And I'm sorry, but 600 million unique data entries isn't "big data" that would fit into a single Excel 2013 worksheet if you used multiple columns (570 ish columns) but still 1 worksheet.
It is also important to know that we only index public data and also we provide an opt-out option if someone wants to be unlisted.
"Turning phone numbers into full profiles" is a primary objective of every telephone marketing/"lead-generation" campaign in the history of time, and automating part of it by aggregating publicly available data seems only natural.
I would guess this is aimed less at telemarketers calling people's homes, and more at telemarketers selling business services (especially B2B startups), where cold-calling is seen as more legitimate and is the way a lot of business gets done. You want to know, at the very least, that you're calling someone whose job title indicates that they have the authority to spend money.
Every time we get new data, we have to compare it with the existing set. This is done in realtime..
So, the fact we have 600+ million identities ready to be queried is the result of having a much bigger dataset were all the non-matched-yet data is stored.
Where's the opt-out, both for individuals with individual phone numbers, and for businesses who own large blocks of numbers?
You can always mail us to contact@contactive.com for any privacy concern. We would remove any phone number upon request.
How much out of 600M are Indian Contacts?
Can we have countries vise count of Data you own?
As a matter of fact, our API powers our core services like our Contactive Caller ID app which has more than 1 million downloads in the Google Play Store with a consistent 4-5 star rating.
Additionally, if we identify a call, but the resolution has low confidence, the user will be prompted to vote it up or down. This feeds directly into our identity graph, recalculating in realtime the connections between identities and contact information.
We also use the client app to enhance the existing connections in our identity graph. Each edge in our graph has a confidence level, and by using the data available to the app we adjust and recalculate the confidence levels of our directory in real-time. We never publish data points like photos, notes, etc. from the address book of our users.
- All Contactive API accesses are real time. If we have the data, we will return it right away, if we don't, we will try to find it as soon as we can and return it on the same API request. Full Contact uses the callback pattern, where they notify when they are able or not to resolve the information on a separate call (if they dont have it at the moment of query).
- Contactive not only gives you social network identities, it also gives you aggregated and prioritized data, like the job history of someone, or the list of pictures. This data is returned in the best possible way to be displayed. This saves time from developers because they do not have to make any effort prioritizing each field of the many sources we return.
- Contactive also gives you HTML rendering of a contact, allowing you as a developer to embed it on a iframe. This allows you to integrate it in a web app in a matter of minutes.
I'm one of the lead engineers for the FullContact Person API and there's a few inaccuracies with your feature comparison that I'd like to address.
1) True, we can optionally do callbacks. However we'll return the data immediately if we've seen it recently. This is most cases. If callbacks don't work for you, data is usually populated within 10 seconds and can be polled for.
2) We also prioritize data. All of our fields that make sense are sorted and have flags to denote preferred elements.
3) We also have an HTML endpoint, however it's a terrible idea to embed into an iframe as you'll leak your API key. For this reason we recommend that our customers proxy calls through their own server-side endpoint to ensure their API key does not leak. That being said, we do provide the HTML endpoint, mainly for internal usecases where users can be trusted or cases where users bring their own keys.
I was creeped out for a second, but then proceeded to order more pizza.
Everything is stored in a graph and to make the connections between phone, emails and identities we've created algorithms to compare contact information. For this we use signals like name similarity, location, friends in common and many others.
All of this is indexed in realtime and when you do a query to our API you get the most up-to-date data.
I look forward to checking out the Contactive API, and perhaps even having a discussion with them to see if there is an opportunity for us to work together.
In the meantime, since our product was mentioned here, I'd be happy to field any questions.