Queen Mary University of London
Queen Mary University of London (QMUL) is a public research university in London and a member of the Russell Group. It runs no developer portal, publishes no OpenAPI, and offers no self-service API credentials — but the claim that it therefore has no programmable surface is wrong, and this profile replaces it. Four surfaces are institution-operated and were verified live: Queen Mary Research Online (QMRO) runs DSpace 8.4 and answers an unauthenticated HAL service document at qmro.qmul.ac.uk/server/api advertising 79 endpoint families; QMplus, the university's Moodle learning platform, is an LTI 1.3 Advantage tool platform publishing its own RSA key set, OIDC auth, token and services endpoints; the QMplus Moodle web-services REST entry point is live and token-gated; and Apocrita, the university's own HPC service, publishes machine-readable documentation at docs.hpc.qmul.ac.uk on Queen Mary's own address space. Two more are federated identity the institution genuinely owns: a Shibboleth Identity Provider registered in the Jisc UK Access Management Federation with the scope qmul.ac.uk, and a Microsoft Entra ID tenant whose OpenID Connect discovery document resolves from the qmul.ac.uk domain. Two are tenant relationships on suppliers' platforms and are recorded as relationships, not as Queen Mary's engineering: the Ex Libris Primo VE / Alma library discovery deployment behind librarysearch.qmul.ac.uk, whose public configuration API and SRU endpoint both answer, and the SearchStax Solr index that powers site and course search. Three are registry memberships — a DataCite provider record, a Crossref member id with its own DOI prefix, and a ROR identifier. Student-facing systems (MySIS, timetables, MyQMUL) are authentication-gated, no open-data portal exists, and the institution's public dataset publishing amounts to CSV files under the Freedom of Information publication scheme.
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 Queen Mary University of London the way a machine reads it — 18 machine-readable artifacts across 11 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 — Queen Mary University of London scores 28.8/100 (thin), 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.
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 Queen Mary University of London'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/queen-mary-university-of-london/"
title="Queen Mary University of London on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/queen-mary-university-of-london.svg"
alt="Queen Mary University of London Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/queen-mary-university-of-london/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/queen-mary-university-of-london/"
title="Queen Mary University of London on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/queen-mary-university-of-london/card.svg"
alt="Queen Mary University of London 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 Queen Mary University of London
Each block below is one kind of artifact we hold for Queen Mary University of London. 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.
Queen Mary Research Online (QMRO) — DSpace 8.4 REST API
Queen Mary's open-access institutional repository runs DSpace 8.4 and exposes the standard DSpace REST API on the university's own host. The HAL service document at /server/api ...
QMplus LTI 1.3 Advantage Tool Platform
QMplus, Queen Mary's Moodle virtual learning environment, runs as an LTI 1.3 / LTI Advantage tool platform and publishes the four endpoints the standard requires an external lea...
QMplus Moodle Web Services (REST)
The standard Moodle web-services REST entry point on QMplus. It answers an unauthenticated request with a structured moodle_exception carrying ERRORCODE invalidtoken, which prov...
Shibboleth SAML Identity Provider (UK Access Management Federation)
Queen Mary's own Shibboleth Identity Provider, entityID https://idp.shibboleth.qmul.ac.uk/idp/shibboleth, asserting shibmd:Scope "qmul.ac.uk". Its entity descriptor is published...
Microsoft Entra ID Tenant — OpenID Connect Discovery
Queen Mary's Microsoft Entra ID tenant, GUID 569df091-b013-40e3-86ee-bd9cb9e25814, EU region scope. The OpenID Connect discovery document resolves from the qmul.ac.uk domain hin...
Apocrita — Queen Mary Research Computing Service
Apocrita is Queen Mary's own high-performance computing cluster, run by ITS Research, and its documentation site is genuinely institution-hosted — docs.hpc.qmul.ac.uk resolves t...
Library Search — Ex Libris Primo VE / Alma discovery tenancy
Queen Mary's library discovery layer is Ex Libris Primo VE over Alma, fronted by the vanity host librarysearch.qmul.ac.uk, which CNAMEs to qmul.primo.exlibrisgroup.com and on to...
Queen Mary site and course search — SearchStax Solr tenancy
Every page on qmul.ac.uk, including the undergraduate course finder, queries a hosted Apache Solr index on SearchStax under Queen Mary's own account 29847 and index qmu-1736. Th...
DataCite member organisation and repository client
Queen Mary is a DataCite member organisation, provider id "iuar", memberType consortium_organization, linked to ROR https://ror.org/026zzn846, with one registered repository cli...
Crossref member and DOI prefix
Queen Mary is a Crossref member, id 11031, holding DOI prefix 10.26494. Recorded as a registry membership on the same basis as the DataCite entry: it is a fact about the institu...
ROR organisation identifier
Queen Mary's Research Organization Registry identifier, https://ror.org/026zzn846. It is the join key that connects the institution's DataCite membership, its ORCID affiliation ...
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.
Queen Mary University Of London 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.
Examples 1
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.
Queen Mary University Of London Authentication
saml2/openid_connect/jwt_bearer/none · 5 schemes
SECURITYResources
Every other property we hold for Queen Mary University of London — 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 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 8
Properties that don't map to a standard resource type
Scroll within the panel for all 8 ·
← All providers · Data indexed from github.com/api-evangelist/queen-mary-university-of-london · machine-readable index on apis.io
This is an independent, third-party profile of Queen Mary University of London, 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.