### Yahoo Fantasy Sports API Player Data XML Example

Source: https://developer.yahoo.com/fantasysports/index

This XML snippet provides a detailed example of the player data structure returned by the Yahoo Fantasy Sports API. It includes various attributes such as player keys, IDs, full names, editorial team information, uniform numbers, display positions, image URLs, eligibility, and starting status for multiple players.

```XML
          <image_url>https://l.yimg.com/a/i/us/sp/v/mlb/players_l/20110503x/7746.jpg?x=46&amp;y=60&amp;xc=1&amp;yc=1&amp;wc=164&amp;hc=215&amp;q=100&amp;sig=O01i1gfOs6RgisJQjmdipQ--</image_url>
          <is_undroppable>0</is_undroppable>
          <position_type>B</position_type>
          <eligible_positions>
            <position>1B</position>
            <position>2B</position>
            <position>OF</position>
            <position>Util</position>
          </eligible_positions>
          <has_player_notes>1</has_player_notes>
          <has_recent_player_notes>1</has_recent_player_notes>
          <selected_position>
            <coverage_type>date</coverage_type>
            <date>2011-07-22</date>
            <position>2B</position>
          </selected_position>
          <starting_status>
            <coverage_type>date</coverage_type>
            <date>2011-07-22</date>
            <is_starting>0</is_starting>
          </starting_status>
        </player>
        <player>
          <player_key>253.p.7737</player_key>
          <player_id>7737</player_id>
          <name>
            <full>Martin Prado</full>
            <first>Martin</first>
            <last>Prado</last>
            <ascii_first>Martin</ascii_first>
            <ascii_last>Prado</ascii_last>
          </name>
          <editorial_player_key>mlb.p.7737</editorial_player_key>
          <editorial_team_key>mlb.t.15</editorial_team_key>
          <editorial_team_full_name>Atlanta Braves</editorial_team_full_name>
          <editorial_team_abbr>Atl</editorial_team_abbr>
          <uniform_number>14</uniform_number>
          <display_position>2B,3B,OF</display_position>
          <image_url>https://l.yimg.com/a/i/us/sp/v/mlb/players_l/20110503x/7737.jpg?x=46&amp;y=60&amp;xc=1&amp;yc=1&amp;wc=164&amp;hc=215&amp;q=100&amp;sig=WPYI1xO62JwsL8QturlmJw--</image_url>
          <is_undroppable>0</is_undroppable>
          <position_type>B</position_type>
          <eligible_positions>
            <position>2B</position>
            <position>3B</position>
            <position>OF</position>
            <position>Util</position>
          </eligible_positions>
          <has_player_notes>1</has_player_notes>
          <selected_position>
            <coverage_type>date</coverage_type>
            <date>2011-07-22</date>
            <position>3B</position>
          </selected_position>
          <starting_status>
            <coverage_type>date</coverage_type>
            <date>2011-07-22</date>
            <is_starting>1</is_starting>
          </starting_status>
        </player>
        <player>
          <player_key>253.p.7744</player_key>
          <player_id>7744</player_id>
          <name>
            <full>Erick Aybar</full>
            <first>Erick</first>
            <last>Aybar</last>
            <ascii_first>Erick</ascii_first>
            <ascii_last>Aybar</ascii_last>
          </name>
          <editorial_player_key>mlb.p.7744</editorial_player_key>
          <editorial_team_key>mlb.t.3</editorial_team_key>
          <editorial_team_full_name>Los Angeles Angels</editorial_team_full_name>
          <editorial_team_abbr>LAA</editorial_team_abbr>
          <uniform_number>2</uniform_number>
          <display_position>SS</display_position>
          <image_url>https://l.yimg.com/a/i/us/sp/v/mlb/players_l/20110503x/7744.jpg?x=46&amp;y=60&amp;xc=1&amp;yc=1&amp;wc=164&amp;hc=215&amp;q=100&amp;sig=qHzsNyGFtGYxlpMxtysSPQ--</image_url>
          <is_undroppable>0</is_undroppable>
          <position_type>B</position_type>
          <eligible_positions>
            <position>SS</position>
            <position>Util</position>
          </eligible_positions>
          <selected_position>
            <coverage_type>date</coverage_type>
            <date>2011-07-22</date>
            <position>SS</position>
          </selected_position>
          <starting_status>
            <coverage_type>date</coverage_type>
            <date>2011-07-22</date>
            <is_starting>1</is_starting>
          </starting_status>
        </player>
        <player>
          <player_key>253.p.7977</player_key>
          <player_id>7977</player_id>
          <name>
            <full>Andrew McCutchen</full>
            <first>Andrew</first>
            <last>McCutchen</last>
            <ascii_first>Andrew</ascii_first>
            <ascii_last>McCutchen</ascii_last>
          </name>
          <editorial_player_key>mlb.p.7977</editorial_player_key>
          <editorial_team_key>mlb.t.23</editorial_team_key>
          <editorial_team_full_name>Pittsburgh Pirates</editorial_team_full_name>
          <editorial_team_abbr>Pit</editorial_team_abbr>
          <uniform_number>22</uniform_number>
          <display_position>OF</display_position>
          <image_url>https://l.yimg.com/a/p/sp/tools/med/2011/05/ipt/1304541420.jpg?x=46&amp;y=60&amp;xc=1&amp;yc=1&amp;wc=164&amp;hc=215&amp;q=100&amp;sig=61GeaeZwqXZWy2ITOX62Zg--</image_url>
```

