yahooapi

README

yahooapi

Documentation

Overview

Fantasy Sports API

Documentation from https://developer.yahoo.com/fantasysports/guide

Index

• type GameResource
• type LeagueCollection
• type LeagueResource
• type ManagerResource
• type MatchupResource
• type RosterAddsResource
• type ScoreBoardResource
• type TeamCollection
• type TeamLogoResource
• type TeamPointsResource
• type TeamProjectedPointsResource
• type TeamResource
• type TransactionCollection
• type UserCollection
• type UserResource
• type YahooConfig
  • func NewYahooConfig(clientID, clientSecret string, scopes []string, hostName string, ...) *YahooConfig
  • func (y *YahooConfig) AcceptTrade()
  • func (y *YahooConfig) AllowTrade()
  • func (a *YahooConfig) AuthYahoo(w http.ResponseWriter, r *http.Request)
  • func (a *YahooConfig) AuthYahooCallback(w http.ResponseWriter, r *http.Request)
  • func (y *YahooConfig) DeletePendingTrade()
  • func (y *YahooConfig) DeleteWaiver()
  • func (y *YahooConfig) DisallowTrade()
  • func (y *YahooConfig) EditWaivers()
  • func (y *YahooConfig) GetLeagueScoreboard(r *http.Request) *LeagueCollection
  • func (y *YahooConfig) GetLeagueStandings(r *http.Request) *LeagueCollection
  • func (y *YahooConfig) GetTransactionCollection() *TransactionCollection
  • func (y *YahooConfig) GetUserCollectionAll(r *http.Request) *UserCollection
  • func (y *YahooConfig) GetUserCollectionGames(r *http.Request) *UserCollection
  • func (y *YahooConfig) GetUserCollectionLeagues(r *http.Request) *UserCollection
  • func (y *YahooConfig) GetUserCollectionTeams(r *http.Request) *UserCollection
  • func (y *YahooConfig) LeagueScoreboardHandler(w http.ResponseWriter, r *http.Request)
  • func (y *YahooConfig) LeagueStandingsHandler(w http.ResponseWriter, r *http.Request)
  • func (a *YahooConfig) RegisterRoutes(r *mux.Router)
  • func (y *YahooConfig) RejectTrade()
  • func (y *YahooConfig) UserCollectionAllHandler(w http.ResponseWriter, r *http.Request)
  • func (y *YahooConfig) UserCollectionGamesHandler(w http.ResponseWriter, r *http.Request)
  • func (y *YahooConfig) UserCollectionLeaguesHandler(w http.ResponseWriter, r *http.Request)
  • func (y *YahooConfig) UserCollectionTeamsHandler(w http.ResponseWriter, r *http.Request)
  • func (y *YahooConfig) VoteDownTrade()

Types

type GameResource

type GameResource struct {
	XMLName  xml.Name         `xml:"game",json:"-"`
	Game_key string           `xml:"game_key",json:",omitempty"`
	Game_id  string           `xml:"game_id",json:",omitempty"`
	Namecode string           `xml:"namecode",json:",omitempty"`
	Type     string           `xml:"type",json:",omitempty"`
	Url      string           `xml:"url",json:",omitempty"`
	Season   string           `xml:"season",json:",omitempty"`
	Leagues  []LeagueResource `xml:"leagues>league",json:",omitempty"`
	Teams    []TeamResource   `xml:"teams>team",json:",omitempty"`
}

Game resource

Description With the Game API, you can obtain the fantasy game related information, like the fantasy game name, the Yahoo! game code, and season.

To refer to a Game resource, you’ll need to provide a game_key, which will either be a game_id or game_code. The game_id is a unique ID identifying a given fantasy game for a given season. For instance, the game_id for the Free NFL draft and trade fantasy game for the 2009 season is 222, while the game_id for the Plus version is 223. A game_code generally identifies a game, independent of season, and, when used as a game_key, will typically return the current season of that game. For instance, the game_code for the Free NFL game is nfl, and the game_code for the Plus game is pnfl; using nfl as your game_key during the 2010 season would be the same as providing the game_id for the 2010 season of the NFL game (242). As of the 2010 seasons, the Plus and Free games have been combined into a single code. Next year, the game_code nfl will point to the new game_id for the 2011 version of the NFL game. Thus, if you always want the current season of a game, the game_code should be used as a game_key.

Below is a list of game IDs for most of our seasons of each game. If you’re looking for a current game ID that’s not listed in the table below, as mentioned above, you can request game information by game_code. For example:

