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 EventExposure API

With an EventExposure you declare that your application publishes eventsof a specific type. This makes the events available for subscription byother applications. Each exposure is scoped to a zone and can definevisibility, approval strategy, and publisher-side scopes with filtering.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 4 operations across 4 paths, and defines 18 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.

4 operations 4 paths 18 schemas 4 GET

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 4

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

EventExposure 4

With an EventExposure you declare that your application publishes events of a specific type. This makes the events available for subscription by other applications. Each exposure…

GET
/applications/{applicationId}/eventexposures
Find all EventExposures
getAllEventExposures 4 params → 200400401403415500
GET
/applications/{applicationId}/eventexposures/{eventExposureName}
Find an existing EventExposure
getEventExposure 2 params → 200400401403404415500
GET
/applications/{applicationId}/eventexposures/{eventExposureName}/status
Find an existing EventExposure and return its status
getEventExposureStatus 2 params → 200400401403404415500
GET
/applications/{applicationId}/eventexposures/{eventExposureName}/eventsubscriptions
Find all EventSubscriptions of this EventExposure
getAllExposureEventSubscriptions 5 params → 200400401403415500

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are Delivery (8 properties), EventExposure (5 properties), EventSubscription (4 properties), EventSubscriptionApproval (4 properties). Each schema is shown below with its type and property counts.

EventApproval
object
Configures how subscriptions to this event are approved. Maps to EventExposureSpec.Approval in the EventExposure CR.
2 properties
EventSubscription
object
Declaration that an application subscribes to events of a specific type. Maps to EventSubscriptionSpec in the EventSubscription CR.
4 properties
EventExposure
object
Declaration that an application publishes events of a specific type. Maps to EventExposureSpec in the EventExposure CR.
5 properties
EventVisibility
string
Defines who can see and subscribe to an exposed event. Maps to EventExposureSpec.Visibility in the EventExposure CR.
ResponseFilter
object
Controls which fields are included or excluded from the event payload.
2 properties
EventTrigger
object
Defines filtering criteria for event delivery. Maps to EventTrigger in the EventExposure/EventSubscription CR.
2 properties
EventSubscriptionApproval
object
Approval status of the event subscription.
4 properties
Delivery
object
Configures how events are delivered to the subscriber. Maps to EventSubscriptionSpec.Delivery in the EventSubscription CR.
8 properties 1 required
EventExposureListResponse
object
3 properties
EventScope
object
A named scope with publisher-side trigger filtering. Scopes allow publishers to partition their events and apply filters. Maps to EventExposureSpec.Scopes[] in…
2 properties 2 required
PayloadType
string
Defines the event payload format. Maps to EventSubscriptionSpec.Delivery.Payload in the EventSubscription CR.
DeliveryType
string
Defines how events are delivered to subscribers. Maps to EventSubscriptionSpec.Delivery.Type in the EventSubscription CR.
EventSubscriptionResponse
object
EventSubscriptionListResponse
object
3 properties
ResponseFilterMode
string
Controls whether the response filter includes or excludes the specified fields.
EventExposureResponse
object
4 required
EventApprovalStrategy
string
Defines the approval mode for event subscriptions. Maps to EventExposureSpec.Approval.Strategy in the EventExposure CR.
SelectionFilter
object
Defines criteria for selecting which events are delivered.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

deutsche-telekom-eventexposure-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
#EventExposure
← Back to D APIs
API Details
ID
deutsche-telekom:deutsche-telekom-eventexposure-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-eventexposure-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/deutsche-telekom-eventexposure-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 EventExposure 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.