University of Liverpool · OAuth Scopes

University of Liverpool OAuth Scopes

OAuth 2.0 probed

University of Liverpool uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

EducationHigher EducationUniversityRussell GroupUnited KingdomResearchResearch RepositoryResearch DataOpen AccessOAI-PMHEPrintsIdentity FederationLibraryMetadata
Scopes: 0 Flows: Method: probed

Scopes (0)

University of Liverpool implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

The only scope vocabulary the University of Liverpool publishes machine-readably is the one advertised by its own AD FS authorization server's OpenID Connect discovery document. Read verbatim from that document on 2026-09-01. The scholarly surfaces (OAI-PMH, EPrints REST) are anonymous and have no scope model at all; the Canvas, Elements, Alma/Primo and Talis scopes belong to those vendors' products and are deliberately not restated here.

📄 Provider scope reference:

Source

OAuth Scopes

university-of-liverpool-scopes.yml Raw ↑ 
generated: '2026-09-01'
method: probed
source: https://fs.liverpool.ac.uk/adfs/.well-known/openid-configuration
note: >-
  The only scope vocabulary the University of Liverpool publishes machine-readably is the one
  advertised by its own AD FS authorization server's OpenID Connect discovery document. Read
  verbatim from that document on 2026-09-01. The scholarly surfaces (OAI-PMH, EPrints REST) are
  anonymous and have no scope model at all; the Canvas, Elements, Alma/Primo and Talis scopes belong
  to those vendors' products and are deliberately not restated here.
issuer: https://fs.liverpool.ac.uk/adfs
operator: institution
scopes:
- name: openid
  description: Standard OpenID Connect scope requesting an ID token.
- name: profile
  description: Standard OIDC profile claims.
- name: email
  description: Standard OIDC email claim.
- name: allatclaims
  description: AD FS scope returning all claims configured for the relying party.
- name: aza
  description: AD FS broker/primary-refresh-token scope used by Microsoft client stacks.
- name: user_impersonation
  description: AD FS delegated access on behalf of the signed-in user.
- name: logon_cert
  description: AD FS certificate-based logon scope.
- name: winhello_cert
  description: AD FS Windows Hello for Business certificate enrolment scope.
- name: vpn_cert
  description: AD FS VPN certificate issuance scope.
grant_types_supported:
- authorization_code
- refresh_token
- client_credentials
- urn:ietf:params:oauth:grant-type:jwt-bearer
- implicit
- password
- srv_challenge
- urn:ietf:params:oauth:grant-type:device_code
- device_code
response_types_supported:
- code
- id_token
- code id_token
- id_token token
- code token
- code id_token token
self_service_registration: false

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set 
curl "https://apis.io/api/v1/scopes/university-of-liverpool-scopes"
All oauth scopes 
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.