University of New South Wales
The University of New South Wales (UNSW Sydney) is a public research university in Sydney, Australia, and a member of the Group of Eight. Like almost every institution, UNSW is a federation of buyers rather than an API producer, and its programmable footprint has to be read that way. The one substantial platform UNSW runs itself — the Enterprise API Gateway and Developer Portal on Microsoft Azure API Management at apideveloper.unsw.edu.au — is completely gated: onboarding is request-based, the API catalogue is invisible before sign-in, no base URL is disclosed, and the portal states outright that consumers cannot exercise APIs in the portal. The surfaces a member of the public can actually read are three, and all three are institution- operated: the UNSWorks institutional repository REST API (DSpace 7.0, anonymous discovery search, authenticated item browse), its OAI-PMH 2.0 harvesting endpoint exposing twelve metadata formats back to 2007, and the UNSW Shibboleth identity provider whose SAML 2.0 entity metadata is published under the institution's own domain and registered in the Australian Access Federation. Everything else is a tenancy on someone else's platform — an Ex Libris Primo library discovery view, a vendor-hosted Moodle that is a conformant LTI 1.3 platform, a Microsoft Power Apps research-data toolkit — or student-society work on non-institution domains. UNSW publishes no OpenAPI, no open data portal, no status page, no changelog and no API governance ruleset.
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 New South Wales the way a machine reads it — 22 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 New South Wales scores 52.6/100 (developing), with a separate agent-readiness read of 33/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.
Why this profile is thin
UNSW's one substantial institution-operated API platform — the Enterprise API Gateway behind apideveloper.unsw.edu.au — cannot be read without authorisation, and authorisation is granted only through a manual request process that can require a data sharing agreement or a manager's approval. The catalogue path returns 404 unauthenticated, no gateway base URL is published anywhere on the portal, and the portal itself states that even authorised consumers cannot exercise APIs from within it. So the count, shape, versioning and lifecycle of UNSW's enterprise APIs are unknowable from outside, and this profile asserts nothing about them. What could be read was read completely: the UNSWorks DSpace REST API, its OAI-PMH endpoint and the UNSW Shibboleth IdP metadata were all probed live and are fully covered. Nothing here was blocked by bot protection, and the thinness of this profile is a fact about UNSW's publishing posture, not a gap in the sweep. UNSW operates no open data portal (data.unsw.edu.au redirects to an information-governance page), publishes no OpenAPI, no status page, no changelog and no security.txt, and its research-data toolkit sits behind a Microsoft tenant login.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is University of New South Wales's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://apideveloper.unsw.edu.au/→ HTTP 200https://apideveloper.unsw.edu.au/getting-started→ HTTP 200https://apideveloper.unsw.edu.au/apis→ HTTP 404https://apideveloper.unsw.edu.au/signin→ HTTP 200https://unsworks.unsw.edu.au/server/api→ HTTP 200https://unsworks.unsw.edu.au/server/api/discover/search/objects?size=1→ HTTP 200https://unsworks.unsw.edu.au/server/api/core/items?size=1→ HTTP 401https://unsworks.unsw.edu.au/oai/request?verb=Identify→ HTTP 200https://unsworks.unsw.edu.au/oai/request?verb=ListMetadataFormats→ HTTP 200https://aaf.unsw.edu.au/idp/shibboleth→ HTTP 200https://md.aaf.edu.au/aaf-metadata.xml→ HTTP 200https://moodle.telt.unsw.edu.au/mod/lti/certs.php→ HTTP 200https://freerooms.devsoc.app/api/buildings→ HTTP 200https://api.unsw.edu.au/→ HTTP 502https://data.unsw.edu.au/→ HTTP 200https://www.unsw.edu.au/llms.txt→ HTTP 404https://www.unsw.edu.au/.well-known/security.txt→ HTTP 404https://resdata.unsw.edu.au/→ HTTP 0
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 New South Wales'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/unsw-sydney/"
title="University of New South Wales on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/unsw-sydney.svg"
alt="University of New South Wales Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/unsw-sydney/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/unsw-sydney/"
title="University of New South Wales on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/unsw-sydney/card.svg"
alt="University of New South Wales 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 New South Wales
Each block below is one kind of artifact we hold for University of New South Wales. 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 11
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.
UNSW Shibboleth Identity Provider (AAF / eduGAIN)
UNSW's own SAML 2.0 identity provider — a Shibboleth IdP whose entity metadata is published as a machine-readable XML document at the entityID URL and is carried in the AAF fede...
UNSW Enterprise Developer Portal
The front door to UNSW's Enterprise API Gateway, built on Microsoft Azure API Management. Cataloguing it is a statement about the gate, not about the APIs behind it: /apis retur...
Moodle @ UNSW (TELT) — LTI 1.3 platform
UNSW's learning management system, operated for UNSW by Open LMS. It is a live, conformant 1EdTech LTI 1.3 platform: the public keyset at /mod/lti/certs.php serves RS256 JWKs, t...
UNSW Library discovery (Ex Libris Primo VE)
UNSW Library's discovery layer runs on Ex Libris Primo VE. This entry records the tenancy so the relationship is visible in the catalogue; no Ex Libris specification is saved un...
Freerooms API (DevSoc, community)
A live student-society API exposing UNSW campus buildings and teaching rooms with coordinates, capacity, school and usage type — the campus-life surface class, built by students...
UNSW Timetable API (DevSoc, community) — ARCHIVED
A scraper and public API for UNSW's timetable site, produced by the UNSW Software Development Society. ARCHIVED BY ITS OWNER ON 2026-04-05 and now read-only. The June 2026 profi...
UNSW Handbook API (CSESoc, community) — ARCHIVED
A public API for fetching degree, specialisation and course information from the UNSW Handbook, published by the UNSW Computer Science and Engineering Society. ARCHIVED BY ITS O...
University of New South Wales Core API
Communities, collections, sites and the metadata registry.
University of New South Wales Discover API
Public discovery search over repository objects.
University of New South Wales Oai Pmh API
OAI-PMH 2.0 verbs, all exercised live against this endpoint.
University of New South Wales Root API
Service entry point and HAL link index.
Scroll within the panel for all 11 ·
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.
Unsw Sydney 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.
Unsw Sydney Finops
FINOPSSemantic 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.
Unsw Sydney 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.
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.
UNSWorks Repository DSpace 7.0 REST payloads
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 University of New South Wales — 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 4
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 3
Authentication, authorization, and security posture
Learn 1
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 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/unsw-sydney · machine-readable index on apis.io
This is an independent, third-party profile of University of New South Wales, 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.