Technical University of Berlin OAuth Scopes

OAuth 2.0 probed

Technical University of Berlin publishes 26 OAuth 2.0 scopes via the authorizationCode, clientCredentials, and deviceCode flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Technical University of Berlin API on a user’s behalf.

Tokens are issued from https://git.tu-berlin.de/oauth/token.

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 UniversityGermanyBerlinResearch DataOpen AccessRepositoryLibraryIdentity FederationCourse CatalogResearch Computing
Scopes: 26 Flows: authorizationCode, clientCredentials, deviceCode Method: probed

OAuth endpoints

Authorization URL
https://git.tu-berlin.de/oauth/authorize
Token URL
https://git.tu-berlin.de/oauth/token
Flows
authorizationCodeclientCredentialsdeviceCode

Scopes (26)

ScopeDescriptionFlows
api Full read/write access to the GitLab API on behalf of the user, across all groups and projects they can reach.
read_api Read-only access to the whole GitLab API.
read_user Read the authenticated user's profile.
read_repository Read repository contents over HTTPS and the API.
write_repository Push to repositories over HTTPS and the API.
read_registry Pull container images from the instance registry.
write_registry Push container images to the instance registry.
read_virtual_registry Read from virtual (dependency-proxy style) registries.
write_virtual_registry Write to virtual registries.
read_observability Read observability (metrics/tracing) data.
write_observability Write observability data.
create_runner Create CI runners.
manage_runner Manage existing CI runners.
k8s_proxy Proxy access to Kubernetes clusters connected to the instance.
self_rotate Allow a token to rotate itself.
mcp Access GitLab's Model Context Protocol surface. Advertised by the instance; /api/v4/mcp returns 401 unauthenticated.
mcp_orbit GitLab MCP "orbit" surface, advertised alongside mcp.
ai_features Access GitLab AI features.
ai_workflows Access GitLab AI workflow features.
read_service_ping Read instance service-ping telemetry.
sudo Act as any user — administrator only.
admin_mode Perform administrative operations — administrator only.
openid Standard OpenID Connect scope; requests an ID token.
profile Release the user's profile claims.
email Release the user's email claim.
user:* Wildcard user-scoped access as advertised in scopes_supported.

Source

OAuth Scopes

tu-berlin-scopes.yml Raw ↑
generated: '2026-08-30'
method: probed
source: https://git.tu-berlin.de/.well-known/openid-configuration
note: >-
  TU Berlin publishes no OpenAPI, so no scope could be derived from a contract. Every scope
  string below is read verbatim from the scopes_supported array of the live OIDC discovery
  document served by the institution's self-hosted GitLab at git.tu-berlin.de (200,
  application/json, saved at well-known/tu-berlin-gitlab-openid-configuration.json). The
  scope vocabulary is GitLab's product vocabulary; the DEPLOYMENT advertising it is TU
  Berlin's, which is why it is recorded here and the descriptions are ours. No other TU
  Berlin host serves an OAuth/OIDC discovery document.
  This file was generated by API Evangelist from the live discovery document on 2026-08-30;
  TU Berlin publishes no scope documentation of its own.
schemes:
- name: gitlab-tu-berlin
  source: https://git.tu-berlin.de/.well-known/openid-configuration
  issuer: https://git.tu-berlin.de
  operator: institution
  flows:
  - flow: authorizationCode
    authorizationUrl: https://git.tu-berlin.de/oauth/authorize
    tokenUrl: https://git.tu-berlin.de/oauth/token
    pkce: S256
  - flow: clientCredentials
    tokenUrl: https://git.tu-berlin.de/oauth/token
  - flow: deviceCode
    tokenUrl: https://git.tu-berlin.de/oauth/token
scopes:
- scope: api
  description: Full read/write access to the GitLab API on behalf of the user, across all groups and projects they can reach.
- scope: read_api
  description: Read-only access to the whole GitLab API.
- scope: read_user
  description: Read the authenticated user's profile.
- scope: read_repository
  description: Read repository contents over HTTPS and the API.
- scope: write_repository
  description: Push to repositories over HTTPS and the API.
- scope: read_registry
  description: Pull container images from the instance registry.
- scope: write_registry
  description: Push container images to the instance registry.
- scope: read_virtual_registry
  description: Read from virtual (dependency-proxy style) registries.
- scope: write_virtual_registry
  description: Write to virtual registries.
- scope: read_observability
  description: Read observability (metrics/tracing) data.
- scope: write_observability
  description: Write observability data.
- scope: create_runner
  description: Create CI runners.
- scope: manage_runner
  description: Manage existing CI runners.
- scope: k8s_proxy
  description: Proxy access to Kubernetes clusters connected to the instance.
- scope: self_rotate
  description: Allow a token to rotate itself.
- scope: mcp
  description: Access GitLab's Model Context Protocol surface. Advertised by the instance; /api/v4/mcp returns 401 unauthenticated.
- scope: mcp_orbit
  description: GitLab MCP "orbit" surface, advertised alongside mcp.
- scope: ai_features
  description: Access GitLab AI features.
- scope: ai_workflows
  description: Access GitLab AI workflow features.
- scope: read_service_ping
  description: Read instance service-ping telemetry.
- scope: sudo
  description: Act as any user — administrator only.
- scope: admin_mode
  description: Perform administrative operations — administrator only.
- scope: openid
  description: Standard OpenID Connect scope; requests an ID token.
- scope: profile
  description: Release the user's profile claims.
- scope: email
  description: Release the user's email claim.
- scope: 'user:*'
  description: Wildcard user-scoped access as advertised in scopes_supported.

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-berlin-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.

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