This is a node module created to wrap the Yahoo! Fantasy Sports API (link). At the moment, not all subresources are available, nor are any of the 'collection' elements. I do hope to add them, and they have been added to the code, but as of now this project is very much in an open beta phase.
The API is designed to act as a helper for those interacting with the Y! Fantasy API. The goal is for ease of use for the user, both in terms of querying endpoints and parsing responses. I've noticed that in working with the API, the data is not always the easiest to understand, so hopefully what I have created here will help people out.
You can install the module via npm by running:
$ npm install yahoo-fantasy
I've created a customized version of the Passport Strategy for Yahoo! OAuth to help me when I developed this module. It's a fork of the strategy on the PassportJS homepage, which simply fixed a couple of issues. It would appear that the original creator is no longer supporting the strategy, and I may have missed some things, but it has worked as much as I've needed it. Please let me know if you have any questions about it.
I recommend using the Passport Strategy for OAuth2 with the updates I've made to this project over the... years now... wow...
This module is available under the MIT Licence
More complete documentation can be found using the application sandbox. This sandbox is also a work in progress, but it is my hope going forward to complete it.
The API can be used by simply importing the module and querying data
var YahooFantasy = require('yahoo-fantasy');
// you can get an application key/secret by creating a new application on Yahoo!
var yf = new YahooFantasy(
Y!APPLICATION_KEY,
Y!APPLICATION_SECRET
);
// if a user has logged in (not required for all endpoints)
yf.setUserToken(
Y!CLIENT_TOKEN,
Y!CLIENT_SECRET
);
// query a resource/subresource
yf.{resource}.{subresource} (
{possible argument(s)},
function cb(err, data) {
// handle error
// callback function
// do your thing
}
);
yf.{resource}.{subresource} (
{possible argument(s)}
)
.then(data => // do your thing)
.catch(err => // handle error)
try {
let data = await yf.{resource}.{subresource} (
{possible argument(s)}
)
// do your thing
} catch(err) {
// handle error
}
This project is very much still a work in progress, please report any issues via the GitHub issues page.
- Resolve error when no team logo is present (Issue #42)
- Introduced
promisebased flow for all endpoints as an alternative to callbacks. Thanks Marois!
- Fixed a bug in the players.league collection call where it was trying to use split on an array... (Issue #46).
- Fixed similar bugs in other places...
- Added the ability to specify a date or week when querying the
team.statsresource. - Unit test fixes (Issue #42). Thanks Marios!
- Updated "vulnerable" dependencies.
- Fixed an issue with the
user.game_leaguesresource, where the data was not at all user friendly (renamedleaguestogamesat the top level of the return object)
- Fixed some typos in some import statements which caused issues on some servers
- Major refactor to use ES6?... 2015? ...2018? Whatever the hell they're calling it now...
- Using ES Modules (mjs) files where possible
- Removed transactions collections (they'll be back!)
- Added a fix to give a cleaner value for the new "batting order" attribute in the player oject.
- Fixed a bug where the league players collection was not properly parsing the ownership subresource
- Fixed a bug where "mapTeamPoints" helper function was not defining "self". Thanks platky!
- Removed the code that added a "reason" to errors coming from Yahoo! as it was breaking other errors. Retry notifications should now be handled within the application using the module.
- Moved to Yahoo!'s OAuth2.0 authentication mechanism.
- Fixed game resource roster postions callback bug.
- Fixed a typo that was breaking team mapping.
- Breaking changes
- Fixed NFL scoreboard/matchups bug (Issue #19)
- In fixing this bug I realized that my "team" set up was really only useful for MLB fantasy, so I rewrote team mapping to work better across all sports and give additional details that weren't previously reported. This will cause errors if you are using the team.manager attribute in your code.
- Fixed a bug where leagueFetch was throwing an error, thanks danielspector!
- Fixed a bug where player stats by week url was not being created properly, thanks withsmilo!
- Fixed a bug where collections that contained subresources would return no data.
- Added "Transactions" collection with functionality to add players, drop players, and add/drop players, thanks again githubsmilo!
- Fixed a bug in player.draft_analysis, thanks githubsmilo!
- Added weeks param for league.scoreboard
- Added weeks param for team.matchups
- Fixed a bug where individual players weren't mapping properly
- Minor code cleanup
- Added the ability to specify a date or week when querying the roster resource.
- Cleaned up the player normalization model
- Fixed a bug where the team.roster call was erroring
- Fixes to how POST data is handled
- Significantly restructured the code to have more consistency and set it up better for future plans, namely POST methods and proper unit testing
- Removed the "refresh user token" and instead return the error to the user who can handle the refresh within their application.
- Additional player attributes added, thanks ryus08!
- Added a method to refresh the user's token if it has expired.
- Hotfix to fix "Teams" collection - use error first convention
- Made helper classes more consistent
- Added collections for games, leagues, players, and teams
- Moved to error first convention because JavaScript
- Added 'Team Matchups' subresource
- Added 'League Scoreboard' subresource
- Minor code cleanup and improvements
- Refactored module to fix a bug where user sessions were not necessarily unique because of require caching.
- Initial release.