Select A Category: All | Commissioner News
Show me an article titled
Site News
Secure League Pages (Published Thu Feb 6 12:24:02 p.m. ET 2020)

When your league is upgraded to the 2020 season, the option to Use SSL will be turned on automatically. This change should not have any effect on your league, except to make it more secure, so you should not notice any difference. However, there are a few instances where it can cause conflicts. That's why we give each league the option to choose whether or not they want to use the SSL setting on the Reports and Security Settings screen.

Here are some issues to be aware of with this option:

  • The option to use SSL was added in 2018, and about half of the leagues had switched to it already.
  • Some web browsers will give you warnings when accessing a non-secure site, and eventually some browsers may not even load non-secure sites, so it is strongly advised to leave your league set with the SSL option from now on.
  • We will eventually remove the option to use the non-secure option, most likely in the 2021 season.
  • The only reason we allow the non-secure option now is because of some potential conflicts with third party add-ons and links to images and other resources. For example, if your league uses custom code or you have icons or images that are linked to another site, and that other site is not secure, then it may cause your league appearance to have issues. If that is the case, then a "quick fix" is to turn off your league SSL option. But that is NOT a permanent fix! Instead, you should work on converting all of the non-secure images and links and add-ons to a secure environment. Sometimes that just means changing your "http://" links to "https://". This will work if the site you are linking to already supports SSL, which is the case for most web sites now. If not, then you'll have to either move your images and links to another server, or contact the site to have them update their security options.
  • Also be aware that if you have javascript included from a non-secure site, it could potentially expose your personally identifiable information, so that is an even more important reason to convert to using 100% secure links and sites.
2020 Developers API Release Notes (Published Tue Feb 4 4:00:00 p.m. ET 2020)

During this offseason we've made a few changes to the MyFantasyLeague.com Developer's API. These changes are described below. We will add entries here as necessary during the early part of the offseason. The goal is to have the API stable by mid-May. After that the only changes that we will make will be bug fixes.

  • First of all, we have introduced an API Client Registration process. While registering your client is not a requirement to use the API, you will want to register it if you plan to use it for any kind of significant tasks. Unregistered clients will be subject to usage limits. There's more information about this on the main Developers API page.
  • The live_chat request which was used to make draft picks has finally been removed. Last year we introduced the live_draft request as a replacement.
  • The FRANCHISE_ID parameter, which was used on a few import functions to specify the target franchise of an operation has been renamed to FRANCHISE. FRANCHISE_ID will now be used exclusively to specify the franchise to impersonate. The difference between target franchise and impersonate is subtle: using a target franchise the commissioner does an operation on an owner's franchise, while impersonate the commissioner does the operation as the franchise.
  • Non-league specific calls must be directed to api.myfantasyleague.com and be made via SSL protocol (https). These are all requests that do not have L= parameter. This requirement does not apply to calls embedded on league pages via javascript. In that case you must continue to use the local host to avoid cross-domain issues.
  • The ADP request parameters have been changed. The FRANCHISES parameter has been renamed FCOUNT to avoid confusion with other uses of FRANCHISES, and the way to filter results by time has been completely revamped. This is now a simpler system that relies on specifying the PERIOD parameter to request data for drafts that started after one of a several key dates.
  • (Added Feb 5)The Trades requests now work with a trade ID. Instead of having to pass the various trade elements on every request, now the tradeResponse can indicate which trade to operate on via a trade id. The pendingTrades request will provide these ids.

File last updated on February 6, 2020.