--------------------------------

### Yahoo Fantasy Sports Matchup and Team XML Example

Source: https://developer.yahoo.com/fantasysports/guide

This XML snippet provides an example of a Yahoo Fantasy Sports API response for a matchup, showcasing the detailed structure for individual teams. It includes team keys, IDs, names, URLs, logo information, division IDs, FAAB balance, playoff clinching status, manager details (ID, nickname, GUID), and weekly points (actual and projected).

```XML
                <team_logo>
                  <size>medium</size>
                  <url>https://a323.yahoofs.com/coreid/49be42a6i26e5zul3re3/d2x_9_UweKP95SJZ_Hwnk2Rl/2/tn48.jpg?ciA8DVOBIRa6b7wq</url>
                </team_logo>
              </team_logos>
              <division_id>2</division_id>
              <faab_balance>1</faab_balance>
              <clinched_playoffs>1</clinched_playoffs>
              <managers>
                <manager>
                  <manager_id>12</manager_id>
                  <nickname>-- hidden --</nickname>
                  <guid>RW3ELDFMOFTES2EUAWQVCPPN7E</guid>
                </manager>
              </managers>
              <team_points>
                <coverage_type>week</coverage_type>
                <week>16</week>
                <total>135.22</total>
              </team_points>
              <team_projected_points>
                <coverage_type>week</coverage_type>
                <week>16</week>
                <total>142.81</total>
              </team_projected_points>
            </team>
            <team>
              <team_key>223.l.431.t.10</team_key>
              <team_id>10</team_id>
              <name>Gehlken</name>
              <url>https://football.fantasysports.yahoo.com/archive/pnfl/2009/431/10</url>
              <team_logos>
                <team_logo>
                  <size>medium</size>
                  <url>https://a323.yahoofs.com/coreid/4b978f0ci2432zws140sp2/imXqmYo8cq3NxEFtQB4wgAs-/6/tn48.jpeg?ciA8DVOBMH.UXGXk</url>
                </team_logo>
              </team_logos>
              <division_id>1</division_id>
              <faab_balance>0</faab_balance>
              <clinched_playoffs>1</clinched_playoffs>
              <managers>
                <manager>
                  <manager_id>5</manager_id>
                  <nickname>-- hidden --</nickname>
                  <guid>4LAITFUXFASDNAXFWUOHWNU3BY</guid>
                </manager>
              </managers>
              <team_points>
                <coverage_type>week</coverage_type>
                <week>16</week>
                <total>137.86</total>
              </team_points>
              <team_projected_points>
                <coverage_type>week</coverage_type>
                <week>16</week>
                <total>133.57</total>
              </team_projected_points>
            </team>
          </teams>
        </matchup>
        <matchup>
          <week>16</week>
          <status>postevent</status>
          <is_tied>0</is_tied>
          <winner_team_key>223.l.431.t.8</winner_team_key>
          <teams count="2">
            <team>
              <team_key>223.l.431.t.8</team_key>
              <team_id>8</team_id>
              <name>Y! - Pianowski</name>
              <url>https://football.fantasysports.yahoo.com/archive/pnfl/2009/431/8</url>
              <team_logos>
                <team_logo>
                  <size>medium</size>
                  <url>https://l.yimg.com/a/i/us/sp/fn/default/full/nfl/icon_10_48.gif</url>
                </team_logo>
              </team_logos>
              <division_id>1</division_id>
              <faab_balance>0</faab_balance>
              <clinched_playoffs>1</clinched_playoffs>
              <managers>
                <manager>
                  <manager_id>6</manager_id>
                  <nickname>-- hidden --</nickname>
                  <guid>WMKEJTV3VUJA4VZWQ25O27W43M</guid>
                </manager>
              </managers>
              <team_points>
                <coverage_type>week</coverage_type>
                <week>16</week>
                <total>103.39</total>
              </team_points>
              <team_projected_points>
                <coverage_type>week</coverage_type>
                <week>16</week>
                <total>104.17</total>
              </team_projected_points>
            </team>
            <team>
              <team_key>223.l.431.t.12</team_key>
              <team_id>12</team_id>
              <name>Y! - Behrens</name>
              <url>https://football.fantasysports.yahoo.com/archive/pnfl/2009/431/12</url>
              <team_logos>
                <team_logo>
                  <size>medium</size>
                  <url>https://lookup.avatars.yahoo.com/images?yid=abehrens53&amp;size=medium&amp;type=jpg&amp;pty=3000</url>
                </team_logo>
              </team_logos>
              <division_id>1</division_id>
              <faab_balance>0</faab_balance>
              <clinched_playoffs>1</clinched_playoffs>
              <managers>
                <manager>
                  <manager_id>3</manager_id>
                  <nickname>-- hidden --</nickname>
                  <guid>E2KS77CDQPACRTSBCYPOFFW6AI</guid>
                </manager>
              </managers>
              <team_points>
                <coverage_type>week</coverage_type>
                <week>16</week>
                <total>101.94</total>
              </team_points>
```

