University of Lisbon
The University of Lisbon (Universidade de Lisboa, ULisboa) is Portugal's largest public university — 18 schools plus the National Museum of Natural History and Science — and it is a federation of buyers rather than a producer of APIs. It runs no central developer portal, publishes no OpenAPI of its own, and has no open data portal: data.ulisboa.pt and dados.ulisboa.pt do not resolve, and the institution has no organization on the national portal dados.gov.pt. What it does operate, on its own infrastructure, is a small but real set of standards-based surfaces: the FenixEdu academic API at Instituto Superior Tecnico — institution-authored open-source software serving degrees, courses, campus spaces, blueprints, parking and a 1.2 MB serialized domain model anonymously, with Bennu OAuth 2.0 in front of person-scoped data; two independent OAI-PMH 2.0 endpoints, one over a 100,245-item DSpace 7.6.1 repository running since 2002 and one over the Koha union library catalog; and a SAML 2.0 identity provider published into the national RCTSaai federation and onward to eduGAIN, alongside a second IdP for Instituto Superior Tecnico that asserts SIRTFI. The institution also authors an open-source Erasmus Without Paper node on GitHub, which is its most substantive piece of public API engineering. Everything else is someone else's contract running under its name — most importantly researchportal.ulisboa.pt, which looks institutional and CNAMEs to ulisbon.elsevierpure.com; its own OAI-PMH Identify calls it a "Pure OAI Repository" and its Pure Web Service OpenAPI is behind an API key. Its Erasmus Without Paper node is hosted by another university entirely. Both are recorded here as tenancies, with the vendor contract deliberately left out of this repository.
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 Lisbon the way a machine reads it — 32 machine-readable artifacts across 1 API, 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 Lisbon scores 48.6/100 (developing), with a separate agent-readiness read of 26/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 Lisbon'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-lisbon/"
title="University of Lisbon on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-lisbon.svg"
alt="University of Lisbon Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-lisbon/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-lisbon/"
title="University of Lisbon on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-lisbon/card.svg"
alt="University of Lisbon 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 Lisbon
Each block below is one kind of artifact we hold for University of Lisbon. 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.
FenixEdu Academic API (Instituto Superior Tecnico)
Public REST API of the FenixEdu academic information system operated by Instituto Superior Tecnico, a school of the University of Lisbon. Anonymous access to institution metadat...
Repositorio da Universidade de Lisboa — OAI-PMH
OAI-PMH 2.0 metadata harvesting interface over the DSpace 7.6.1 institutional open-access repository. Operating since November 2002; 100,245 items; twelve metadata formats inclu...
Repositorio da Universidade de Lisboa — DSpace REST API
Anonymous HAL+JSON REST API of the institution's DSpace 7.6.1 repository — communities, collections, items, bitstreams, discovery search, metadata schemas and external-source in...
Catalogo Coletivo ULisboa (Koha) — OAI-PMH
OAI-PMH 2.0 interface over the union library catalog of the 18 schools, the National Museum of Natural History and Science and the Tropical Scientific Research Institute, runnin...
Universidade de Lisboa SAML 2.0 Identity Provider (RCTSaai / eduGAIN)
The institution's central SAML 2.0 identity provider, published into the Portuguese national identity federation RCTSaai (operated by FCCN) and onward to eduGAIN. Live machine-r...
Instituto Superior Tecnico SAML 2.0 Identity Provider (RCTSaai / eduGAIN)
The identity provider for Instituto Superior Tecnico, federated through RCTSaai into eduGAIN and asserting SIRTFI incident-response assurance — a stronger security posture than ...
ULisboa Research Portal — Elsevier Pure tenancy
The institution's current research information system, an Elsevier Pure tenant (tenant id "ulisbon") presented on a ulisboa.pt hostname. The relationship is real and is recorded...
Erasmus Without Paper node (HEI ulisboa.pt)
The institution's node in the Erasmus Without Paper network, through which student mobility, inter-institutional agreements, learning agreements and transcripts move between Eur...
DataCite repository membership (QWBT.ULISBOA)
An active DataCite repository client registered to the university's central services for minting DOIs over the institutional repository. Recorded honestly with its caveat: the D...
ROR organization identifier
The institution's registered ROR identifier — the canonical machine-readable organizational identity used across DataCite, Crossref and OpenAIRE metadata. ROR also holds records...
Crossref memberships (organic units)
Five ULisboa organic units hold Crossref member IDs in their own right, minting DOIs for their journals independently of the rectorate. There is no single institutional Crossref...
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.
University Of Lisbon 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 2
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.
University of Lisbon 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.
Examples 9
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.
Datacite Client Qwbt Ulisboa
EXAMPLEFenixedu About
EXAMPLEFenixedu Academicterms
EXAMPLEFenixedu Degree
EXAMPLEFenixedu Error 401
EXAMPLEFenixedu Error 404
EXAMPLEFenixedu Parking
EXAMPLERepositorio Dspace Api Root
EXAMPLEScroll within the panel for all 9 ·
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 Lisbon — 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 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 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/university-of-lisbon · machine-readable index on apis.io
This is an independent, third-party profile of University of Lisbon, 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.