Comments on: Person API v3

By: Robin Dindayal

Robin Dindayal — Mon, 29 Nov 2010 21:25:55 +0000

Hi There,
Are the above examples still supported? I don’t see them listed in your documentation any more.

Please advise,
Robin

By: Axel Schultze

Axel Schultze — Sat, 15 May 2010 17:56:31 +0000

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

By: Chris

Chris — Fri, 19 Mar 2010 03:00:38 +0000

@Pete – great feedback. The API docs have been update to make it clear if the website takes a username or userid.

By: Pete

Pete — Wed, 10 Mar 2010 22:23:35 +0000

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.

By: Chris

Chris — Tue, 26 Jan 2010 23:00:00 +0000

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

By: Dan

Dan — Mon, 25 Jan 2010 00:14:36 +0000

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