• There was an issue with the data integration that caused the 1215 (Spring 2021) term associated data to not be available. This has been corrected as of now, and go forward. 


  • The API now runs as a .NET 5 application, and benefits from all the improvements, including performance. 


  • There was an issue on the Courses endpoint with routing correctly with Term, CourseID, and Subject parameters when the subject was exactly 6 characters long. This has been corrected, and the endpoints will now route and return data correctly. Previously they would return an error. 


  • We've added additional filters to the WCMS content (news, events, blogs, opportunities) per site endpoints to allow you to limit results and get latest items first. 
  • We've added some missing indexes in the database for the WCMS content items that should improve the data return performance. 
  • In some cases the Body and Description fields for WCMS endpoints news, events, blog posts, and opportunities would return null values even if the source had content. This has now been resolved. 


  • Addition of Food Services specific information from WCMS. We've added endpoints to give Franchise, Outlet, and related information to the API under the v3/FoodServices endpoint. There is some missing documentation, the endpoint functions as a caching proxy to the source data. We do not modify the schema which represents the data in WCMS, and provide it as is. See the live API documentation for more detail. 

This announcement is for the endpoints off of and what is referred to as the v2 Open Data API. 

We are planning the follow, which will have an impact on access and use of the API. 

Key Dates for Actions

Monday, January 25th, 2021 - the V2 endpoints will be disabled, potentially returning a message about their imminent deprecation. 

Friday, January 29th, 2021 - the V2 endpoints will be enabled again to operate as they are today. We may bring the endpoints back up earlier than this to facilitate critical use cases. 

Friday, February, 26th or earlier - usage dependent the V2 endpoints will be turned off permanently. They may be disabled earlier if no critical use case remains, but will not be enabled past the February 26th cutoff date. 


As we've announced, and as we're asked to retire the underlying servers the V2 API needs to be shutdown. We've made the main data points, based on use, available in the V3 API. You can see documentation, and getting started with V3. 

It's an ongoing challenge to contact the users of V2 API keys. In many cases the email registered is no longer the person using the key, or there is little interest to make changes to the application or tool using the key. 

The temporary shutdown will help to bring users that want to continue to use the data to action, and allow us to help them migrate where necessary. 


If you have questions or issues please us the GitHub issue tracker or the IST-Opendata RT queue


  • We've added a "Holiday Dates" endpoint. It currently has method and data for paid holidays at the University of Waterloo as managed by HR. There is an ICS format of the endpoint that requires no 


  • In the background we've updated some of the packages, nut, and bolts that power the API stack.


  • We've added the WCMS content endpoint in preview. Effectively we believe that this is what it will look like on full release, and are looking for feedback. We may add additional fields, and some of the data content may change, but we don't except we'll remove or significantly alter the existing schema. 


  • As we come to the end of the year, thank you for providing feedback and suggestions using the GitHub issue tracker. We look forward to enabling you with more data, and wish you a joyful holiday season! 
  • In the background we've updated some of the packages, nut, and bolts that  power the API stack. 

We've made just one change in this release, but we think it's important. 


  • We've enabled CORS (, with the following policy ("GET" from any Origin, with any headers, disallow credentials) for all endpoints with one exception. CORS will be enabled for all public Open Data v3 API endpoints going forward. 
  • The exception endpoint is "Account" endpoint. This endpoint does not have CORS enabled. 