--------------------------------

### Example XML Response for Player Statistics and Points

Source: https://developer.yahoo.com/fantasysports/index

An example XML structure showing player statistics and total points for a season within the Yahoo Fantasy Sports API context. This snippet illustrates the format for individual player data, including stat IDs, values, coverage type, season, and total points.

```XML
              <stat_id>6</stat_id>
              <value>11</value>
            </stat>
            <stat>
              <stat_id>9</stat_id>
              <value>33</value>
            </stat>
            <stat>
              <stat_id>10</stat_id>
              <value>2</value>
            </stat>
            <stat>
              <stat_id>11</stat_id>
              <value>1</value>
            </stat>
            <stat>
              <stat_id>12</stat_id>
              <value>-4</value>
            </stat>
            <stat>
              <stat_id>13</stat_id>
              <value>0</value>
            </stat>
            <stat>
              <stat_id>15</stat_id>
              <value>0</value>
            </stat>
            <stat>
              <stat_id>16</stat_id>
              <value>0</value>
            </stat>
            <stat>
              <stat_id>18</stat_id>
              <value>6</value>
            </stat>
            <stat>
              <stat_id>57</stat_id>
              <value>0</value>
            </stat>
          </stats>
        </player_stats>
        <player_points>
          <coverage_type>season</coverage_type>
          <season>2009</season>
          <total>310.17</total>
        </player_points>
      </player>
    </players>
  </league>
</fantasy_content>
```

--------------------------------

### Example of Chaining Sub-Resources in Yahoo Fantasy API

Source: https://developer.yahoo.com/fantasysports/guide

Demonstrates how to construct a URI to chain multiple resources and collections, such as a logged-in user, their games, and leagues within those games, using the Yahoo Fantasy Sports API.

```APIDOC
/fantasy/v2/;use_login=1//
```

--------------------------------

### PHP Yahoo OAuth 1.0a Authentication and API Access Example

Source: https://developer.yahoo.com/fantasysports/guide

This comprehensive PHP example demonstrates the full OAuth 1.0a authentication flow for Yahoo APIs. It covers obtaining a request token, user authorization via a URL, capturing the verifier, exchanging for an access token, and then using that access token to make a sample API call. The script also includes logic to persist the access token data to a file for subsequent use, avoiding repeated authorization steps. Error handling for OAuth exceptions and API request failures is integrated.