YQL: select * from fantasysports.games where game_key='nfl'; API: http://fantasysports.yahooapis.com/fantasy/v2/game/nfl Game IDs Table Season nfl game ID pnfl game ID mlb game ID pmlb game ID nba game ID nhl game ID 2001 57 58 12 – 16 15 2002 49 62 39 44 67 64 2003 79 78 74 73 95 94 2004 101 102 98 99 112 111 2005 124 125 113 114 131 130 2006 153 154 147 148 165 164 2007 175 176 171 172 187 186 2008 199 200 195 196 211 210 2009 222 223 215 216 234 233 2010 242 – 238 – 249 248 2011 257 – 253 – 265 263 2012 273 – 268 – 304 303

<?xml version="1.0" encoding="UTF-8"?>
 <fantasy_content xml:lang="en-US" yahoo:uri="http://fantasysports.yahooapis.com/fantasy/v2/game/nfl" xmlns:yahoo="http://www.yahooapis.com/v1/base.rng" time="30.575037002563ms" copyright="Data provided by Yahoo! and STATS, LLC" xmlns="http://fantasysports.yahooapis.com/fantasy/v2/base.rng">
   <game>
     <game_key>257</game_key>
     <game_id>257</game_id>
     <name>Football</name>
     <code>nfl</code>
     <type>full</type>
     <url>http://football.fantasysports.yahoo.com/f1</url>
     <season>2011</season>
   </game>
 </fantasy_content>

type LeagueCollection

type LeagueCollection struct {
	XMLName xml.Name         `xml:"fantasy_content",json:"-"`
	Leagues []LeagueResource `xml:"leagues>league",json:",omitempty"`
	Body    string
}

type LeagueResource

type LeagueResource struct {
	XMLName               xml.Name           `xml:"league",json:"-"`
	LeagueKey             string             `xml:"league_key",json:",omitempty"`
	LeagueID              string             `xml:"league_id",json:",omitempty"`
	Name                  string             `xml:"name",json:",omitempty"`
	URL                   string             `xml:"url",json:",omitempty"`
	Password              string             `xml:"password",json:",omitempty"`
	LeageChatID           string             `xml:"league_chat_id",json:",omitempty"`
	DraftStatus           string             `xml:"draft_status",json:",omitempty"`
	NumberOfTeams         string             `xml:"num_teams",json:",omitempty"`
	EditKey               string             `xml:"edit_key",json:",omitempty"`
	WeeklyDeadline        string             `xml:"weekly_deadline",json:",omitempty"`
	LeagueUpdateTimestamp string             `xml:"league_update_timestamp",json:",omitempty"`
	ScoringType           string             `xml:"scoring_type",json:",omitempty"`
	LeagueType            string             `xml:"league_type",json:",omitempty"`
	Renew                 string             `xml:"renew",json:",omitempty"`
	Renewed               string             `xml:"renewed",json:",omitempty"`
	ShortInvitationURL    string             `xml:"short_invitation_url",json:",omitempty"`
	IsProLeague           string             `xml:"is_pro_league",json:",omitempty"`
	CurrentWeek           string             `xml:"current_week",json:",omitempty"`
	StartWeek             string             `xml:"start_week",json:",omitempty"`
	StartDate             string             `xml:"start_date",json:",omitempty"`
	EndWeek               string             `xml:"end_week",json:",omitempty"`
	EndDate               string             `xml:"end_date",json:",omitempty"`
	GameCode              string             `xml:"game_code",json:",omitempty"`
	Season                string             `xml:"season",json:",omitempty"`
	ScoreBoard            ScoreBoardResource `xml:"scoreboard",json:",omitempty"`
}

League resource

Description When users join a Fantasy Football, Baseball, Basketball, or Hockey draft and trade game, they are organized into leagues with a limited number of friends or other Yahoo! users, with each user managing a Team. With the League API, you can obtain the league related information, like the league name, the number of teams, the draft status, et cetera. Leagues only exist in the context of a particular Game, although you can request a League Resource as the base of your URI by using the global ````. A particular user can only retrieve data for private leagues of which they are a member, or for public leagues.

type ManagerResource

type ManagerResource struct {
	XMLName        xml.Name `xml:"manager",json:"-"`
	ManagerID      string   `xml:"manager_id",json:",omitempty"`
	Nickname       string   `xml:"nickname",json:",omitempty"`
	GUID           string   `xml:"guid",json:",omitempty"`
	IsCommissioner string   `xml:"is_commissioner",json:",omitempty"`
	IsCurrentLogin string   `xml:"is_current_login",json:",omitempty"`
	Email          string   `xml:"email",json:",omitempty"`
	ImageURL       string   `xml:"image_url",json:",omitempty"`
}