The next immediate priorities are additional query options for the important dates endpoint, and content from the WCMS ( system. This will include sites, news, events, blogs, and opportunities. 

As always, if you encounter any issues, or have a question please use our GitHub repository to open an issue

We're making minor changes, additions, and fixes in this release of the v3 of Open Data API. 


  • Course endpoint will now return requisite (pre, anti, co) information description as part of the response (requirementsDescription). See
  • Course endpoint will now return enrollment and drop consent code and description (enrollConsentCode, enrollConsentDescription, dropConsentCode, dropConsentDescription). 
  • Class endpoint will now return enrollment and drop consent code and description (enrollConsentCode, enrollConsentDescription, dropConsentCode, dropConsentDescription). 


  • The GeoJSON Buildings endpoint was returning the latitude and longitude coordinates reversed. See
  • In the Course and Class endpoints the 'catalogNumber' property would have an extra space before the correct value. 


There was a longer than expected interruption during the update, as there was an issue with the runtime on the server. 

As always, if you encounter any issues, or have a question please use our GitHub repository to open an issue

We've been away for some time. We tried to make some changes during that time, like moving the announcements, and news about the API, and open data to GitHub for public access. Progress has been minimal, and we'd like to take a moment to explain where things are, immediate changes, and near future ones coming up. 

Why has there been little progress? 

After taking over the Open Data initiative, and the API, there were priority and staffing changes that meant a significant loss of time assigned to the Open Data initiative. As the strategic priorities of the University and the technical group were defined and changed, we had to evaluate where we spent limited resources. While Open Data is an important asset, and supports initiatives by staff, students, and our community, there was no immediate need to make progress while v2 of the API was operational. 

What will happen with the existing legacy v2 Open Data API?

It has remained in a legacy, critical support only state for most of 2019, and through 2020. At this stage it is on hardware, and software that is going out of support by the end of the year, and must be retired. As such, it will remain operational until the end of 2020, and be shutdown as soon as reasonably possible after that date. The v2 of the API has had tremendous success with getting data out to the community, and helping to develop some amazing projects, and solve data problems. We hope to build on that with more accurate, high quality data, going forward. 

What is the status of the v3 Open Data API?

We released what we called a technical preview, and it has been live and in use by a limited amount of clients for over a year. We've now published a significant set of changes to the API endpoints, and the endpoint schemas. While we recognize this is a breaking change, based on the usage, and the changes needed to support getting the information into the API this was necessary. We'll be posting more details going forward, the biggest changes and the reasoning behind them are the following: 

  1. On the academic data side (Quest); we removed any reference to effective dating of data. We'll be providing only the snapshot of data that is true "today". Having the flexibility to see the data as it was true in the past added complexity in exposing it, and had a significant educational component to make sure data was appropriately used by the clients and downstream systems. 
  2. For academic data, and with other data as possible, we will be aiming for a range of near real time to sub-2 hour refreshes for the current, past, and next term. In all other cases data should be considered archived.
  3. There will be a significant decrease in initial endpoints available, as no authoritative data steward or system exists.

What is the status of "Crowd" data API? 

We originally planned to have the data sources we could not find a data steward for, or the data was community curated offered through a "Crowd" API. This plan is indefinitely on hold at this time. 

What changes will we be making before the end of the year? 

We'll be updating the documentation across our sites (,, releasing more updates for v3 of the API, and turning off v2. 

Where do I leave comments and feedback? 

The easiest place to voice your questions, comments, and opinions is by filing an issue on our GitHub page ( If you wish for your communication to be less public, please open a request ticket through RT ( for the IST-Opendata queue. 

Important Dates endpoint

There have been significant changes to the important dates data at the University of Waterloo. The underlying model for it is changing in the WCMS system where it comes from. The good news is this means that the concept of important dates will expand to more areas!

The new data is available in the new version of the Open Data API. The end point is and you can find additional information and documentation here

At this time we will not be back porting the data into the existing v2 version of the API. This means that new dates and changes will only be reflected in v3 and you should update any use appropriately.

We're happy to make available a preview version of the Open Data API. As it stands, it has a few bare bones data sets available. We're primarily looking for feedback on the format, documentation, and the registration experience.

As a reminder, this data comes directly from the underlying authoritative systems and we're committed to it's accuracy.

Once we feel we have sufficient feedback on the registration process and the getting started guides and live documentation we will add additional data sets. The focus will be on replacing the course information, course scheduling, and those academic data sets that were by far the highest use cases on the current API version.

Please take a moment to check out the Getting Started - OpenAPI page, and try it out. We'd love if you could report your feedback on our public GitHub project page.

Thank you, and we're excited to bring future improvements (smile)

Welcome and vNext Update

It's been some time since we announced that there would be a transition period for the Open Data project. We're back to give another update and put something usable in your hands for feedback.

Open Data vNext in Technical Preview

Note: we currently do not have the email confirmation setup, expect this shortly and we'll update this post then.

The Open Data API is available in technical preview. We're borrowing the term, and what this means for us is that we are reasonably sure this is what the data will look like in terms of endpoints and model schema, but are open to feedback and can still introduce breaking changes. The API is available at and the relevant documentation (using Swagger) is available at

Please see the Getting Started page.

For providing feedback please email or post an issue on the original Open Data GitHub page

We'll continue to iterate on changes based on any feedback and add a few more popular data sets before we proceed to the next phase.

Source API Updates

We've added improvements and new data features over the last 3 months. We will continue to add authenticated and private data end points as client needs arise and we can secure partnerships with authoritative sources for the requested data. Some of the recent data additions include service indicators, milestone information, Watcard photo data, and revisions due to the Watiam upgrade.

You can see the changes we've made reflected here.