```php
// 3. If none of that worked, send the user to get a new token
if( ! $access_token ) {

  print "Better try to get a new access token.\n";
  $o = new OAuth( $consumer_key, $consumer_secret,
                  OAUTH_SIG_METHOD_HMACSHA1, OAUTH_AUTH_TYPE_URI );
  $o->enableDebug();

  $request_token = NULL;

  try {
    $response = $o->getRequestToken( "https://api.login.yahoo.com/oauth/v2/get_request_token", 'oob' );
    $request_token = $response['oauth_token'];
    $request_secret = $response['oauth_token_secret'];

    print "Hey! Go to this URL and tell us the verifier you get at the end.\n";
    print ' ' . $response['xoauth_request_auth_url'] . "\n";

  } catch( OAuthException $e ) {
    print $e->getMessage() . "\n";
  }

  // Wait for input, then try to use it to get a new access token.
  if( $request_token && $request_secret ) {
    print "Type the verifier and hit enter...\n";
    $verifier = fgets( STDIN );
    $verifier = rtrim( $verifier );

    print "Here's the verifier you gave us: ${verifier}\n";

    try {
      $o->setToken( $request_token, $request_secret );
      $response = $o->getAccessToken( 'https://api.login.yahoo.com/oauth/v2/get_token', NULL, $verifier );

      print "Got it!\n";
      $access_token = $response['oauth_token'];
      $access_secret = $response['oauth_token_secret'];
      $access_session = $response['oauth_session_handle'];
      $store_access_token_data = true;
      print " Token: ${access_token}\n";
      print " Secret: ${access_secret}\n";
      print " Session Handle: ${access_session}\n\n";

    } catch( OAuthException $e ) {
      print 'Error: ' . $e->getMessage() . "\n";
      print 'Response: ' . $e->lastResponse . "\n";
      print "Shoot, couldn't get the access token. :(\n";
    }
  }

}

if( $access_token ) {

  // Try to make request using stored token
  try {
    $o->setToken( $access_token, $access_secret );
    if( $o->fetch( $url ) ) {
      print "Got data from API:\n\n";
      print $o->getLastResponse() . "\n\n";

      print "Successful!\n";
    } else {
      print "Couldn't fetch\n";
    }
  } catch( OAuthException $e ) {
    print 'Error: ' . $e->getMessage() . "\n";
    print 'Error Code: ' . $e->getCode() . "\n";
    print 'Response: ' . $e->lastResponse . "\n";
  }
}

// 4. Rewrite token information if necessary
if( $store_access_token_data ) {

  print "Looks like we need to store access token data! Doing that now.\n";

  $tok_fh = fopen( $token_file_name, 'w' );
  if( $tok_fh ) {
    fwrite( $tok_fh, "${access_token}\n" );
    fwrite( $tok_fh, "${access_secret}\n" );
    fwrite( $tok_fh, "${access_session}\n" );

    fclose( $tok_fh );
  } else {
    print "Hm, couldn't open file to write back access token information.\n";
  }
}
?>
```

--------------------------------

### Example Player Roster Data XML

Source: https://developer.yahoo.com/fantasysports/guide

An example XML structure representing player data within a fantasy team's roster, including player details, positions, and status. This illustrates the typical response format for retrieving roster information.

```XML
<eligible_positions>
            </eligible_positions>
          <selected_position>
            <coverage_type>date</coverage_type>
            <date>2011-07-22</date>
            <position>BN</position>
          </selected_position>
        </player>
        <player>
          <player_key>253.p.6571</player_key>
          <player_id>6571</player_id>
          <name>
            <full>Ryan Vogelsong</full>
            <first>Ryan</first>
            <last>Vogelsong</last>
            <ascii_first>Ryan</ascii_first>
            <ascii_last>Vogelsong</ascii_last>
          </name>
          <editorial_player_key>mlb.p.6571</editorial_player_key>
          <editorial_team_key>mlb.t.26</editorial_team_key>
          <editorial_team_full_name>San Francisco Giants</editorial_team_full_name>
          <editorial_team_abbr>SF</editorial_team_abbr>
          <uniform_number>32</uniform_number>
          <display_position>SP,RP</display_position>
          <image_url>https://l.yimg.com/a/i/us/sp/v/mlb/players_l/20110706/6571.jpg?x=46&amp;y=60&amp;xc=1&amp;yc=1&amp;wc=164&amp;hc=215&amp;q=100&amp;sig=bdeeFeFntdasbz_0xzXCGA--</image_url>
          <is_undroppable>0</is_undroppable>
          <position_type>P</position_type>
          <eligible_positions>
            <position>SP</position>
            <position>RP</position>
            <position>P</position>
          </eligible_positions>
          <has_player_notes>1</has_player_notes>
          <selected_position>
            <coverage_type>date</coverage_type>
            <date>2011-07-22</date>
            <position>BN</position>
          </selected_position>
        </player>
        <player>
          <player_key>253.p.7382</player_key>
          <player_id>7382</player_id>
          <name>
            <full>David Wright</full>
            <first>David</first>
            <last>Wright</last>
            <ascii_first>David</ascii_first>
            <ascii_last>Wright</ascii_last>
          </name>
          <status>DL</status>
          <on_disabled_list>1</on_disabled_list>
          <editorial_player_key>mlb.p.7382</editorial_player_key>
          <editorial_team_key>mlb.t.21</editorial_team_key>
          <editorial_team_full_name>New York Mets</editorial_team_full_name>
          <editorial_team_abbr>NYM</editorial_team_abbr>
          <uniform_number>5</uniform_number>
          <display_position>3B</display_position>
          <image_url>https://l.yimg.com/a/i/us/sp/v/mlb/players_l/20110503x/7382.jpg?x=46&amp;y=60&amp;xc=1&amp;yc=1&amp;wc=164&amp;hc=215&amp;q=100&amp;sig=QNOFMSgR6NuPxUwDMUSM1w--</image_url>
          <is_undroppable>0</is_undroppable>
          <position_type>B</position_type>
          <eligible_positions>
            <position>3B</position>
            <position>Util</position>
            <position>DL</position>
          </eligible_positions>
          <has_player_notes>1</has_player_notes>
          <has_recent_player_notes>1</has_recent_player_notes>
          <selected_position>
            <coverage_type>date</coverage_type>
            <date>2011-07-22</date>
            <position>DL</position>
          </selected_position>
          <starting_status>
            <coverage_type>date</coverage_type>
            <date>2011-07-22</date>
            <is_starting>1</is_starting>
          </starting_status>
        </player>
      </players>
    </roster>
  </team>
</fantasy_content>
```

