FanFeedr Developer Blog

RSS Feed

Change in the response format for videos

Folks,

Effective 22 December 2011, we are going to change the response format for videos so that they return the same information that is delivered via standard stories. Please let us know if this presents any challenges for you.

Thanks, Ty

API Update: v1 Deprecation, New Documentation, Added Functionality

We pushed a few API-related updates today that we would like to telll you about. 

Deprecation

Support for API v1 has been turned off. If anyone needs assistance migrating to the current version of our API, please post to our forums here.

Documentation

We have adopted Mashery's new I/O Docs format for our documentation.

We're really excited about this implementation as it allows developers to execute live calls directly from any of the methods listed in our documentation.

API Updates

We have pushed the following updates:

(1) Events/:id/lineup method

This method returns a complete lineup, when available, for a given event id member. 

Note: This call is currently only available for MLB. We will be adding support for other leagues soon. For MLB, probably pitchers are included in the returns.

Format:

[{"player": "player_id",

"confirmed": false,

"team": "team_id",

"position": "SP",

"batting_order": null},

...]

(2) Improved MLB boxscores

The returns have been enhanced to include extended batting, pitching, and fielding data.

(3) Augmented Team/:id returns

These returns now include additional information such as "mascot" and "team colors". Nicknames for all teams have also been supplemented.

Feedback

Please let us know what you think of our new documentation and API features.

Cheers,

Benn

On behalf of the FanFeedr API team

New API Release

We're excited to announce the release of the next version of our API!

Key Features

We wrote about some of the planned changes in our last blog post, but here are the highlights:

  • This version of our API is completely RESTful
  • Available resources represent a collection of members, each now associated with an UUID
  • Sports resources are divided into an inheritance structure -  to obtain information about a specific resource, users must query the ‘parent’ resources
  • The only supported format for this API is JSON

BETA Version

We've labeled this version as BETA because we plan to make changes over the next few weeks based on internal evaluations and user feedback. 

Information contained in API v1 has been migrated to this version and is fully accessible.

Plans and Rate Limits

Based on our analysis of API usage and developer feedback, we have made a few changes to our plans. 

For our Basic free plan, we have reduced the number of calls allocated to 25 per hour. We're confident that this rate limit will meet user needs, based on current and expected use cases.

Developers needing higher rate limits may sign up for a new Bronze plan. This plan has a daily rate limit of 2400 calls and is economically priced at $25 per month. 

We will continue to study our rate limits and plans and make any adjustments as needed to sufficiently serve our ecosystem.

Deprecation

With this API release, we will now have 3 live versions of our API. All future development will focus on the new version of the API.

In order to best allocate our resources, we have decided to full deprecate our APIs v0 and v1. Access to these APIs will be turned off on August 1, 2011.

We will provide support through forums and IRC to help users migrate to the new API.

Portal Upgrades

We have completely rewritten our documentation but plan to take over management of our developer portal in the next few weeks from our hosted provider.

Some items we will be rolling out as part of an integrated set of tools:

  • A new design
  • API test console
  • Status monitoring tool
  • Issues tracker
  • Interactive Q&A forums

The FanFeedr API Team

Special thanks to our engineering team of Jonathan Stasiak, Andy Adams, and Chris Sabanty for their contributions to this release.

API Roadmap

We already have some features planned for future release relating to authentication methods, adding content and data for additional sports, and providing new supported formats.  Please let us know your thoughts on our new API by posting to our forum or contacting us via Twitter. We appreciate the feedback that we’ve received from our ecosystem and look forward to supporting your projects. 

If you have any questions or comments about this release or any other matter, please contact me directly at benn@fanfeedr.com. Thank you for being part of the FanFeedr community, and we look forward to continued collaboration.

Cheers,

Benn, on behalf of the FanFeedr API Team


Roadmap Update

We're excited to report that Team FanFeedr has been busy working on a new version of our API!

So that you can plan accordingly, what follows is a brief preview of what you should expect to see within the next 2 weeks.

A completely RESTful API

Our new API will have the same functionality as the current API, but the routes will change. Programmatically, entity resources will be replaced with UUIDs, as described below.

Methods to retrieve data from the FanFeedr API will require a GET request. The API will support JSON only.

The end result will be clearer organization, more intuitive paths, and reduced datasets.

Available Resources

Each available resource will represent a collection that contains members. Each member will be associated with an UUID, that can be queried to obtain its properties.

Sports resources will be divided into an inheritance structure of:

  • leagues
  • divisions
  • conferences
  • teams
  • persons

