University of Waterloo Status API

Waterloo's public service status page at status.uwaterloo.ca, with the full Statuspage v2 JSON API behind it — status.json, summary.json and an RSS incident history all return 200 unauthenticated. The page and the incident data are Waterloo's; the platform and its API contract are Atlassian Statuspage's, shared by every Statuspage customer, so the contract is not saved under this slug. Real operational transparency, and the only machine-readable incident feed on the profile.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/university-of-waterloo-status-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: university-of-waterloo:university-of-waterloo-status-api
name: University of Waterloo Status API
description: Waterloo's public service status page at status.uwaterloo.ca, with the full Statuspage v2
  JSON API behind it — status.json, summary.json and an RSS incident history all return 200 unauthenticated.
  The page and the incident data are Waterloo's; the platform and its API contract are Atlassian Statuspage's,
  shared by every Statuspage customer, so the contract is not saved under this slug. Real operational
  transparency, and the only machine-readable incident feed on the profile.
humanURL: https://status.uwaterloo.ca/
baseURL: https://status.uwaterloo.ca/api/v2/
x-operator: tenant
x-operator-basis: 'Institution-specific subdomain on a vendor platform (Atlassian Statuspage). Probed
  2026-09-01: /api/v2/status.json and /api/v2/summary.json both 200 application/json, /history.rss 200
  application/rss+xml.'
x-contract-owner: Atlassian Statuspage
tags:
- Status
- Operational Transparency
- Incidents
properties:
- type: StatusPage
  url: https://status.uwaterloo.ca/
- type: APIReference
  url: https://status.uwaterloo.ca/api/v2/summary.json
- type: Documentation
  url: https://status.uwaterloo.ca/api/v2/