--------------------------------

### Example XML Response for Team Stats

Source: https://developer.yahoo.com/fantasysports/guide

An example XML structure showing statistical data for a team in Yahoo Fantasy Sports, including various stat IDs and their corresponding values for a specific date.

```XML
      <date>2011-07-06</date>
      <stats>
        <stat>
          <stat_id>60</stat_id>
          <value>13/31</value>
        </stat>
        <stat>
          <stat_id>7</stat_id>
          <value>9</value>
        </stat>
        <stat>
          <stat_id>12</stat_id>
          <value>3</value>
        </stat>
        <stat>
          <stat_id>13</stat_id>
          <value>11</value>
        </stat>
        <stat>
          <stat_id>16</stat_id>
          <value>1</value>
        </stat>
        <stat>
          <stat_id>3</stat_id>
          <value>.419</value>
        </stat>
        <stat>
          <stat_id>50</stat_id>
          <value>7.0</value>
        </stat>
        <stat>
          <stat_id>28</stat_id>
          <value>1</value>
        </stat>
        <stat>
          <stat_id>32</stat_id>
          <value>0</value>
        </stat>
        <stat>
          <stat_id>42</stat_id>
          <value>6</value>
        </stat>
        <stat>
          <stat_id>26</stat_id>
          <value>1.29</value>
        </stat>
        <stat>
          <stat_id>27</stat_id>
          <value>0.71</value>
        </stat>
      </stats>
```

--------------------------------

### Users Collection URI Examples

Source: https://developer.yahoo.com/fantasysports/guide

Illustrates various URI formats for extracting single or multiple sub-resources from the Users collection, including login and field-specific queries, demonstrating how to construct API requests.

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

--------------------------------

### Example XML for Yahoo Fantasy Sports Team Data

Source: https://developer.yahoo.com/fantasysports/guide

This XML snippet provides a detailed structure for multiple fantasy sports teams, including their unique key, ID, name, associated URLs, team logos, division ID, FAAB balance, manager details (ID, nickname, GUID, commissioner status), season points, and comprehensive standings (rank, wins, losses, ties, percentage, divisional outcomes). Note that the first team's opening tag was inferred to complete the snippet.

