How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Deutsche Telekom Roles API

The Roles API from Deutsche Telekom — 16 operation(s) for roles.

Deutsche Telekom Roles API is one of 50 APIs that Deutsche Telekom publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Roles. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 28 operations across 16 paths, and defines 8 schemas. It is described by OpenAPI 3.0.1, at version 1.0.0.

Requests are made against a single base URL, https://api.telekom.de/controlplane/v1.

28 operations 16 paths 8 schemas 4 DELETE16 GET4 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0.0
Server
https://api.telekom.de/controlplane/v1
Contact
Resource Areas
1

Paths & Operations 28

Across 16 paths, the API surfaces 28 operations — 4 DELETE, 16 GET, 4 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Roles 28
GET
/{realm}/clients/{id}/roles
Get all roles for the realm or client
6 params → 2XX
POST
/{realm}/clients/{id}/roles
Create a new role for the realm or client
2 params body → 2XX
GET
/{realm}/clients/{id}/roles/{role-name}
Get a role by name
3 params → 2XX
PUT
/{realm}/clients/{id}/roles/{role-name}
Update a role by name
3 params body → 2XX
DELETE
/{realm}/clients/{id}/roles/{role-name}
Delete a role by name
3 params → 2XX
GET
/{realm}/clients/{id}/roles/{role-name}/composites
Get composites of the role
3 params → 2XX
POST
/{realm}/clients/{id}/roles/{role-name}/composites
Add a composite to the role
3 params body → 2XX
DELETE
/{realm}/clients/{id}/roles/{role-name}/composites
Remove roles from the role’s composite
3 params body → 2XX
GET
/{realm}/clients/{id}/roles/{role-name}/composites/clients/{client}
An app-level roles for the specified app for the role’s composite
4 params → 2XX
GET
/{realm}/clients/{id}/roles/{role-name}/composites/realm
Get realm-level roles of the role’s composite
3 params → 2XX
GET
/{realm}/clients/{id}/roles/{role-name}/groups
Return List of Groups that have the specified role name
6 params → 2XX
GET
/{realm}/clients/{id}/roles/{role-name}/management/permissions
Return object stating whether role Authoirzation permissions have been initialized or not and a reference
3 params → 2XX
PUT
/{realm}/clients/{id}/roles/{role-name}/management/permissions
Return object stating whether role Authoirzation permissions have been initialized or not and a reference
3 params body → 2XX
GET
/{realm}/clients/{id}/roles/{role-name}/users
Return List of Users that have the specified role name
5 params → 2XX
GET
/{realm}/roles
Get all roles for the realm or client
5 params → 2XX
POST
/{realm}/roles
Create a new role for the realm or client
1 param body → 2XX
GET
/{realm}/roles/{role-name}
Get a role by name
2 params → 2XX
PUT
/{realm}/roles/{role-name}
Update a role by name
2 params body → 2XX
DELETE
/{realm}/roles/{role-name}
Delete a role by name
2 params → 2XX
GET
/{realm}/roles/{role-name}/composites
Get composites of the role
2 params → 2XX
POST
/{realm}/roles/{role-name}/composites
Add a composite to the role
2 params body → 2XX
DELETE
/{realm}/roles/{role-name}/composites
Remove roles from the role’s composite
2 params body → 2XX
GET
/{realm}/roles/{role-name}/composites/clients/{client}
An app-level roles for the specified app for the role’s composite
3 params → 2XX
GET
/{realm}/roles/{role-name}/composites/realm
Get realm-level roles of the role’s composite
2 params → 2XX
GET
/{realm}/roles/{role-name}/groups
Return List of Groups that have the specified role name
5 params → 2XX
GET
/{realm}/roles/{role-name}/management/permissions
Return object stating whether role Authoirzation permissions have been initialized or not and a reference
2 params → 2XX
PUT
/{realm}/roles/{role-name}/management/permissions
Return object stating whether role Authoirzation permissions have been initialized or not and a reference
2 params body → 2XX
GET
/{realm}/roles/{role-name}/users
Return List of Users that have the specified role name
4 params → 2XX

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are UserRepresentation (23 properties), CredentialRepresentation (9 properties), RoleRepresentation (8 properties), GroupRepresentation (8 properties). Each schema is shown below with its type and property counts.

UserRepresentation
object
23 properties
CredentialRepresentation
object
9 properties
UserConsentRepresentation
object
4 properties
ManagementPermissionReference
object
3 properties
FederatedIdentityRepresentation
object
3 properties
GroupRepresentation
object
8 properties
RoleRepresentation
object
8 properties
RoleRepresentation-Composites
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

deutsche-telekom-roles-api-openapi.yml Raw ↑

Other APIs Deutsche Telekom publishes across the network.

Deutsche Telekom SMS API
Deutsche Telekom Rich Communication Services API
Deutsche Telekom Conversational Connect API
Deutsche Telekom Voice API
Deutsche Telekom Video API
Deutsche Telekom Reports API
Deutsche Telekom AI Studio
Deutsche Telekom Number Verification API
Deutsche Telekom Verify API
Deutsche Telekom 5G Slices for App Developers
Open Telekom Cloud
Open Telekom Integration Platform
Where this information came from

This is an independent, third-party profile of Deutsche Telekom Roles API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.