Project News
Championship Schedules
Each year FIRST releases preliminary schedules for FRC matches. When we do so, they _do not_ come through on the API and the webpages. We do this on purpose, as we don't want to create any confusion in the off chance that a schedule change is needed. We kindly ask that you please respect our request to keep this information inside the PDF copies preliminary, and do not serve up this data from any other locations/websites/services. Once the schedule is official, it will appear in all the API endpoints and webpages, at which point you can do what you wish. Thanks
Alex Herreid (FIRST) - 04/05/2018 4:08 PM GMT
Demo Teams Added
This is a notification that some "demo teams" have been added to the database. These teams, with team numbers 9985-9999 are not representative of real FIRST Robotics Competition teams, but rather, are used for off-season events to better support "pre-rookie" teams, testing and development, and other efforts. However, they still appear through the API, in match results, etc, as those teams may appear at events that list their results through the API.
If you have any questions, please feel free to pose them in the discussion.
Alex Herreid (FIRST) - 11/07/2016 10:08 PM GMT
API Version 2 Information and Updates
Hello community developers!

If you are interested in the Community Developers Project, and would like an authorization token for additional exploration, please "join" the project. Be sure to include details about yourself/your team/what your project is when you are submitting your request. During the off season, we will process requests once per month, near the end of each month. During the regular season, requests are processed about once per week, before each competition week. Tokens are removed if the account is inactive for over 6 months (0 requests), or has been banned for one month without contacting us. If your token disappears, just send us a message and we'll help you out.

Documentation for version 2 of the FRC Events API has been released. You can find the documentation in the same environment as it was originally, Apiary, at this address:

There have been significant changes in the second version. Please review the documentation carefully, and, for any applications or development going forward, use the most recent revision of the API. Pay close attention to the addresses for calling the various endpoints- as well as the notes regarding endpoints with multiple possible responses (i.e. score details and rankings). You can also check out the new stuff, like the "scores" endpoint, which will allow access to detailed scoring data for each match. Keep in mind that some of this data is subject to change, like the details of the scoring endpoint in relation to the 2016 game, which we won't be releasing documentation for until Kickoff.

If there are other changes which you wish to have considered for version 2 of the API, but do not exist in the preliminary documentation, please report them by clicking "Trackers" then "feature requests" here on TeamForge. We will continue to monitor the requests and make changes to the preliminary documentation as needed. You can test against this version of the API using the Apiary testing functionality, or the frc-staging-events server.

Please remember that v2.0 is not final until Kickoff- we will keep updating the versions that are available for testing, but additional changes may be made if we uncover any problems, or changes are needed for the new game. We will post here when v2.0 is final.

Happy coding,
The FMS Team
Alex Herreid (FIRST) - 12/09/2015 11:20 PM GMT
Project Statistics