```XML
<team>
          <name>Erickson - RotoWire</name>
          <url>https://football.fantasysports.yahoo.com/archive/pnfl/2009/431/13</url>
          <team_logos>
            <team_logo>
              <size>medium</size>
              <url>https://lookup.avatars.yahoo.com/images?yid=jeff_rotonews&amp;size=medium&amp;type=jpg&amp;pty=3000</url>
            </team_logo>
          </team_logos>
          <division_id>2</division_id>
          <faab_balance>17</faab_balance>
          <managers>
            <manager>
              <manager_id>11</manager_id>
              <nickname>-- hidden --</nickname>
              <guid>SB4Y5HVVUKMCTKZFQCXHIZ222E</guid>
            </manager>
          </managers>
          <team_points>
            <coverage_type>season</coverage_type>
            <season>2009</season>
            <total>1484.56</total>
          </team_points>
          <team_standings>
            <rank>9</rank>
            <outcome_totals>
              <wins>6</wins>
              <losses>7</losses>
              <ties>0</ties>
              <percentage>.462</percentage>
            </outcome_totals>
            <divisional_outcome_totals>
              <wins>3</wins>
              <losses>3</losses>
              <ties>0</ties>
            </divisional_outcome_totals>
          </team_standings>
        </team>
        <team>
          <team_key>223.l.431.t.9</team_key>
          <team_id>9</team_id>
          <name>Y! - Funston</name>
          <url>https://football.fantasysports.yahoo.com/archive/pnfl/2009/431/9</url>
          <team_logos>
            <team_logo>
              <size>medium</size>
              <url>https://lookup.avatars.yahoo.com/images?yid=brandoanf1&amp;size=medium&amp;type=jpg&amp;pty=3000</url>
            </team_logo>
          </team_logos>
          <division_id>1</division_id>
          <faab_balance>10</faab_balance>
          <managers>
            <manager>
              <manager_id>1</manager_id>
              <nickname>-- hidden --</nickname>
              <guid>3H7IQ3F2742K2ODHSJK5YXL23E</guid>
              <is_commissioner>1</is_commissioner>
            </manager>
          </managers>
          <team_points>
            <coverage_type>season</coverage_type>
            <season>2009</season>
            <total>1430.24</total>
          </team_points>
          <team_standings>
            <rank>10</rank>
            <outcome_totals>
              <wins>6</wins>
              <losses>7</losses>
              <ties>0</ties>
              <percentage>.462</percentage>
            </outcome_totals>
            <divisional_outcome_totals>
              <wins>2</wins>
              <losses>4</losses>
              <ties>0</ties>
            </divisional_outcome_totals>
          </team_standings>
        </team>
        <team>
          <team_key>223.l.431.t.7</team_key>
          <team_id>7</team_id>
          <name>RotoWire_Liss</name>
          <url>https://football.fantasysports.yahoo.com/archive/pnfl/2009/431/7</url>
          <team_logos>
            <team_logo>
              <size>medium</size>
              <url>https://l.yimg.com/a/i/us/sp/fn/default/full/nfl/icon_10_48.gif</url>
            </team_logo>
          </team_logos>
          <division_id>2</division_id>
          <faab_balance>68</faab_balance>
          <managers>
            <manager>
              <manager_id>7</manager_id>
              <nickname>-- hidden --</nickname>
              <guid>4BDB5LIG3IFVROH7SRBX44LBZM</guid>
            </manager>
          </managers>
          <team_points>
            <coverage_type>season</coverage_type>
            <season>2009</season>
            <total>1424.56</total>
          </team_points>
          <team_standings>
            <rank>11</rank>
            <outcome_totals>
              <wins>6</wins>
              <losses>7</losses>
              <ties>0</ties>
              <percentage>.462</percentage>
            </outcome_totals>
            <divisional_outcome_totals>
              <wins>3</wins>
              <losses>3</losses>
              <ties>0</ties>
            </divisional_outcome_totals>
          </team_standings>
        </team>
```

--------------------------------

### Example XML Response for Yahoo Fantasy Sports Scoreboard

Source: https://developer.yahoo.com/fantasysports/index

This XML snippet provides an example response from the Yahoo Fantasy Sports API's scoreboard endpoint. It details league information such as key, ID, name, URL, draft status, number of teams, and scoring type. Crucially, it includes scoreboard data with the current week and individual matchup details, including team keys, IDs, names, and URLs for participating teams.

```XML
<?xml version="1.0" encoding="UTF-8"?>
<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/league/223.l.431/scoreboard" time="148.71311187744ms" copyright="Data provided by Yahoo! and STATS, LLC">
  <league>
    <league_key>223.l.431</league_key>
    <league_id>431</league_id>
    <name>Y! Friends and Family League</name>
    <url>https://football.fantasysports.yahoo.com/archive/pnfl/2009/431</url>
    <draft_status>postdraft</draft_status>
    <num_teams>14</num_teams>
    <edit_key>17</edit_key>
    <weekly_deadline/>
    <league_update_timestamp>1262595518</league_update_timestamp>
    <scoring_type>head</scoring_type>
    <current_week>16</current_week>
    <start_week>1</start_week>
    <end_week>16</end_week>
    <is_finished>1</is_finished>
    <scoreboard>
      <week>16</week>
      <matchups count="2">
        <matchup>
          <week>16</week>
          <status>postevent</status>
          <is_tied>0</is_tied>
          <winner_team_key>223.l.431.t.10</winner_team_key>
          <teams count="2">
            <team>
              <team_key>223.l.431.t.5</team_key>
              <team_id>5</team_id>
              <name>RotoExperts</name>
              <url>https://football.fantasysports.yahoo.com/archive/pnfl/2009/431/5</url>
              <team_logos>
```

