- 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.
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.