type MatchupResource

type MatchupResource struct {
	XMLName       xml.Name             `xml:"matchup",json:"-"`
	Week          string               `xml:"week",json:",omitempty"`
	Status        string               `xml:"status",json:",omitempty"`
	IsTied        string               `xml:"is_tied",json:",omitempty"`
	WinnerTeamKey string               `xml:"winner_team_key",json:",omitempty"`
	Teams         []TeamPointsResource `xml:"teams>team",json:",omitempty"`
}

type RosterAddsResource

type RosterAddsResource struct {
	XMLName       xml.Name `xml:"roster_adds",json:"-"`
	CoverageType  string   `xml:"coverage_type",json:",omitempty"`
	CoverageValue string   `xml:"coverage_value",json:",omitempty"`
	Value         string   `xml:"value",json:",omitempty"`
}

type ScoreBoardResource

type ScoreBoardResource struct {
	XMLName  xml.Name          `xml:"scoreboard",json:"-"`
	Week     string            `xml:"week",json:",omitempty"`
	Matchups []MatchupResource `xml:"matchups>matchup",json:",omitempty"`
}

type TeamCollection

type TeamCollection struct {
	XMLName xml.Name `xml:"fantasy_content",json:"-"`
	// contains filtered or unexported fields
}

type TeamLogoResource

type TeamLogoResource struct {
	XMLName xml.Name `xml:"team_logo",json:"-"`
	Size    string   `xml:"size",json:",omitempty"`
	URL     string   `xml:"url",json:",omitempty"`
}

Team resource

Description The Team APIs allow you to retrieve information about a team within our fantasy games. The team is the basic unit for keeping track of a roster of players, and can be managed by either one or two managers (the second manager being called a co-manager). With the Team APIs, you can obtain team-related information, like the team name, managers, logos, stats and points, and rosters for particular weeks. Teams only exist in the context of a particular League, although you can request a Team Resource as the base of your URI by using the global ````. A particular user can only retrieve data about a team if that team is part of a private league of which the user is a member, or if it’s in a public league.

<teams count="1">
	<team>
		<team_key>348.l.900006.t.1</team_key>
		<team_id>1</team_id>
		<name>Steve's Team</name>
		<is_owned_by_current_login>1</is_owned_by_current_login>
		<url>
		http://football.fantasysports.yahoo.com/f1/900006/1
		</url>
		<team_logos>
		<team_logo>
		<size>large</size>
		<url>
		  https://s.yimg.com/dh/ap/fantasy/nfl/img/icon_01_100.png
		</url>
		</team_logo>
		</team_logos>
		<waiver_priority>10</waiver_priority>
		<number_of_moves>1</number_of_moves>
		<number_of_trades>0</number_of_trades>
		<roster_adds>
		<coverage_type>week</coverage_type>
		<coverage_value>1</coverage_value>
		<value>0</value>
		</roster_adds>
		<league_scoring_type>head</league_scoring_type>
		<managers>
			<manager>
				<manager_id>1</manager_id>
				<nickname>Steve</nickname>
				<guid>VJ...DM</guid>
				<is_commissioner>1</is_commissioner>
				<is_current_login>1</is_current_login>
				<email>st...om</email>
				<image_url>
				https://s.yimg.com/dh/ap/social/profile/profile_b64.png
				</image_url>
			</manager>
		</managers>
	</team>
</teams>

type TeamPointsResource

type TeamPointsResource struct {
	XMLName      xml.Name `xml:"team_points",json:"-"`
	CoverageType string   `xml:"coverage_type",json:",omitempty"`
	Week         string   `xml:"week",json:",omitempty"`
	Total        string   `xml:"total",json:",omitempty"`
}

type TeamProjectedPointsResource

type TeamProjectedPointsResource struct {
	XMLName      xml.Name `xml:"team_projected_points",json:"-"`
	CoverageType string   `xml:"coverage_type",json:",omitempty"`
	Week         string   `xml:"week",json:",omitempty"`
	Total        string   `xml:"total",json:",omitempty"`
}

type TeamResource

