Aalto University
Aalto University is a multidisciplinary public research university in Espoo, Finland, formed in 2010 from the merger of the Helsinki University of Technology, the Helsinki School of Economics and the University of Art and Design Helsinki. Unusually for this cohort, Aalto operates a real institution-owned API program rather than only a set of vendor tenancies: the Aalto API Gateway (Red Hat 3scale, at 3scale.apps.ocp4.aalto.fi) publishes five documented API products — facilities and room reservations, SISU course data, Acris research publications, projects and cost centres, and a deprecated Oodi-sourced course API — and its ActiveDocs index is publicly readable, exposing forty-four Aalto-authored Swagger/OpenAPI documents whose servers all sit under *.api.aalto.fi. Every one of those endpoints is API-key gated and returns 403 to an anonymous caller, so the contracts are public while the data is not. The genuinely anonymous surfaces are elsewhere: the Aaltodoc institutional repository (Aalto-hosted DSpace 9.2) serves a live OAI-PMH 2.0 endpoint with sixteen metadata formats and an open REST API, and the Linked Open Aalto Data SPARQL endpoint answers real queries — but only over POST, since GET times out. Aalto also runs its own Shibboleth SAML 2.0 identity provider and is registered in the Haka federation with forty-one entities, which is machine-readable institutional infrastructure that almost no university in this cohort catalogues. Its library discovery, research information system and research portal are vendor tenancies (Ex Libris, Elsevier Pure) and are recorded as relationships, not as Aalto's engineering.
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 Aalto University the way a machine reads it — 21 machine-readable artifacts across 5 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 — Aalto University scores 42.2/100 (developing), with a separate agent-readiness read of 30/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.
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-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Aalto 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/aalto/"
title="Aalto University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aalto.svg"
alt="Aalto University Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/aalto/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aalto/"
title="Aalto University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aalto/card.svg"
alt="Aalto 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 Aalto University
Each block below is one kind of artifact we hold for Aalto 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 13
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.
Aalto API Gateway
Aalto's own Red Hat 3scale API gateway, the front door to every institution-operated API at Aalto. Five API products are documented on the portal; the underlying ActiveDocs inde...
Aalto Facilities API
Buildings, building details, opening hours, rooms and room reservations across Aalto's Espoo campus. OpenAPI 3.0.1, version 1.0.2, contact it-integ@aalto.fi, served from facilit...
Aalto Course API (SISU)
Course units and course-unit realisations drawn from SISU, the Finnish higher-education student information system Aalto runs. OpenAPI 3.0.1, version 0.0.18, titled "Sisu API (r...
Aalto Research Publications API (Acris gateway)
Aalto's own four-path gateway contract over Acris, its research information system, exposing research outputs, a single output by id, an enhanced output view and output fingerpr...
Aalto Projects and Cost Centers API
Administrative reference data — cost centres, projects, departments and schools — from Aalto's data warehouse. OpenAPI 3.0.0, version 1.0.10, X-ApiKey header, served from api.aa...
Aalto People Profile API
A two-path proxy over Aaltopeople returning groups and public staff profiles. OpenAPI 3.0.1, version 1.0.3, contact it-integ@aalto.fi, served from aaltopeople.api.aalto.fi. Pres...
Aalto Open API — Course API (Oodi, deprecated)
The Oodi-sourced course API, still published on the portal and explicitly marked deprecated: "This API source is OODI and should not be used." Swagger 2.0, two paths, superseded...
Aaltodoc Repository — OAI-PMH and DSpace REST
Aalto's institutional repository of theses, articles and conference publications, running Aalto-hosted DSpace 9.2 on aaltodoc.aalto.fi. Both read surfaces are fully anonymous an...
Aalto Shibboleth Identity Provider (Haka / eduGAIN)
Aalto's own Shibboleth SAML 2.0 identity provider, entityID https://idp.aalto.fi/idp/shibboleth, scope aalto.fi, registration authority http://www.aalto.fi registered 2019-04-15...
Linked Open Aalto Data (SPARQL)
Aalto's open data published as Linked Data — courses, people, publications, places, projects, organisation and events — under data.aalto.fi URIs. The landing page and dataset de...
Acris — Aalto Current Research Information System (Elsevier Pure)
Aalto's research information system is Elsevier Pure, deployed as Acris at acris.aalto.fi with the Pure Portal at research.aalto.fi. The data and the DOIs are Aalto's; the contr...
Aalto Learning Centre discovery (Ex Libris Primo / Alma, Finna)
Library discovery and the library management system are Ex Libris products under Aalto tenancies — primo.aalto.fi resolves to the Primo NDE interface with view 358AALTO_INST:MAI...
SISU student information system (Funidata)
sisu.aalto.fi is Aalto's deployment of SISU, the student information system built by Funidata, a company jointly owned by Finnish universities. It is the system of record behind...
Scroll within the panel for all 13 ·
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.
Aalto Plans Pricing
PLANSRate 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.
Aalto 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.
Aalto 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.
Aalto Context
JSON-LDJSON Schema 2
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.
Aalto facilities api — component schemas
JSON SCHEMASecurity 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 Aalto 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.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
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 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
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 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/aalto · machine-readable index on apis.io
This is an independent, third-party profile of Aalto 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.