Database Reference
In-Depth Information
People by Account
Klout's API will give you an inluence score for a given Twitter username. You can then use this
information to help prioritize Twitter accounts within your own service (for example, by high-
lighting links shared by people with higher reputation or spam iltering those with low scores):
http://api.klout.com/1/klout.xml?key=[your_api_key]&users=[usernames]
This service allows you to link Twitter usernames with accounts on other sites. Unfortunately,
the data is still pretty sparse, and the Facebook account lookup doesn't return any useful inform-
ation, but it's still worth a look:
curl "http://api.qwerly.com/v1/twitter/petewarden.json?api_key=<key>"
{ "location":"Boulder, CO",
"name":"Pete Warden",
"twitter_username":"petewarden",
"qwerly_username":null,
"services":[
{"type":"github","url":"http://github.com/petewarden","username":"petewarden"},
{"type":"twitter","url":"http://twitter.com/petewarden","username":"petewarden"},
{"type":"klout","url":"http://klout.com/petewarden","username":"petewarden"}
]}
Search Terms
Sometimes you're trying to match a word or phrase with some web pages within your service,
either for traditional user-driven search or as part of a backend analysis process. The biggest
downside of most of the APIs is usually their restrictive terms of service, especially if you're do-
ing further processing with the results instead of showing them directly to users, so make sure
you read the ine print. You can ind PHP example code for Bing, BOSS, and Google
on my
blog
.
One of the earliest search APIs, BOSS is under threat from Yahoo!'s need to cut costs. It's still a
great, simple service for retrieving search results, though, with extremely generous usage limits.
Its
terms of service
prohibit anything but user-driven search usage, and you'll need to
sign up
to