type TeamResource struct {
	XMLName               xml.Name                    `xml:"team",json:"-"`
	TeamKey               string                      `xml:"team_key",json:",omitempty"`
	TeamID                string                      `xml:"team_id",json:",omitempty"`
	Name                  string                      `xml:"name",json:",omitempty"`
	IsOwnedByCurrentLogin string                      `xml:"is_owned_by_current_login",json:",omitempty"`
	URL                   string                      `xml:"url",json:",omitempty"`
	TeamLogos             []TeamLogoResource          `xml:"team_logos>team_logo",omitempty"`
	WaiverPriority        string                      `xml:"waiver_priority",json:",omitempty"`
	NumberOfMoves         string                      `xml:"number_of_moves",json:",omitempty"`
	NumberOfTrades        string                      `xml:"number_of_trade",json:",omitempty"`
	RosterAdds            RosterAddsResource          `xml:"roster_adds",json:",omitempty"`
	LeageScoringType      string                      `xml:"league_scoring_type",json:",omitempty"`
	Managers              []ManagerResource           `xml:"managers>manager",json:",omitempty"`
	TeamPoints            TeamPointsResource          `xml:"team_points",json:",omitempty"`
	TeamProjectedPoints   TeamProjectedPointsResource `xml:"team_projected_points",json:",omitempty"`
}

type TransactionCollection

type TransactionCollection struct{}

Transactions collection With the Transactions API, you can obtain information via GET from a collection of transactions simultaneously. The transactions collection is qualified in the URI by a particular league. Each element beneath the Transactions Collection will be a Transaction Resource

You can also POST to the API to perform operations like adding and/or dropping players to/from a team and proposing trades.

type UserCollection

type UserCollection struct {
	XMLName xml.Name       `xml:"fantasy_content",json:"-"`
	Users   []UserResource `xml:"users>user",json:",omitempty"`
}

Users collection With the Users API, you can obtain information from a collection of users simultaneously. Each element beneath the Users Collection will be a User Resource

<fantasy_content xmlns:yahoo="http://www.yahooapis.com/v1/base.rng" xmlns="http://fantasysports.yahooapis.com/fantasy/v2/base.rng" xml:lang="en-US" yahoo:uri="http://fantasysports.yahooapis.com/fantasy/v2/users;use_login=1" time="22.95708656311ms" copyright="Data provided by Yahoo! and STATS, LLC" refresh_rate="31">
  <users count="1">
    <user>
      <guid>VJ....DM</guid>
    </user>
  </users>
</fantasy_content>

type UserResource

type UserResource struct {
	XMLName   xml.Name       `xml:"user",json:"-"`
	UserGuids []string       `xml:"guid",json:",omitempty"`
	Games     []GameResource `xml:"games>game",json:",omitempty"`
}

User resource With the User API, you can retrieve fantasy information for a particular Yahoo! user. Most usefully, you can see which games a user is playing, and which leagues they belong to and teams that they own within those games. Because you can currently only view user information for the logged in user, you would generally want to use the Users collection, passing along the use_login flag, instead of trying to request a User resource directly from the URI.

type YahooConfig

type YahooConfig struct {
	SessionStore sessions.Store
	// contains filtered or unexported fields
}

func NewYahooConfig

func NewYahooConfig(clientID, clientSecret string, scopes []string, hostName string, landing string, sessionStore sessions.Store) *YahooConfig

func (*YahooConfig) AcceptTrade

func (y *YahooConfig) AcceptTrade()

Accepting Trades Once you have the transaction_key for a pending trade that has been proposed to you, which you can get by asking the transactions collection for all pending trades for your team, you can choose to accept it. The input XML should look like:

<?xml version='1.0'?>
<fantasy_content>
  <transaction>
    <transaction_key>248.l.55438.pt.11</transaction_key>
    <type>pending_trade</type>
    <action>accept</action>
    <trade_note>Dude, that is a totally fair trade.</trade_note>
  </transaction>
</fantasy_content>

func (*YahooConfig) AllowTrade

func (y *YahooConfig) AllowTrade()

Allowing/Disallowing Trades If there are accepted trades in your league waiting to be processed, which you can get by asking the transactions collection for all pending trades for your team, and you’re the commissioner of a league that has the commissioner approve trades, you can choose to allow or disallow the trade. The input XML should look like:

<?xml version='1.0'?>
<fantasy_content>
  <transaction>
    <transaction_key>248.l.55438.pt.11</transaction_key>
    <type>pending_trade</type>
    <action>allow</action>
  </transaction>
</fantasy_content>

Or

