Sports, distributed: the FanFeedr API

Posted: December 12th, 2009 | Author: Ty | Filed under: API, Aggregation, Distribution, Release | View Comments

machines talking to machines Pictures, Images and Photos

We relaunched our API tonight, and it has several sizes that should fit your sporting needs.

What would I do with the FanFeedr API?

Essentially, you can build a robust sports application with headlines, info and tweets from the best sources in sports.

What sports can I access using the API?

  • NFL
  • MLB
  • NBA
  • NHL
  • Soccer (or Football, if you prefer)
  • NCAA football
  • NCAA basketball
  • NCAA women’s basketball
  • Tennis
  • Golf

We have four tiers . . .

Free

  • 100 queries/hour for any sport, league, athlete, team or college
  • URLs are FanFeedr URLs
  • Free

Free Daily

  • 1,500/day for any sport, league, athlete, team or college
  • URLs are FanFeedr URLs
  • Free

Gold

  • 250 QPH
  • URLs are from the underlying provider
  • Email support for help desk issues
  • Increased caching abilities.
  • $250/month

Enterprise

  • 2,500 QPH
  • URLs are from the underlying provider
  • Phone and email support for help desk issues
  • Increased caching abilities.
  • $1,200/month

API users can ingest JSON or XML, whichever is easiest, and we are adding new responses as they are requested. Additionally, we offer round-the-clock support on the paid services, as well as a professional services engineer who can assist you and your team with implementation.

We are adding a fifth tier, where we pay you to use the API, in January. Let us know if you would like to be notified when that becomes available. If you are site that gets between 50,000 to 1MM uniques a month, and you would like to make small to major incremental scratch, ping us at info at fanfeedr dot com.

Where can I learn more?

  • The API is here.
  • The documentation is here.
  • The IRC channel is here.

Let us know what you think and/or need.

FanFeedr!



Leave a Reply

  • Powered by WP Hashcash

blog comments powered by Disqus