KU Leuven · OAuth Scopes

KU Leuven OAuth Scopes

OAuth 2.0 probed

KU Leuven 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.

UniversityHigher EducationEducationBelgiumEuropeFlandersResearch DataResearch RepositoryOpen DataCourse CatalogIdentity FederationOAI-PMHDataverseOpenSearchPublic Research University

Scopes: 0 Flows: Method: probed

Scopes (0)

KU Leuven 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.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-19'
method: probed
source: >-
  Attempted discovery of a published authorization-scope model across every KU Leuven-operated
  surface on 2026-08-19: the ICTS Data Services documentation, the RDR API documentation and its
  live OpenAPI at https://rdr.kuleuven.be/openapi, and the SAP OData timetable documentation.
name: KU Leuven — authorization scopes
operator: institution
scopes: []
finding: none_published
detail: >-
  No OAuth scope, no API-key scope and no permission string is published for any KU Leuven surface.
  The public ICTS Data Services indices need no authorization at all. The RDR uses Dataverse's role
  model rather than scopes — access is decided by role assignment (Dataset Creator and the roles
  managed under /roles and /admin), not by a scope granted to a client. The timetable API documents
  an OAuth authorization-code grant but publishes no scope names, and client credentials are issued
  by KU Leuven case by case.
evidence:
- url: https://rdr.kuleuven.be/openapi
  status: 200
  note: >-
    Live Dataverse 6.7.1 description, 425 paths, no securitySchemes with an oauth2 flow and no
    scope enumeration.
- url: https://admin.kuleuven.be/icts/services/dataservices/api/uurrooster
  status: 200
  note: Documents the OAuth authorization endpoint but names no scopes.
- url: https://admin.kuleuven.be/icts/services/dataservices/gebruiksvoorwaarden.html
  status: 200
  note: Terms of use govern the public indices in place of an authorization model.
related:
  role_model: openapi/ku-leuven-roles-api-openapi.yml

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/ku-leuven-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 email required.

GitHub Google LinkedIn

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