Release: rel1119
Name: Release Candidate (2015)
Description: Hello Community Developers,
We have exciting news for you today: the documentation for the 2015 version of the API is now available. You can find it online using the link below. As you will see on the top of the documentation, this version is our “Release Candidate”. We intend for this documentation to match how the API will behave in the production environment. However, if we (or you) uncover any bugs or issues with the API or its documentation during the coming days, we may still make minor updates. We will continue to monitor the TeamForge site, so please post there if you have a question, or notice anything within the documentation that you believe needs to be adjusted.

The documentation currently shows “version X.X” for the API. When we have leave the Release Candidate stage, the documentation and API will be updated to report “v1.0”. Once we have added the version number, the API and documentation are considered final and you will know you are coding against a known request and response pattern. We anticipate the release of version 1.0 (and having the production server available to take requests) around the beginning of February. If you have matched the documentation and used our “Mock Server” to test your products, it should be a relatively simple transition come the end of the month.

In the future, we will increment the version number and publish new documentation with new features as they become available. Please take note of how to include the version number in your API calls- the production server will require you to add “v1.0” (or whichever version number) when you make requests or else it won’t return anything. Additionally, the URL (“Mock Server”) on the right side bar of Apiary allows you to test your code against the current API documentation. That data it returns is just hard-coded though, so there is no validation of the parameters and you won’t receive “dynamic” data in return. This is expected, and not a “bug”, it is just a testing tool for you to use if you wish.

If you are not familiar with Apiary, it is the tool that we use to power our documentation and demos. You can take a look at rel1117 under “Preliminary Documentation” for details about Apiary and how it works.

http://docs.frcevents.apiary.io/

As always, please use our TeamForge site to enter any bugs or comments you may have. We also encourage the use of discussion area to coordinate projects or ask questions of other community developers.

Happy coding!
-The FMS Team
Status: Active
Maturity: Pre-General Availability
Related Planning Folders:

Files Change Log Reported Tracker Artifacts Fixed Tracker Artifacts Planned Tracker Artifacts Associations  
Configure number of rows100 RowsDrop Down
 (8 Items)
PrioritySortArtifact ID : Title3Sort DownAssigned ToSortTeam2Sort UpCreated BySortStatusSortCategory1Sort UpTrackerSort 
Transparent decoration   artf3996 : Discrepancy of teamNumber parameter in Event AwardsNoneIsiah Lloyd(deleted)ClosedFRC Event API Bugs
Transparent decoration   artf4008 : Need Match DetailNoneTom Saxton(deleted)ClosedFRC Event API Bugs
Transparent decoration   artf4009 : Response Code 429 "too many requests" UndocumentedNoneTom Saxton(deleted)ClosedFRC Event API Bugs
Transparent decoration   artf4019 : Team listing, add ability to query for changes since last n days.Alex Herreid (FIRST)Kerry DenHerder(deleted)ClosedFRC Event API Feature Requests
Transparent decoration   artf4034 : Red Carded Alliance Not IndicatedAlex Herreid (FIRST)Eugene Fang (The Blue Alliance)(disabled)ClosedFRC Event API Bugs
Transparent decoration   artf4037 : DQ matches not identifiedNoneBen Ng(deleted)ClosedFRC Event API Bugs
Transparent decoration   artf4052 : Add information to Schedule data that would make it easy to detect changes.Alex Herreid (FIRST)Kerry DenHerder(deleted)ClosedFRC Event API Feature Requests
Transparent decoration   artf4060 : Include Team Website in Team DetailsAlex Herreid (FIRST)Phil Lopreiato (The Blue Alliance)ClosedFRC Event API Feature Requests