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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Deutsche Telekom

Deutsche Telekom EventSpecification API

Manage EventSpecifications

Documentation Provider Profile APIs.io OpenAPI GitHub

Deutsche Telekom EventSpecification 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 EventSpecification. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 6 operations across 3 paths, and defines 17 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.

6 operations 3 paths 17 schemas 1 DELETE3 GET1 POST1 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
TARDIS
Resource Areas
1

Paths & Operations 6

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

EventSpecification 6

Manage EventSpecifications

GET
/eventspecifications
Find all EventSpecifications
getAllEventSpecifications 3 params → 200400401403404415500
POST
/eventspecificationsdeprecated
Create an EventSpecification
createEventSpecification body → 202400401403404415500
GET
/eventspecifications/{eventSpecificationId}
Find an existing EventSpecification
getEventSpecification 1 param → 200400401403404415500
PUT
/eventspecifications/{eventSpecificationId}
Update an existing EventSpecification
updateEventSpecification 1 param body → 202400401403404415500
DELETE
/eventspecifications/{eventSpecificationId}
Delete an EventSpecification
deleteEventSpecification 1 param → 204400401403404415500
GET
/eventspecifications/{eventSpecificationId}/status
Find an existing EventSpecification and return its status
getEventSpecificationStatus 1 param → 200400401403404415500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are ResourceStatusResponse (8 properties), Error (7 properties), ResourceRef (5 properties), Status (5 properties). Each schema is shown below with its type and property counts.

EventSpecification
object
5 properties 3 required
FieldProblem
object
3 properties 1 required
EventSpecificationListResponse
object
2 properties
State
string
EventSpecificationUpdateRequest
Links
object
HATEOAS links for pagination
2 properties 2 required
OverallStatus
string
Status of this resource and all its relevant sub-resources
EventSpecificationCreateRequest
ResourceStatusResponse
object
Response resource which contains information about the status of the resource and all its relevant sub-resources
8 properties 3 required
Problem
object
5 properties 2 required
StateInfo
object
2 properties 1 required
Error
object
RFC-7807 conform object sent on any error
7 properties 2 required
ProcessingState
string
Status
object
5 properties 3 required
ResourceRef
object
5 properties 4 required
EventSpecificationResponse
5 required
Category
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Deutsche Telekom publishes across the network.

Deutsche Telekom SMS API
AE Profile APIs.io
Deutsche Telekom Rich Communication Services API
AE Profile APIs.io
Deutsche Telekom Conversational Connect API
AE Profile APIs.io
Deutsche Telekom Voice API
AE Profile APIs.io
Deutsche Telekom Video API
AE Profile APIs.io
Deutsche Telekom Reports API
AE Profile APIs.io
Deutsche Telekom AI Studio
AE Profile APIs.io
Deutsche Telekom Number Verification API
AE Profile APIs.io
Deutsche Telekom Verify API
AE Profile APIs.io
Deutsche Telekom 5G Slices for App Developers
AE Profile APIs.io
Open Telekom Cloud
AE Profile APIs.io
Open Telekom Integration Platform
AE Profile APIs.io
#EventSpecification
← Back to D APIs
API Details
ID
deutsche-telekom:deutsche-telekom-eventspecification-api
Server
https://api.telekom.de/controlplane/v1
Docs
https://developer.telekom.com/en/products/sms-api
Provider
Deutsche Telekom
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=deutsche-telekom-eventspecification-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/deutsche-telekom-eventspecification-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Deutsche Telekom EventSpecification 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.