Infochimps API Documentation

Quickstart Tutorial

The fastest way to get started with the API is with the Quickstart Tutorial

Data Set APIs

• Twitter
  • Trstrank – a robust reputation metric for Twitter users (includes friend and follower counts)
  • Wordbag – a user’s 100 most characteristic words
  • Influence – powerful analytics for determining qualities of a Twitter user
  • Conversation – interactions (replies, retweets, mentions) between two specific Twitter users
  • Strong Links – a list of the people a user interacts with the most
  • Word Usage – usage frequencies and dispersions for given words
  • Screen name, search ID & REST API ID Conversion – convert between Twitter screen names, REST API IDs and search IDs
• Digital Element
  • Demographics – Find out the demographics of users with given IPs
  • Domains – Find out which domains are served from which IPs
  • Geographic Locations – Find out all about the geolocale of an IP
• Census
  • IP Census – MaxMind GeoLite IP Census Data
  • Geo Census – Lat/Long and Zip Census Data
• Finance
  • Stocks – Daily open/high/low/close/volume for stock symbols from 1970
• Geo
  • Zip Codes – Zip Code Information

Introduction

Welcome to the Infochimps API! Here’s some basic information to get you going:

• You need to sign up for an API key in order to access the API.
• All API requests must include an API key, otherwise your request will return with an Unauthorized (401) error.
• The basic structure of a request looks like this:
  http://api.infochimps.com/[path_to_data_set_api]/[method].json?apikey=[your_api_key]&[parameter]=[parameter_value]
  For example, if you are making a request to get trstrank it may look like this: http://api.infochimps.com/soc/net/tw/trstrank.json?screen_name=infochimps&apikey=api_test-W1cipwpcdu9Cbd9pmm8D4Cjc469
• Best practice is to specify a version number (for example (note the ‘v’ attribute): http://api.infochimps.com/soc/net/tw/trstrank.json?screen_name=infochimps&apikey=api_test-W1cipwpcdu9Cbd9pmm8D4Cjc469&v=0.2) in your request. Requests that do not include a version will always point to the latest version of the API call. If the call gets updated, it might break your code. Also, older versions will not necessarily remain available indefinitely.
• Callbacks for JSONP and JavaScript

Examples

• Code Examples
• YQL calls for Infochimps. Example: Trstrank

Errors

• 404 – “Not Found” – Record may not be in our database, may be protected or may not exist.
• 403 – "Rate Limit Exceeded " – The apikey has exceeded its rate limits for the period (hour or month), wait and try again.
• 401 – “Unauthorized” – All requests require that you provide an API key.
• 400 – “Bad Request” – The request you made was malformed, or you did not specify some required parameters. Refer to the example in the call’s documentation.

Please contact us if you continue to receive errors.