University of Ottawa
The University of Ottawa (uOttawa / Universite d'Ottawa) is a public bilingual research university in Ottawa, Ontario, Canada, and the largest English-French bilingual university in the world. Its programmable footprint is small, undocumented, and almost entirely a by-product of the platforms it runs rather than anything it sells or supports: uOttawa publishes no developer portal, no API gateway, no OpenAPI, no llms.txt and no security.txt, and api.uottawa.ca and developer.uottawa.ca do not resolve. What it does operate itself, on its own hosts, is worth naming precisely. uO Research (Recherche uO Research) at ruor.uottawa.ca is a self-hosted DSpace 8.3 institutional repository exposing a public REST/HATEOAS API and an OAI-PMH 2.0 provider with fourteen metadata formats; www.uottawa.ca serves an undocumented but fully anonymous Drupal JSON:API surface advertising 287 resource types; and fca-caf.uottawa.ca runs the institution's own Shibboleth SAML 2.0 identity provider, registered in the Canadian Access Federation by CANARIE and interfederated through eduGAIN. Everything else that looks like a uOttawa API belongs to a vendor: the Omni library discovery layer is Ex Libris Primo VE via the OCUL consortium, the course catalogue at catalogue.uottawa.ca is Leepfrog CourseLeaf (CNAME uottawa-ca-public.courseleaf.com), and the research-data collection is a Borealis (Dataverse) tenancy. Those are recorded here as tenant relationships, never as uOttawa contracts. The institution is also a registrant in three identifier registries - DataCite (member UOTT, repository uott.library, prefix 10.20381), Crossref (members 7569 and 16151), and ROR (03c4mmv16) - which is a fact about uOttawa even though the registries' own APIs are not.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles University of Ottawa the way a machine reads it — 21 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — University of Ottawa scores 44.4/100 (developing), with a separate agent-readiness read of 30/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from University of Ottawa's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-ottawa/"
title="University of Ottawa on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-ottawa.svg"
alt="University of Ottawa Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-ottawa/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-ottawa/"
title="University of Ottawa on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-ottawa/card.svg"
alt="University of Ottawa Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile University of Ottawa
Each block below is one kind of artifact we hold for University of Ottawa. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
uO Research DSpace REST API
Public DSpace 8.3 REST/HATEOAS API for uO Research (Recherche uO Research), the University of Ottawa Library's self-hosted institutional repository. Probed 2026-09-01: the root ...
uO Research OAI-PMH
OAI-PMH 2.0 metadata-harvesting provider for uO Research. Probed 2026-09-01: Identify returns repositoryName "Recherche uO Research", repositoryIdentifier ruor.uottawa.ca, admin...
uottawa.ca Content JSON:API
Undocumented, anonymously readable JSON:API 1.0 surface on the University of Ottawa's own Drupal web platform. Probed 2026-09-01: https://www.uottawa.ca/jsonapi returns HTTP 200...
uOttawa Shibboleth Identity Provider (Canadian Access Federation)
The University of Ottawa's own SAML 2.0 identity provider and its published federation metadata. Probed 2026-09-01: https://fca-caf.uottawa.ca/idp/shibboleth returns HTTP 200 ap...
uOttawa Course Catalogue (CourseLeaf tenancy)
uOttawa's academic course catalogue, served on a uOttawa hostname but operated by Leepfrog Technologies: catalogue.uottawa.ca is a CNAME to uottawa-ca-public.courseleaf.com (12....
uOttawa Dataverse collection on Borealis
The University of Ottawa's research-data collection on Borealis, the Canadian Dataverse repository run by Scholars Portal / OCUL for CRKN. Probed 2026-09-01: GET https://boreali...
Omni library discovery (Ex Libris Primo VE tenancy)
uOttawa Library's discovery layer, Omni, is an Ex Libris Primo VE view delivered through the Ontario Council of University Libraries consortium at ocul-uo.primo.exlibrisgroup.co...
DataCite membership (UOTT)
The University of Ottawa is a DataCite member and DOI registrant. Probed 2026-09-01: GET https://api.datacite.org/providers/uott returns HTTP 200 with name "University of Ottawa...
Crossref membership (7569, 16151)
Two Crossref member records belong to the institution. Member 7569, "University of Ottawa Library", holds prefixes 10.18192 and 10.51224 with 3,860 DOIs (989 current, 2,871 back...
ROR registration (03c4mmv16)
The University of Ottawa is registered in the Research Organization Registry as https://ror.org/03c4mmv16, domain uottawa.ca, created 2018-11-14 and last modified 2026-07-20 in ...
Scroll within the panel for all 10 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
University Of Ottawa Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
University Of Ottawa Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
University of Ottawa API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
uO Research DSpace Community
JSON SCHEMAuottawa.ca JSON:API article resource
JSON SCHEMAExamples 2
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for University of Ottawa — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 2
Reference material describing how the API behaves
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/university-of-ottawa · machine-readable index on apis.io
This is an independent, third-party profile of University of Ottawa, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.