Delft University of Technology · OAuth Scopes

Delft University of Technology OAuth Scopes

OAuth 2.0 probed

Delft University of Technology 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 EducationEducationTechnical UniversityResearch DataOpen AccessIdentity FederationResearch RepositoryResearch Computing4TU.FederationNetherlandsEurope
Scopes: 0 Flows: Method: probed

Scopes (0)

Delft University of Technology 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.

TU Delft publishes no authorization scope vocabulary for any surface it operates. The only public institutional API, 4TU.ResearchData, authorizes with an opaque personal bearer token that carries no scope claims; there is no OAuth 2.0 authorization server, no OIDC discovery document, and no consent screen enumerating permissions. This file records the absence deliberately rather than leaving the slot empty — an empty scopes/ directory reads as "not checked", and this was checked.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-19'
method: probed
source: >-
  https://data.4tu.nl/v2/account/articles (HTTP 403), djehuty docs/api.md, and a check for
  https://data.4tu.nl/.well-known/openid-configuration and /.well-known/oauth-authorization-server
  (both HTTP 404, "This resource does not exist.").
x-operator: institution
scopes_published: false
note: >-
  TU Delft publishes no authorization scope vocabulary for any surface it operates. The only
  public institutional API, 4TU.ResearchData, authorizes with an opaque personal bearer token
  that carries no scope claims; there is no OAuth 2.0 authorization server, no OIDC discovery
  document, and no consent screen enumerating permissions. This file records the absence
  deliberately rather than leaving the slot empty — an empty scopes/ directory reads as
  "not checked", and this was checked.
scopes: []
authorization_model:
  type: all-or-nothing-token
  granularity: account
  delegation: none
  consent_surface: none
  revocation: Token can be revoked from the depositor dashboard; no programmatic revocation endpoint found.

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/tu-delft-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.