41–50 of 51 posts
This looks like a ripoff of EveryoneAPI.com
We solve a similar problem but our approaches are different. For example, we don't charge for every bit of information and we integrate with social networks to provide a more complete version of the profile, including job position and education.
This looks like a ripoff of EveryoneAPI.com
We solve a similar problem but our approaches are different. For example, we don't charge for every bit of information and we integrate with social networks to provide a more complete version of the profile, including job position and education.
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.
Seems like Full Contact? http://www.fullcontact.com/
These are some difference with Full Contact: - 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). - Contact…
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.
This + twilio = user identification. Looks like I'm gonna have to be more careful with my phone number...
We know there may be some privacy concerns regarding the use of our data but we don't allow anyone to systematically query our API to build phone number lists (We just allow 180 requests per min) We are very strict in the way people use our API. That's the reason we don't have an open registration process.
This + twilio = user identification. Looks like I'm gonna have to be more careful with my phone number...
We know there may be some privacy concerns regarding the use of our data but we don't allow anyone to systematically query our API to build phone number lists (We just allow 180 requests per min) We are very strict in the way people use our API. That's the reason we don't have an open registration process.
Earlier quoted context omitted.
This is already a business reality for most savvy organizations. Example, ordered pizza on saturday. Sunday, call another branch of the same pizza shop and the person answering the phone greets me by name before I even have a chance to say hello... I was creeped out for a second, but then proceeded to order more pizza.
There's nothing weird going on there.. They took down your name when you called and they simply log you in their system with the phone # you called in with, your name, and likely your address if you got it delivered.
Earlier quoted context omitted.
There's nothing weird going on there.. They took down your name when you called and they simply log you in their system with the phone # you called in with, your name, and likely your address if you got it delivered.
Information sharing is only recently the norm. Even between different branches of the same pizza chain.
Earlier quoted context omitted.
Well. We have a much more bigger phone number database and provide very compelling profiles associated to each phone number. Full Contact doesn't focus on phone numbers. We do. 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.
Direct question: are you using the app to collect info about the users to you can enhance your database also based on that data?
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.
Earlier quoted context omitted.
Direct question: are you using the app to collect info about the users to you can enhance your database also based on that data?
We use the app for machine learning purposes. When you get a call that cannot be identified, we ask the user to input the name of the caller. 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…