University of Waterloo · Rate Limits

University Of Waterloo Rate Limits

The University of Waterloo publishes an explicit numeric rate limit for its Open Data API v3: 120 requests per minute, introduced in January 2026 alongside reopened self-serve key registration and response caching on semi-static endpoints. Waterloo states the limit and the algorithm may be adjusted. No limit is published for the gated SourceAPI, whose throughput is negotiated per data set with the responsible data steward. The UWSpace DSpace REST and OAI-PMH endpoints publish no limit; harvest politely.

University Of Waterloo Rate Limits is the machine-readable rate-limit profile for University of Waterloo on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests-per-minute.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Education, Higher Education, University, and Rate Limiting.

3 Limits Throttle: 429
EducationHigher EducationUniversityRate Limiting

Limits

Open Data API v3 api-key
requests-per-minute · minute
120
Published by the provider on 2026-01-23. Applies to keys issued through POST /v3/Account/Register. Waterloo reserves the right to adjust the limit and the algorithm, and to revoke keys with notice.
SourceAPI client
requests-per-minute
not published
Access is granted per data set through Jira Service Desk portal 115 in collaboration with data stewards; throughput is governed by that agreement and by University of Waterloo Policy 46 — Information Management, not by a published table.
UWSpace (DSpace REST + OAI-PMH) client
requests-per-minute
not published
No limit published on dspacemainprd01.lib.uwaterloo.ca. The UWSpace front end declares a server-side UI rate limiter of 500 requests per 60s window in its own runtime configuration; that governs the Angular front end, not the REST or OAI-PMH surfaces.

Policies

Caching
Waterloo added server-side caching to several semi-static Open Data endpoints in January 2026 to mitigate operational performance and cost; prefer cached reads over polling.
Backoff Strategy
Exponential backoff with jitter; honor Retry-After if returned; harvest during off-peak hours.

Sources

Work with this as data

Every rate limit 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 rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • 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 rate limit 
curl "https://apis.io/api/v1/rate-limits/university-of-waterloo-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?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.

GitHub Google LinkedIn

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