<?xml version='1.0'?>
<fantasy_content>
  <transaction>
    <transaction_key>248.l.55438.pt.11</transaction_key>
    <type>pending_trade</type>
    <action>disallow</action>
  </transaction>
</fantasy_content>

func (*YahooConfig) AuthYahoo

func (a *YahooConfig) AuthYahoo(w http.ResponseWriter, r *http.Request)

func (*YahooConfig) AuthYahooCallback

func (a *YahooConfig) AuthYahooCallback(w http.ResponseWriter, r *http.Request)

func (*YahooConfig) DeletePendingTrade

func (y *YahooConfig) DeletePendingTrade()

func (*YahooConfig) DeleteWaiver

func (y *YahooConfig) DeleteWaiver()

DELETE Using DELETE, you may cancel any pending waiver claim or proposed trade. The URL for DELETEing a transaction resource is: http://fantasysports.yahooapis.com/fantasy/v2/transaction/

You can only DELETE transactions of the types waiver or pending_trade if the pending trade has not yet been accepted.

func (*YahooConfig) DisallowTrade

func (y *YahooConfig) DisallowTrade()

func (*YahooConfig) EditWaivers

func (y *YahooConfig) EditWaivers()

PUT Using PUT, you may edit the waiver priority or FAAB bid for any of your pending waiver claims. You can also accept or reject trades that have been proposed to you, and allow or vote against trades if your league settings allow it. The URL for PUTting to a Transaction resource is: http://fantasysports.yahooapis.com/fantasy/v2/transaction/

You can only PUT to Transactions of the types waiver or pending_trade.

Editing Waivers Once you have the transaction_key for a waiver claim, which you can get by asking the transactions collection for all waivers for a certain team, you can edit the waiver priority or FAAB bid. The input XML should look like:

<?xml version='1.0'?>
<fantasy_content>
  <transaction>
    <transaction_key>248.l.55438.w.c.2_6093</transaction_key>
    <type>waiver</type>
    <waiver_priority>1</waiver_priority>
    <faab_bid>20</faab_bid>
  </transaction>
</fantasy_content>

func (*YahooConfig) GetLeagueScoreboard

func (y *YahooConfig) GetLeagueScoreboard(r *http.Request) *LeagueCollection

func (*YahooConfig) GetLeagueStandings

func (y *YahooConfig) GetLeagueStandings(r *http.Request) *LeagueCollection

func (*YahooConfig) GetTransactionCollection

func (y *YahooConfig) GetTransactionCollection() *TransactionCollection

GetTransactionCollection

URI:http://fantasysports.yahooapis.com/fantasy/v2/league//transactions Description:Fetch all completed transactions within a league. Sample:http://fantasysports.yahooapis.com/fantasy/v2/league/223.l.431/transactions

URI:http://fantasysports.yahooapis.com/fantasy/v2/transactions;transaction_keys=,{transaction_key2} Description:Fetch specific transactions {transaction_key1} and {transaction_key2} Sample:http://fantasysports.yahooapis.com/fantasy/v2/transactions;transaction_keys=223.l.431.tr.26,223.l.431.tr.27

URI:http://fantasysports.yahooapis.com/fantasy/v2/leagues;league_keys={league_key1},{league_key2}/transactions Description:Fetch all completed transactions of the leagues {league_key1} and {league_key2} Sample:http://fantasysports.yahooapis.com/fantasy/v2/leagues;league_keys=223.l.431,223.l.21821/transactions

URI:http://fantasysports.yahooapis.com/fantasy/v2/league/{league_key}/transactions;types=waiver,pending_trade;team_key= Description:Fetch all pending trades and waivers relevant to the particular team. Sample:http://fantasysports.yahooapis.com/fantasy/v2/league/223.l.431/transactions;types=waiver,pending_trade;team_key=223.l.431.t.1

Any sub-resource valid for a transaction is a valid sub-resource under the transactions collection. Any sub-resource for a collection of transactions is extracted using a URI like:

 /transactions/{sub_resource}
OR
 /transactions;transaction_keys={transaction_key1},{transaction_key2}/{sub_resource}

Multiple sub-resources can be extracted from transactions in the same URI using a format like:

 /transactions;out={sub_resource_1},{sub_resource_2}
OR
 /transactions;transaction_keys={transaction_key1},{transaction_key2};out={sub_resource_1},{sub_resource_2}

Filters The transactions collection can have filters such as the following to obtain a subset of a transactions collection that satisfy the filtering condition. These filters can be combined to obtain a more restricted list of transactions.

