University of Alberta
The University of Alberta is a public research university in Edmonton, Alberta, Canada, and a member of the U15 Group of Canadian Research Universities. It operates no public API product. Its central developer site, api.ualberta.ca, is a live placeholder that says only that the university "is currently working to improve the way data is cataloged, shared, and governed" and gives an email address; there is no portal, no key issuance and no catalog behind it. The one machine-readable contract the institution itself publishes and runs is its SAML 2.0 identity provider metadata at login.ualberta.ca, which is institution-operated by definition and is the only surface in this profile whose operator is the university. Everything else that looks like a University of Alberta API is a tenancy on someone else's platform: ERA, the institutional repository, migrated off the library's own Jupiter application at era.library.ualberta.ca onto Scholaris, the OCUL/Scholars Portal national DSpace service, and now answers as ualberta.scholaris.ca with a DSpace REST API and an OAI-PMH endpoint; research data lives in the university's collection on Borealis, the Canadian Dataverse Repository run by the same consortium; the library catalogue is Ex Libris Alma and Primo VE, whose Z39.50 server the library documents in its own words; and its 90,338 DOIs are registered through DataCite. The course catalogue and Bear Tracks are HTML only — every JSON path probed on apps.ualberta.ca returns 404 or 410, which is why the third-party UAlberta course APIs that exist are HTML scrapers. The university's real engineering output is open source rather than hosted: the University of Alberta Library GitHub organization is active and substantial, and includes its own OAI-PMH implementation and DSpace and DataCite client tooling.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles University of Alberta the way a machine reads it — 10 machine-readable artifacts across 6 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 Alberta scores 29.3/100 (thin), with a separate agent-readiness read of 5/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Probed 2026-08-30. The University of Alberta publishes exactly one machine-readable contract it also operates: its SAML 2.0 identity provider metadata at login.ualberta.ca, which returns 200 application/samlmetadata+xml. There is no institution-operated REST API. api.ualberta.ca returns 200 but the body is a placeholder saying the university is still working out how data is cataloged, shared and governed, and offers only an email address; data.ualberta.ca serves the same byte-identical page. Every other apparent surface is a tenancy: ERA on Scholaris (OCUL DSpace), the research data collection on Borealis (Canadian Dataverse, a host five other institutions in this cohort also claim), the Alma Z39.50 server and Primo VE discovery layer from Ex Libris, and DOI registration through DataCite. The course catalogue is HTML only — apps.ualberta.ca returns 404 for /api and 410 for every .json path tried, so the third-party UAlberta course APIs in the wild are scrapers. The library's Open Journal Systems installation is gone: journals.library.ualberta.ca now 302s to a library publishing page, so there is no Crossref depositing surface either. Twenty files were removed from this repository in this pass — two Borealis-derived OpenAPI documents, the pristine original and its refine report, and the sixteen collections, schemas, structures, examples, rulesets, vocabulary, JSON-LD context, authentication and agentic-access artifacts derived from them. They described the Dataverse software's contract, not the university's.
This is an honest zero, not a gap in our research. University of Alberta does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://login.ualberta.ca/saml2/idp/metadata.php→ HTTP 200https://api.ualberta.ca/→ HTTP 200https://data.ualberta.ca/→ HTTP 200https://ualberta.scholaris.ca/server/api→ HTTP 200https://ualberta.scholaris.ca/server/oai/request?verb=Identify→ HTTP 200https://era.library.ualberta.ca/oai?verb=Identify→ HTTP 200https://borealisdata.ca/oai?verb=Identify→ HTTP 200https://borealisdata.ca/dataverse/ualberta→ HTTP 200https://www.ualberta.ca/en/library/research-support/open-data/z3950.html→ HTTP 200https://api.datacite.org/repositories?query=alberta→ HTTP 200https://apps.ualberta.ca/catalogue→ HTTP 200https://apps.ualberta.ca/api→ HTTP 404https://apps.ualberta.ca/catalogue/course/cmput.json→ HTTP 410https://journals.library.ualberta.ca/index.php/index/oai?verb=Identify→ HTTP 302https://library.ualberta.ca/peel/api→ HTTP 200https://login.ualberta.ca/idp/shibboleth→ HTTP 404
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 Alberta'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-alberta/"
title="University of Alberta on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-alberta.svg"
alt="University of Alberta Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-alberta/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-alberta/"
title="University of Alberta on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-alberta/card.svg"
alt="University of Alberta 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 Alberta
Each block below is one kind of artifact we hold for University of Alberta. 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 6
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.
University of Alberta SAML 2.0 Identity Provider Metadata
The university's own SAML 2.0 identity provider metadata document, served from its own domain. It declares entityID https://login.ualberta.ca/saml2/idp/metadata.php, an IDPSSODe...
ERA — Education and Research Archive (on Scholaris)
ERA is the University of Alberta's institutional repository. It was the library's own Samvera/Hyrax application, Jupiter, at era.library.ualberta.ca; that host now redirects to ...
University of Alberta Research Data Collection on Borealis
The University of Alberta's research data collection on Borealis, the Canadian Dataverse Repository operated by Scholars Portal / Ontario Council of University Libraries. The co...
University of Alberta Library Catalogue (Alma Z39.50 + Primo VE)
The library's discovery and catalogue layer is Ex Libris. The library publishes its own Z39.50 production server details on a ualberta.ca page — host ualberta.alma.exlibrisgroup...
University of Alberta Library DOI Registration (DataCite)
The University of Alberta Library is a registered DataCite repository — client id ualberta.library, symbol UALBERTA.LIBRARY, a member since 2020 — with 90,338 DOIs registered un...
University of Alberta Library Open Source (GitHub)
The University of Alberta Library's GitHub organization, ualbertalib, holds 138 public repositories and is actively maintained. Judged by what the code says about itself rather ...
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 Alberta 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.
Security Posture 1
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 Alberta — 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 4
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-alberta · machine-readable index on apis.io
This is an independent, third-party profile of University of Alberta, 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.