Deutsche Telekom · Authentication Profile

Deutsche Telekom Authentication

Authentication

Deutsche Telekom secures its APIs with http and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

TelecommunicationsTelcoMobile Network OperatorCPaaSNetwork API5GCloudIdentityNumber VerificationOpen GatewayCAMARAT-SystemsT-MobileMagentaMagentaBusinessAPI GatewayOpen SourceGermanyEurope
Methods: http, oauth2 Schemes: 2 OAuth flows: clientCredentials API key in:

Security Schemes

bearerAuth http
scheme: bearer
OAuth2 oauth2
· flows: clientCredentials

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/controlplane-file-manager-openapi.yml, openapi/controlplane-identity-openapi.yml,
  openapi/controlplane-rover-server-openapi.yml
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - clientCredentials
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: JWT Bearer token authentication
  sources:
  - openapi/controlplane-file-manager-openapi.yml
  - openapi/controlplane-identity-openapi.yml
- name: OAuth2
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://example.com/auth/realms/realm//protocol/openid-connect/token
    scopes: 13
  description: OAuth2 client_credentials flow
  sources:
  - openapi/controlplane-rover-server-openapi.yml