func (*YahooConfig) GetUserCollectionAll

func (y *YahooConfig) GetUserCollectionAll(r *http.Request) *UserCollection

Any sub-resource valid for a user is a valid sub-resource under the users collection. Any sub-resource for a collection of users is extracted using a URI like:

/users;use_login=1/{sub_resource}

Multiple sub-resources can be extracted from users in the same URI using a format like:

/users;use_login=1;out={sub_resource_1},{sub_resource_2}
/users;field={field_name1},{field_name2}

func (*YahooConfig) GetUserCollectionGames

func (y *YahooConfig) GetUserCollectionGames(r *http.Request) *UserCollection

GetUserResource It is generally recommended that you instead use the Users collection, passing along the use_login flag.

Retrieve User Collection URIs

URI:
Description:Fetch user information of the logged-in user.
Sample:http://fantasysports.yahooapis.com/fantasy/v2/users;use_login=1

Sub-resources Name: Description: Fetch the Games in which the user has played. Additionally

accepts flags is_available to only return available games.

URI: /fantasy/v2/;use_login=1/games Sample: http://fantasysports.yahooapis.com/fantasy/v2/users;use_login=1/games

func (*YahooConfig) GetUserCollectionLeagues

func (y *YahooConfig) GetUserCollectionLeagues(r *http.Request) *UserCollection

Name: / Description: Fetch leagues that the user belongs to in one or more games. The leagues will be scoped to the user. This will throw an error if any of the specified games do not support league sub-resources. URI: /fantasy/v2/;use_login=1/games;game_keys=,{game_key2}/leagues Sample: http://fantasysports.yahooapis.com/fantasy/v2/users;use_login=1/games;game_keys=223/leagues

func (*YahooConfig) GetUserCollectionTeams

func (y *YahooConfig) GetUserCollectionTeams(r *http.Request) *UserCollection

Name: Description: Fetch teams owned by the user in one or more games. The teams

will be scoped to the user. This will throw an error if any of
the specified games do not support team sub-resources.

URI: /fantasy/v2/;use_login=1/games;game_keys=,{game_key2}/teams Sample: http://fantasysports.yahooapis.com/fantasy/v2/users;use_login=1/games;game_keys=223/teams

func (*YahooConfig) LeagueScoreboardHandler

func (y *YahooConfig) LeagueScoreboardHandler(w http.ResponseWriter, r *http.Request)

func (*YahooConfig) LeagueStandingsHandler

func (y *YahooConfig) LeagueStandingsHandler(w http.ResponseWriter, r *http.Request)

func (*YahooConfig) RegisterRoutes

func (a *YahooConfig) RegisterRoutes(r *mux.Router)

func (*YahooConfig) RejectTrade

func (y *YahooConfig) RejectTrade()

Rejecting Trades To reject a pending trade proposed to you, the input XML should look like:

<?xml version='1.0'?>
<fantasy_content>
  <transaction>
    <transaction_key>248.l.55438.pt.11</transaction_key>
    <type>pending_trade</type>
    <action>reject</action>
    <trade_note>No way!</trade_note>
  </transaction>
</fantasy_content>

func (*YahooConfig) UserCollectionAllHandler

func (y *YahooConfig) UserCollectionAllHandler(w http.ResponseWriter, r *http.Request)

func (*YahooConfig) UserCollectionGamesHandler

func (y *YahooConfig) UserCollectionGamesHandler(w http.ResponseWriter, r *http.Request)

func (*YahooConfig) UserCollectionLeaguesHandler

func (y *YahooConfig) UserCollectionLeaguesHandler(w http.ResponseWriter, r *http.Request)

func (*YahooConfig) UserCollectionTeamsHandler

func (y *YahooConfig) UserCollectionTeamsHandler(w http.ResponseWriter, r *http.Request)

func (*YahooConfig) VoteDownTrade

func (y *YahooConfig) VoteDownTrade()

Voting Against Trades If there are accepted trades in your league waiting to be processed, which you can get by asking the transactions collection for all pending trades for your team, and you’re a manager in a league that allows managers to vote against trades, you can choose to vote against the trade. The input XML should look like:

<?xml version='1.0'?>
<fantasy_content>
  <transaction>
    <transaction_key>248.l.55438.pt.11</transaction_key>
    <type>pending_trade</type>
    <action>vote_against</action>
    <voter_team_key>248.l.55438.t.2</voter_team_key>
  </transaction>
</fantasy_content>