University of Sussex
The University of Sussex is a research-intensive public university at Falmer near Brighton in the United Kingdom, a member of the Russell Group's peer set of UK research institutions and ranked #247 in the QS World University Rankings 2025. Its programmable footprint is small and almost entirely indirect, and this profile says so rather than padding it. The one surface the university genuinely operates and publishes machine-readably is its own Shibboleth identity provider: idp.sussex.ac.uk serves signed SAML 2.0 metadata with an entityID of https://idp.sussex.ac.uk/shibboleth and a shibmd:Scope of sussex.ac.uk, running on a Sussex-controlled Azure deployment rather than a vendor's multi-tenant service. Everything else that looks like a Sussex API is a vendor product running under a Sussex name: Okta for single sign-on at okta.sussex.ac.uk, Instructure Canvas for the VLE at canvas.sussex.ac.uk, Figshare for the research repository at sussex.figshare.com, and Ex Libris Primo for library discovery. Those relationships are recorded here as tenant surfaces because they are real institutional facts, but the contracts behind them belong to the vendors and are scored against the vendors' own profiles. Sussex operates no public developer portal, publishes no OpenAPI of its own, and its GitHub organization has no public repositories. The former Sussex Research Online EPrints repository and its OAI-PMH endpoint have been decommissioned and now redirect to an HTML publications page.
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 University of Sussex the way a machine reads it — 11 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 — University of Sussex scores 31.1/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.
Why this profile is thin
Sussex operates exactly one machine-readable contract of its own — the Shibboleth SAML 2.0 identity-provider metadata at idp.sussex.ac.uk, whose host CNAMEs to a Sussex-run Azure instance (uos-idp-shib-prod.uksouth.cloudapp.azure.com), not to a vendor. Every other programmable surface reachable under a Sussex name is a vendor platform on a Sussex-branded hostname: okta.sussex.ac.uk CNAMEs to sussexac.customdomains.okta.com, canvas.sussex.ac.uk to universityofsussex-vanity.instructure.com, sussex.figshare.com to figshare.com, and library discovery is an Ex Libris Primo view (44SUS_INST). There is no developer portal, no institution-authored OpenAPI, no open-data portal (data.sussex.ac.uk and api.sussex.ac.uk do not resolve), and the GitHub organization has zero public repositories. One probe was blocked rather than answered: sussex.figshare.com returns an AWS WAF challenge (HTTP 202, x-amzn-waf-action: challenge, empty body) to every request including ?verb=Identify, so the Figshare tenant's OAI-PMH endpoint could not be confirmed either way. This profile previously carried ten OpenAPIs and thirty-eight artifacts derived from them; all ten were Figshare's generic v2 contract with an empty servers block, shipped identically by eleven other institutions, and have been removed.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is University of Sussex'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://idp.sussex.ac.uk/idp/shibboleth→ HTTP 200https://okta.sussex.ac.uk/.well-known/openid-configuration→ HTTP 200https://canvas.sussex.ac.uk/api/v1/accounts→ HTTP 401https://canvas.sussex.ac.uk/api/lti/security/jwks→ HTTP 200https://sussex.figshare.com/oai?verb=Identify→ HTTP 202https://sro.sussex.ac.uk/cgi/oai2?verb=Identify→ HTTP 200https://sussex.primo.exlibrisgroup.com/discovery/search?vid=44SUS_INST:44SUS_VU1→ HTTP 200https://api.github.com/orgs/universityofsussex/repos→ HTTP 200https://data.sussex.ac.uk/→ HTTP 0https://api.sussex.ac.uk/→ HTTP 0https://www.sussex.ac.uk/llms.txt→ HTTP 404
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 Sussex'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-sussex/"
title="University of Sussex on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-sussex.svg"
alt="University of Sussex Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-sussex/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-sussex/"
title="University of Sussex on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-sussex/card.svg"
alt="University of Sussex 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 Sussex
Each block below is one kind of artifact we hold for University of Sussex. 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 5
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.
University of Sussex Shibboleth Identity Provider (SAML 2.0 metadata)
The university's own Shibboleth IdP, publishing signed SAML 2.0 metadata as a machine-readable EntityDescriptor. entityID https://idp.sussex.ac.uk/shibboleth, shibmd:Scope susse...
University of Sussex Single Sign-On (Okta tenant)
Sussex's Okta organization, reached on the Sussex-branded hostname okta.sussex.ac.uk, which CNAMEs to sussexac.customdomains.okta.com. It serves a complete OpenID Connect discov...
University of Sussex Canvas VLE (Instructure tenant)
Sussex's virtual learning environment, an Instructure Canvas deployment on the university's own hostname canvas.sussex.ac.uk, which CNAMEs to universityofsussex-vanity.instructu...
University of Sussex Research Data Repository (Figshare tenant)
Sussex's institutional research repository, a Figshare tenant at sussex.figshare.com (CNAME to figshare.com). The relationship is independently confirmed by DataCite, where the ...
University of Sussex Library Discovery (Ex Libris Primo tenant)
Library discovery for Sussex runs on Ex Libris Primo VE as institution view 44SUS_INST / 44SUS_VU1, hosted on the vendor's shared platform at sussex.primo.exlibrisgroup.com. Sus...
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 Sussex 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.
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 Sussex — 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 1
Reference material describing how the API behaves
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
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 3
Pricing, plans, and the legal terms of use
Company 3
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/university-of-sussex · machine-readable index on apis.io
This is an independent, third-party profile of University of Sussex, 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.