--------------------------------

### Example XML Response for Team Projected Points

Source: https://developer.yahoo.com/fantasysports/index

An example XML structure showing projected points for a team within a fantasy league, including coverage type, week, and total points. This snippet is part of a larger fantasy content structure.

```XML
              <team_projected_points>
                <coverage_type>week</coverage_type>
                <week>16</week>
                <total>127.28</total>
              </team_projected_points>
            </team>
          </teams>
        </matchup>
      </matchups>
    </scoreboard>
  </league>
</fantasy_content>
```

--------------------------------

### Yahoo Fantasy Sports API: League Key Format

Source: https://developer.yahoo.com/fantasysports/index

Explains the specific format for league keys used in the API, providing examples and a crucial note about the separator character.

```APIDOC
.l.{league_id}

Example: pnfl.l.431 or 223.l.431

Note: The separator between the game_key and league_id is a lower case L (not the number 1).
```

--------------------------------

### Example XML Response for Player Statistics

Source: https://developer.yahoo.com/fantasysports/guide

Illustrates the structure of player statistics and points data returned by the Yahoo Fantasy Sports API. This includes individual stat IDs and their corresponding values, as well as total season points for a player.

```xml
<stat_id>6</stat_id>
              <value>11</value>
            </stat>
            <stat>
              <stat_id>9</stat_id>
              <value>33</value>
            </stat>
            <stat>
              <stat_id>10</stat_id>
              <value>2</value>
            </stat>
            <stat>
              <stat_id>11</stat_id>
              <value>1</value>
            </stat>
            <stat>
              <stat_id>12</stat_id>
              <value>-4</value>
            </stat>
            <stat>
              <stat_id>13</stat_id>
              <value>0</value>
            </stat>
            <stat>
              <stat_id>15</stat_id>
              <value>0</value>
            </stat>
            <stat>
              <stat_id>16</stat_id>
              <value>0</value>
            </stat>
            <stat>
              <stat_id>18</stat_id>
              <value>6</value>
            </stat>
            <stat>
              <stat_id>57</stat_id>
              <value>0</value>
            </stat>
          </stats>
        </player_stats>
        <player_points>
          <coverage_type>season</coverage_type>
          <season>2009</season>
          <total>310.17</total>
        </player_points>
      </player>
    </players>
  </league>
</fantasy_content>
```

--------------------------------

### Constructing a Chained Sub-Resource Request URI

Source: https://developer.yahoo.com/fantasysports/index

This example URI demonstrates how to chain multiple sub-resources (Users, Games, Leagues) for a logged-in user within the Yahoo Fantasy Sports API. It illustrates the hierarchical retrieval of user-specific game and league information by specifying the resource path.

```APIDOC
/fantasy/v2/;use_login=1//
```

--------------------------------

### Yahoo Fantasy Sports Team XML Structure Example

Source: https://developer.yahoo.com/fantasysports/guide

An example of the XML structure for a single fantasy sports team, detailing its various attributes and nested elements like team logos, managers, points, and standings. This structure is typically returned by the Yahoo Fantasy Sports API when querying team-specific information.

```XML
        <team>
          <team_key>223.l.431.t.8</team_key>
          <team_id>8</team_id>
          <name>Y! - Pianowski</name>
          <url>https://football.fantasysports.yahoo.com/archive/pnfl/2009/431/8</url>
          <team_logos>
            <team_logo>
              <size>medium</size>
              <url>https://l.yimg.com/a/i/us/sp/fn/default/full/nfl/icon_10_48.gif</url>
            </team_logo>
          </team_logos>
          <division_id>1</division_id>
          <faab_balance>0</faab_balance>
          <clinched_playoffs>1</clinched_playoffs>
          <managers>
            <manager>
              <manager_id>6</manager_id>
              <nickname>-- hidden --</nickname>
              <guid>WMKEJTV3VUJA4VZWQ25O27W43M</guid>
            </manager>
          </managers>
          <team_points>
            <coverage_type>season</coverage_type>
            <season>2009</season>
            <total>1569.48</total>
          </team_points>
          <team_standings>
            <rank>3</rank>
            <outcome_totals>
              <wins>8</wins>
              <losses>5</losses>
              <ties>0</ties>
              <percentage>.615</percentage>
            </outcome_totals>
            <divisional_outcome_totals>
              <wins>4</wins>
              <losses>2</losses>
              <ties>0</ties>
            </divisional_outcome_totals>
          </team_standings>
        </team>
```