In order to obtain information about a specific resource, users must query the ‘parent’ resources.

For example, to get a list of all teams for the NFL, you will need to call /leagues for the relevant nfl_id. A call for /leagues/{nfl_id}/teams returns the team UUIDs. Calls for each team_id return detailed member information such as name, location id, etc.

Other resources include:

  • geo
  • events
  • content
  • images (requires subscription to a paid plan)
  • sources
  • trending

Parent resources are used to pare down what data is returned by these collections.

For example, to get a list of events currently happening for the NBA, you will need to call /leagues/{nba_id}/events/live for event UUIDs. Calls for specific event_id return detailed member information such as home team, away team, location id, scores, etc.

Portal Upgrades

We are taking over management of our developer portal, and no longer will be relying on solutions from our gateway provider. Our goal with the new format will be to foster a sense of community, where developers can easily interact with our API team and help one another with issues encountered.

We will be integrating an interactive Q&A system, API console for testing of various resources, status monitoring tool, and seamless payment solutions.

The documentation will be clear and concise, with examples of calls and responses.

Final Thoughts

If you have any questions or comments on this or any other matter, please contact me directly at benn@fanfeedr.com.

Thank you for being part of the FanFeedr community, and we look forward to continued collaboration.

 

Cheers,

Benn, on behalf of the FanFeedr API Team

Announcing FanFeedr API v1

Today we are excited to announce the release of the next version of the FanFeedr API.

Highlights of this release:

  • Performance Improvements
  • Related Entities
  • Live Scores
  • Standings
  • Game Details
  • Hot Info
  • Local Data
  • Updated Documentation

Getting Started

API v1 documentation has been uploaded to the developer portal. The URL structure for the v1 release will require changing API calls to include v1/ prior to the query string, e.g. http://api.fanfeedr.com/basic/v1/resource_feed/mlb/ny-yankees/?appid={AppID}

We will continue to support the original version of our API, but will not be adding additional features to that version. Therefore, we encourage you to migrate over to the new version of our API.

Performance Improvements

  • Standardized call formatting and responses
  • Additional output formats, including HTML and RSS
  • Improved performance of API calls via fine tuning of application code
  • Appended additional information to the datasets returned with the resource_feed. The resource_feed now shows you what entities are tagged in an article. Users can specify a particular resource and parse out the results in a more fine grained manner according to what’s in the article.

Related Entities

This call returns related entities mapping as follows:

League -> conferences, divisions, teams

Conference -> divisions, teams

Division -> teams

Teams -> players

Live Scores

By popular demand, in game scores. Supports multiple resources.

Standings

Returns standings for leagues, conferences, divisions, or teams.

Game Details

game_details – extended information for a particular game including live progress, events, and FeedItems about the game.

games_on_date – for any given date, get a list of all games.

latest_game – the latest game for a team, league, list of teams, or list of leagues.

Hot_

hot_topics – returns a list of the hottest teams and players over the past hour, each with the hottest article related to that team or player.

hot_blogs – returns a list of the hottest blogs over the past hour, each with the hottest article published by that blog.

Local_

local_teams – provides a list of professional and college teams within a radius around a given latitude/longitude.

local_news – shortcut to the resource feed for all teams returned by local_teams call.

local_ scoreboard – shortcut for getting the latest events for all teams returned by local_teams call.

Updated Documentation

In response to comments from developers, we have updated and reorganized our documentation. We will be adding call results examples shortly. We plan to add client libraries in the next couple of weeks.

We welcome any additional comments you have regarding the documentation currently listed on the developer portal.

The FanFeedr API Team

Special thanks to our engineers Doug Tabuchi, Andy Adams, and Chris Sabanty for their contributions to this release.

API Roadmap

We are already planning for our next release and evaluating potential new features. If you have an idea for a new feature, please submit a post in the forums under Feature Requests. We will keep you updated on development news through our Announcements forum thread, blog posts, email, andTwitter.

We appreciate the feedback that we’ve received from our developer ecosystem and look forward to supporting your projects. Fostering a rich development community is a key priority for our company, and we have several initiatives planned over the next few months to strengthen our relationship. Over 325 developers have registered API keys, and we will strive to provide you with the most robust set of tools and resources for your projects.

If you have any questions or comments about the API v1 release or any other matter, please contact me directly at benn@fanfeedr.com. Again, thank you for being part of the FanFeedr community, and we look forward to continued collaboration.

Happy coding,

Benn, on behalf of the FanFeedr API Team


[ Page 1 of 1 ]