Welcome to the FRC-API-for-Google-Sheets wiki!

Using the API to augment scouting

At the end of Qualification Matches, FIRST Robotics Competition teams are tasked with forming alliances to play in the playoff matches. Alliance Captains will want to enter the alliance selection with a "pick list" or list of teams they are interested in partnering with. These teams should complement the captain team's strategy and be the best overall fit.

Items which may help create a pick list

• Scout matches at the event, collecting data and writing notes on competing teams
• Scout teams by visiting them in the pits, asking questions and collecting their responses
• Use official rankings provided by FIRST
• Use metrics calculated by third parties such as Offensive Power Ranking (OPR) from The Blue Alliance or Expected Points Added (EPA) from Statbotics
• Use the FRC Events API for empirical data
  • This guide will focus on using the FRC Events API

Advantages to using the API

• The API provides official, accurate, numerical data from match play
• Certain data points are available on a per-robot basis (in most games, there is an AUTONOMOUS and ENDGAME data point available per team, but this varies year-to-year)
• API data is easily accessible (see this guide!) and free to access

Disadvantages to using the API

• Certain game elements are not tracked on a per-robot basis (in most games, this is individual game pieces scored)
• The API cannot provide qualitative notes on a team's robot design, match strategy, or efficacy
• Internet is required to access API data, which may not be available to all teams at all events.

When to use the API

An effective scouting program will collect data through multiple methods to make the most informed picking decisions. It is very possible to build an effective scouting program without using the API, and using the API as a standalone method will likely not yield the best picks.

• Teams may lean on the API more heavily if they have fewer students to watch matches.
• Teams may use the API to reduce the number of data points students have to collect (e.g. if the API tracks climbing, students may not have to manually record this).
• Teams may use the API to check the work of their scouts - checking for consistency between scout-collected and API-collected data.

Additional considerations

• Does your team have the resources to watch every team in every match?
• Determine what data points you're looking for before deciding if using the API is right for you.
• How will you collect data from the API, and once collected, how will you interpret it?

Additional reading

• Introduction to Scouting guide
• Intermediate Scouting guide
• Official API Demo Tool