--------------------------------

### Example XML Response for Fantasy Sports Matchup

Source: https://developer.yahoo.com/fantasysports/index

This XML snippet illustrates the detailed structure of a Yahoo Fantasy Sports API response for a team matchup, including information about participating teams, their managers, team logos, and weekly points.

```xml
        <is_tied>0</is_tied>
        <winner_team_key>223.l.431.t.1</winner_team_key>
        <teams count="2">
          <team>
            <team_key>223.l.431.t.1</team_key>
            <team_id>1</team_id>
            <name>PFW - Blunda</name>
            <url>https://football.fantasysports.yahoo.com/archive/pnfl/2009/431/1</url>
            <team_logos>
              <team_logo>
                <size>medium</size>
                <url>https://l.yimg.com/a/i/us/sp/fn/default/full/nfl/icon_01_48.gif</url>
              </team_logo>
            </team_logos>
            <division_id>2</division_id>
            <faab_balance>22</faab_balance>
            <managers>
              <manager>
                <manager_id>13</manager_id>
                <nickname>Michael Blunda</nickname>
                <guid>XNAXQZRDZPJ3RVFMY7ZTSWEFLU</guid>
              </manager>
            </managers>
            <team_points>
              <coverage_type>week</coverage_type>
              <week>5</week>
              <total>140.00</total>
            </team_points>
            <team_projected_points>
              <coverage_type>week</coverage_type>
              <week>5</week>
              <total>110.85</total>
            </team_projected_points>
          </team>
          <team>
            <team_key>223.l.431.t.7</team_key>
            <team_id>7</team_id>
            <name>RotoWire_Liss</name>
            <url>https://football.fantasysports.yahoo.com/archive/pnfl/2009/431/7</url>
            <team_logos>
              <team_logo>
                <size>medium</size>
                <url>https://l.yimg.com/a/i/us/sp/fn/default/full/nfl/icon_10_48.gif</url>
              </team_logo>
            </team_logos>
            <division_id>2</division_id>
            <faab_balance>68</faab_balance>
            <managers>
              <manager>
                <manager_id>7</manager_id>
                <nickname>RotoWire_Liss</nickname>
                <guid>4BDB5LIG3IFVROH7SRBX44LBZM</guid>
              </manager>
            </managers>
            <team_points>
              <coverage_type>week</coverage_type>
              <week>5</week>
              <total>86.47</total>
            </team_points>
            <team_projected_points>
              <coverage_type>week</coverage_type>
              <week>5</week>
              <total>88.14</total>
            </team_projected_points>
          </team>
        </teams>
      </matchup>
    </matchups>
  </team>
</fantasy_content>
```

--------------------------------

### Example Transaction Data Structure (GET Response)

Source: https://developer.yahoo.com/fantasysports/guide

This XML snippet illustrates the structure of a transaction object, typically returned by a GET request to the transactions collection. It shows details for two players involved in a pending trade, including their names and transaction data.

```XML
<fantasy_content>
  <transaction>
    <player>
      <player_key>257.p.6789</player_key>
      <player_id>6789</player_id>
      <name>
        <full>Adrian Peterson</full>
        <first>Adrian</first>
        <last>Peterson</last>
        <ascii_first>Adrian</ascii_first>
        <ascii_last>Peterson</ascii_last>
      </name>
      <transaction_data>
        <type>pending_trade</type>
        <source_type>team</source_type>
        <source_team_key>257.l.193.t.2</source_team_key>
        <destination_type>team</destination_type>
        <destination_team_key>257.l.193.t.1</destination_team_key>
      </transaction_data>
    </player>
    <player>
      <player_key>257.p.9527</player_key>
      <player_id>9527</player_id>
      <name>
        <full>Arian Foster</full>
        <first>Arian</first>
        <last>Foster</last>
        <ascii_first>Arian</ascii_first>
        <ascii_last>Foster</ascii_last>
      </name>
      <transaction_data>
        <type>pending_trade</type>
        <source_type>team</source_type>
        <source_team_key>257.l.193.t.1</source_team_key>
        <destination_type>team</destination_type>
        <destination_team_key>257.l.193.t.2</destination_team_key>
      </transaction_data>
    </player>
  </transaction>
</fantasy_content>
```