FullContact

What do you like best?

The API is very easy to integrate, is well documented and very stable. Asynchronous processing via webhooks increases the matching ratio, especially useful when the use case allows waiting some minutes for the response.

What do you dislike?

We see a 50% matching rate, there is room for improvements there. We miss the batch endpoint we had in the v2. Some data from the Enrich API have too many fake positives, especially age, employment, and education. We miss a well-documented list of available profiles networks. Outdated data is expected in this kind of APIs but a timestamp about when each data point was updated is desirable to manage when to discard them.

A rate limit of 600 queries per min is very low if you are batch processing profiles.

Recommendations to others considering the product:

Integrate with webhooks, it will increase the matching rate opportunities. Email hashing as MD5 and SHA-256 are available, use it if your use case enforces you to protect the identity of the profiles to match, but take into account that hashing the emails will reduce the matching ration considerably. A rate limit of 600 queries per min could be very low if you are batch processing profiles if that is your case to ensure to handle the rate limits properly by taking into account the X-Rate-Limit, X-Rate-Limit-Remaining, X-Rate-Limit-Reset response headers.

What problems are you solving with the product? What benefits have you realized?

We have been using FullContact APIs since 2014, first the Person API, now the Enrich API to enrich Twitter profiles and to match emails.