La Trobe University
La Trobe University is a public research university headquartered in Bundoora, Melbourne, Victoria, Australia, founded in 1964 and ranked #217 in the QS World University Rankings 2025. La Trobe operates no public, self-service API product and publishes no OpenAPI, AsyncAPI or GraphQL description of its own. Its single institution-operated API host, api.latrobe.edu.au, is an Azure API Management developer portal (CNAME ltu-api-prod-apim.developer.azure-api.net) that redirects every unauthenticated path to /signin, with no public catalogue, documentation or sign-up. Everything else that looks programmable under the La Trobe name is a vendor platform running under an institutional tenancy: the open-access repository OPAL (opal.latrobe.edu.au, CNAME figshare.com) and its alias researchdata.latrobe.edu.au are Figshare; the course handbook (handbook.latrobe.edu.au) is CourseLoop, whose backend at cf-api-ap-southeast-2.prod.courseloop.com refuses unauthenticated calls; library discovery and resource management are Ex Libris Primo and Alma; the Shibboleth identity provider at aaf.latrobe.edu.au is operated by the Australian Access Federation under La Trobe's own domain, entityID and scope. What La Trobe genuinely holds in its own name is registry identity — a DataCite membership with the DOI prefix 10.26181 over 47,824 DOIs, Crossref member 11371, ROR 01rxfrp27, and the AAF/eduGAIN SAML entity that federates its staff and students. That is the honest footprint: institutional identity and stewardship, not institutional engineering.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles La Trobe University the way a machine reads it — 8 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 — La Trobe University scores 19.6/100 (emerging), 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
La Trobe University publishes no institution-authored API contract. The one API host on its own registrable domain, api.latrobe.edu.au, is an Azure API Management developer portal whose every path — /apis, /developer, /.well-known/openid-configuration — redirects to /signin, so the catalogue behind it is not externally observable. developer.latrobe.edu.au and data.latrobe.edu.au do not resolve. There is no CKAN or Socrata open-data portal and no institution-hosted OAI-PMH responder (opal.latrobe.edu.au/oai answers HTTP 202 with an empty body). The remaining machine-readable surfaces are tenancies — Figshare, CourseLoop, Ex Libris and an AAF-managed Shibboleth IdP — and are recorded as such, with x-operator on each entry, rather than credited to La Trobe as its own engineering. A secondary condition worth noting for future runs: every www/library/policy page on latrobe.edu.au sits behind a Cloudflare managed challenge and answers 403 to any non-browser client, including /robots.txt, /llms.txt and /.well-known/security.txt, so no institutional policy or terms pointer could be verified and none is claimed here.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is La Trobe University'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://api.latrobe.edu.au/→ HTTP 200https://api.latrobe.edu.au/apis→ HTTP 200https://developer.latrobe.edu.au/→ HTTP 0https://data.latrobe.edu.au/→ HTTP 0https://opal.latrobe.edu.au/oai?verb=Identify→ HTTP 202https://aaf.latrobe.edu.au/idp/shibboleth→ HTTP 200https://handbook.latrobe.edu.au/→ HTTP 200https://cf-api-ap-southeast-2.prod.courseloop.com/publisher/search-all?siteId=ltu-prod-pres→ HTTP 403https://www.latrobe.edu.au/→ HTTP 403https://www.latrobe.edu.au/llms.txt→ HTTP 403https://www.latrobe.edu.au/.well-known/security.txt→ HTTP 403
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 La Trobe University'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/la-trobe-university/"
title="La Trobe University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/la-trobe-university.svg"
alt="La Trobe University Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/la-trobe-university/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/la-trobe-university/"
title="La Trobe University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/la-trobe-university/card.svg"
alt="La Trobe University 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 La Trobe University
Each block below is one kind of artifact we hold for La Trobe University. 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 3
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.
La Trobe API Gateway (Gated)
La Trobe's own API gateway, an Azure API Management instance published at api.latrobe.edu.au (CNAME ltu-api-prod-apim.developer.azure-api.net). It is not a public developer prod...
OPAL (Open @ La Trobe) Research Repository
OPAL is La Trobe's open-access research repository — its publications, theses, datasets and DOIs — deployed as an institutional tenancy on Figshare. opal.latrobe.edu.au is a CNA...
La Trobe Shibboleth Identity Provider (AAF)
La Trobe's SAML 2.0 identity provider in the Australian Access Federation, and through AAF in eduGAIN. The entity is La Trobe's — entityID https://aaf.latrobe.edu.au/idp/shibbol...
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.
La Trobe University 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.
La Trobe University Context
JSON-LDSecurity 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 La Trobe University — 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.
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
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 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/la-trobe-university · machine-readable index on apis.io
This is an independent, third-party profile of La Trobe University, 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.