We just updated our person API to allow queries by social network profile ID. The new style URLs are also more natural to write. If you want to query by email:
http://api.rapleaf.com/v3/person/email/dummy@rapleaf.com
If you want to query by the SHA1 hash of an email:
http://api.rapleaf.com/v3/person/hash/sha1/1147e414eec8b785fb760f13f7890a767ffaef6e
If you want to query by Myspace profile ID:
http://api.rapleaf.com/v3/person/web/myspace/1234567
If you want to query by Twitter user:
http://api.rapleaf.com/v3/person/web/twitter/janedoe
An API key is also required. You can check out the rest of the documentation here.
5 Comments
This doesn’t seem to work with Facebook profile ids. I have tried several different ids and each time a 400 error is displayed saying: “We do not have this user ID in our system, and cannot currently enqueue user IDs of this type to be searched.”
@Dan – thanks for the comment. We did have a bug that only affected facebook, which is now fixed. However, you will still receive a 400 if you enter a facebook ID that you have not crawled yet (even if it’s a valid facebook ID). Once we crawl that profile, it will show up in the API.
the documentation doesn’t really indicate which sites require the numeric id and which use the alphanumeric (remainder of the url). For example you display using the alpha id for twitter and numeric for myspace. I tried linkedin which the public profile uses alpha but that doesn’t seem to work with the api. can you elaborate on which ones require which data? The data I tried I know you already crawled, so I assume the linkedin call requires a numeric id.
@Pete – great feedback. The API docs have been update to make it clear if the website takes a username or userid.
Great job guys. Your API cuts through it like a hot knife through butter. We saw your service yesterday and implemented it literally over night! It’s up and running helping people in Xeesm to augment their customer data.
Axel
http://xeesm.com/AxelS