University of Auckland
Waipapa Taumata Rau | The University of Auckland is New Zealand's largest and highest-ranked university. Unlike most of this cohort it genuinely operates an API programme of its own: a Kong gateway at apis.auckland.ac.nz fronted by a public developer portal at developer.auckland.ac.nz, which publishes two OpenAPI 3.1.0 contracts — Course Catalog Api V3 and Classes Api V2 — over its PeopleSoft Campus Solutions (CS9) student records, plus guides for registering an application client and calling with the client-credentials flow. Both routes are live and return HTTP 401 without a key, so the contracts are public while the data is registered-developer only. The University also self-hosts ResearchSpace (DSpace) on its own domain with a live OAI-PMH 2.0 service advertising thirteen metadata formats, and runs its own Shibboleth identity provider at iam.auckland.ac.nz publishing SAML 2.0 metadata scoped to auckland.ac.nz. Its research data repository (auckland.figshare.com) and library discovery layer (Ex Libris Primo) are vendor tenancies: the data and the DOIs are the University's, the contracts are not, and no vendor specification is saved under this slug. The previously catalogued unidirectory.auckland.ac.nz staff directory API no longer resolves in DNS and has been removed. There is no open data portal and no llms.txt, security.txt, status page, changelog or deprecation policy on any institution host.
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 Auckland the way a machine reads it — 17 machine-readable artifacts across 2 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 Auckland scores 46.1/100 (developing), with a separate agent-readiness read of 25/100 (agent aware). 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 Auckland'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-auckland/"
title="University of Auckland on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-auckland.svg"
alt="University of Auckland Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-auckland/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-auckland/"
title="University of Auckland on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-auckland/card.svg"
alt="University of Auckland 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 Auckland
Each block below is one kind of artifact we hold for University of Auckland. 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 7
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 Auckland Course Catalog Api V3
Read-only access to the University of Auckland course catalogue, described by the University as "Exposes some course information by querying CS9 views" — CS9 being its PeopleSof...
University of Auckland Classes Api V2
Search for scheduled class offerings at the University of Auckland — "Class API is intended to provide access to Class attributes, such as ID, Name, Description, Definition etc"...
ResearchSpace OAI-PMH 2.0 Service
Live OAI-PMH 2.0 metadata harvesting endpoint for ResearchSpace, the University's self-hosted DSpace institutional repository. Verified 2026-08-30 - Identify returns protocolVer...
ResearchSpace DSpace REST API
The HAL+JSON REST API of the University's self-hosted DSpace 7 instance. /server/api/core/communities returns the live community tree (A1 Research Outputs Online and its sibling...
University of Auckland Shibboleth Identity Provider (SAML 2.0 metadata)
The University's institutional identity provider, publishing SAML 2.0 metadata at https://iam.auckland.ac.nz/shibboleth (200, application/xml). The IDPSSODescriptor declares sup...
University of Auckland Figshare Research Data Repository (tenant)
The University of Auckland's Figshare research data repository, a vendor tenancy on the Figshare platform (institution id 12). Live - the landing page returns HTTP 202 behind an...
University of Auckland Library Discovery (Ex Libris Primo tenant)
The University of Auckland Library's discovery layer, an Ex Libris Primo VE tenancy (vid=64UAUCK_INST:UOA, HTTP 200 verified 2026-08-30). No institution-published catalogue API ...
Scroll within the panel for all 7 ·
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 Auckland 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.
Spectral 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 Auckland API Rules
SPECTRALJSON Schema 3
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.
University of Auckland ClassModel
JSON SCHEMAUniversity of Auckland Course
JSON SCHEMAUniversity of Auckland Term
JSON SCHEMAExamples 1
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 Auckland — 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 7
Reference material describing how the API behaves
Scroll within the panel for all 7 ·
Design & Contract 5
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 2
The organization behind the API
Other 8
Properties that don't map to a standard resource type
Scroll within the panel for all 8 ·
← All providers · Data indexed from github.com/api-evangelist/university-of-auckland · machine-readable index on apis.io
This is an independent, third-party profile of University of Auckland, 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.