Victoria University of Wellington
Te Herenga Waka—Victoria University of Wellington is a public research university in Wellington, Aotearoa New Zealand, and it operates almost no programmable surface of its own. It publishes no developer portal, no API documentation, no API keys, no status page and no changelog. What it has instead is what most universities have: a federation of vendor platforms bought under its own name, and four surfaces it genuinely runs itself. The four are a self-hosted DSpace 7.6.7 institutional repository at ir.wgtn.ac.nz — no CNAME, its own address space, 23,150 records harvestable over its own keyless OAI-PMH 2.0 base URL in twelve metadata formats, with an anonymously readable DSpace REST root, an OpenSearch 1.1 description and FAIR Signposting link sets alongside it; an undocumented but public, keyless JSON configuration endpoint on its own website (www.wgtn.ac.nz/api/globalobject, HTTP 200, CORS open to all origins); a self-hosted WSO2 Identity Server at auth-eis.vuw.ac.nz that issues SAML for the student-records system and whose every discovery endpoint answers HTTP 403 behind a web application firewall — live and protected, not missing; and a SAML 2.0 Shibboleth Identity Provider at idp.vuw.ac.nz, entityID https://idp.vuw.ac.nz/idp/shibboleth, scope vuw.ac.nz, registered in the Tuakiri New Zealand Access Federation since 2012 with the REFEDS Research & Scholarship entity category and a REFEDS Sirtfi assurance certification. The repository and the identity federation entry are the institution's most durable and most genuinely machine-readable assets, and both are classes of interface a university operates by definition rather than by purchase. Everything else programmable that carries the university's name is a tenancy: the Open Access research repository is a SECOND, Figshare-hosted repository on the institution's own openaccess.wgtn.ac.nz vanity domain (OAI-PMH set portal_771, DataCite repository FIGSHARE.VUW, 4,301 DOIs) — the university runs two repositories, one its own and one bought; Te Waharoa library discovery is an Ex Libris Primo/Alma deployment on tewaharoa.victoria.ac.nz whose SRU 1.2 endpoint is anonymously callable and returns MARCXML; Nuku is an Instructure Canvas tenant; the research information system is Symplectic Elements; and browser sign-on for student services federates to a Microsoft Entra ID tenant. The data in those systems is the university's. The contracts are not, and none of them are saved here. A previous profile of this institution attributed Figshare's generic v2 REST API to it as though the university had written it; that contract and the sixteen artifacts derived from it have been removed. The institution also runs three public GitHub organisations, of which only VUW Research Computing — documenting the Rāpoi HPC cluster — is currently active, and it publishes a 12,160-URL machine-readable course sitemap covering every course-year page. The registrar surface, where student-built course APIs appear at peer institutions, is a self-hosted Ellucian Banner Self-Service behind SAML with no public interface at all.
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 Victoria University of Wellington 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 — Victoria University of Wellington scores 36.1/100 (thin), with a separate agent-readiness read of 21/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 Victoria University of Wellington'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/victoria-university-of-wellington/"
title="Victoria University of Wellington on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/victoria-university-of-wellington.svg"
alt="Victoria University of Wellington Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/victoria-university-of-wellington/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/victoria-university-of-wellington/"
title="Victoria University of Wellington on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/victoria-university-of-wellington/card.svg"
alt="Victoria University of Wellington 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 Victoria University of Wellington
Each block below is one kind of artifact we hold for Victoria University of Wellington. 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.
Website Global Object
A public, keyless JSON endpoint served by the university's own website CMS at www.wgtn.ac.nz/api/globalobject. It returns the global site object every page is built from: canoni...
Shibboleth Identity Provider (Tuakiri / eduGAIN)
The university's own SAML 2.0 Identity Provider. entityID https://idp.vuw.ac.nz/idp/shibboleth, shibmd:Scope vuw.ac.nz, metadata served unauthenticated over HTTPS GET and republ...
Institutional Repository (self-hosted DSpace)
The university's institutional repository, ir.wgtn.ac.nz, running DSpace 7.6.7 on the institution's OWN infrastructure: the host sits under its own registrable domain, carries n...
Open Access Repository (Figshare tenancy)
The university's Open Access institutional repository is a Figshare portal running on the institution's own vanity domain openaccess.wgtn.ac.nz, which CNAMEs to figshare.com, wi...
Te Waharoa Library Discovery (Ex Libris Primo / Alma tenancy)
Te Waharoa is the library's discovery service, running on Ex Libris Primo backed by Alma on the institution's own subdomain tewaharoa.victoria.ac.nz, which CNAMEs to victoria.pr...
Nuku Learning Management (Instructure Canvas tenancy)
Nuku is the university's brand for its learning-management system, an Instructure Canvas tenant at nuku.wgtn.ac.nz, which CNAMEs to wgtn-vanity.instructure.com. The Canvas REST ...
Research Information System (Symplectic Elements tenancy)
The university's research information system is Symplectic Elements at elements.wgtn.ac.nz, which CNAMEs to vuw.elements.symplectic.org. HTTP 401 to an anonymous request on 2026...
Enterprise Single Sign-On (WSO2 Identity Server)
The university self-hosts a WSO2 Identity Server at auth-eis.vuw.ac.nz — no CNAME, resolving directly to 130.195.13.55 inside the institution's own address space — and it is the...
Student Records (Ellucian Banner Self-Service tenancy)
The registrar and student-records system at studentrecords.vuw.ac.nz. The sign-on RelayState /c/auth/SSB identifies it as Ellucian Banner Self-Service, and the host resolves dir...
Microsoft Entra ID Tenant (production browser sign-on)
Production browser single sign-on for the university's student-facing services federates to a Microsoft Entra ID tenant, cfe63e23-6951-427e-8683-bb84dcf1d20c, observed on the Nu...
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.
FinOps 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.
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.
JSON Schema 1
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.
Te Herenga Waka Website Global Object
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Victoria University of Wellington — 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 1
Reference material describing how the API behaves
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 2
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 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/victoria-university-of-wellington · machine-readable index on apis.io
This is an independent, third-party profile of Victoria University of Wellington, 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.