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
Kontakt.io

Kontakt.io Stream API

The Stream API from Kontakt.io — 9 operation(s) for stream.

Documentation Provider Profile APIs.io OpenAPI GitHub

Kontakt.io Stream API is one of 30 APIs that Kontakt.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Stream. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, a changelog, and rate-limit docs.

This API exposes 24 operations across 9 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://apps.cloud.us.kontakt.io, https://apps.cloud.uk.kontakt.io.

24 operations 9 paths 9 schemas 7 DELETE6 GET4 PATCH7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://dm-api.cloud.us.kontakt.io
Authentication
API Key
Contact
Kontakt.io Support
Terms of Service
View terms
Resource Areas
1

Authentication & Security 1

Kontakt.io Stream API declares 1 security scheme for authenticating requests. An API key is passed in the header as Api-Key (api_key). By default, every request must be authenticated.

  • api_key — Your Kio Cloud API Key is required to be provided in the Api-Key header in each API call. Get your API Key: sign in to Kio Cloud select Users select Security c…

Paths & Operations 24

Across 9 paths, the API surfaces 24 operations — 7 DELETE, 6 GET, 4 PATCH, 7 POST. Each is listed below with its method, path, parameters, and response codes.

Stream 24
GET
/v3/channels
List all configured channels
get-v3-channels 1 param → 200
POST
/v3/channels
Create new channel
post-v3-channels 1 param body → 200
GET
/v3/channels/{id}
Retrieve channel by id
get-v3-channels-id 1 param → 200
DELETE
/v3/channels/{id}
Delete a channel by id
delete-v3-channels-id 1 param → 200
PATCH
/v3/channels/{id}
Update Channel by ID
patch-v3-channels-id 1 param body → 200
GET
/v3/streams/subscriptions/telemetry
Retrieve telemetry subscription
get-v3-streams-subscriptions-telemetry
POST
/v3/streams/subscriptions/telemetry
Create telemetry subscription
post-v3-streams-subscriptions-telemetry body → 200
PATCH
/v3/streams/subscriptions/telemetry
Update telemetry subscription
patch-v3-streams-subscriptions-telemetry body → 200
DELETE
/v3/streams/subscriptions/telemetry
Delete telemetry subscription
delete-v3-streams-subscriptions-telemetry → 204
GET
/v3/channels/state/{id}
Retrieve channel connection state by id
get-v3-channels-state 1 param → 200
GET
/v3/streams/subscriptions/position
Retrieve position subscription
get-v3-streams-subscriptions-position → 200
POST
/v3/streams/subscriptions/position
Create position subscription
post-v3-streams-subscriptions-position body → 200
PATCH
/v3/streams/subscriptions/position
Update position subscription
patch-v3-streams-subscriptions-position body → 200
DELETE
/v3/streams/subscriptions/position
Delete position subscription
delete-v3-streams-subscriptions-position → 204
GET
/v3/streams/subscriptions/occupancy
Retrieve occupancy subscription
get-v3-streams-subscriptions-telemetry body → 200
POST
/v3/streams/subscriptions/occupancy
Create occupancy subscription
post-v3-streams-subscriptions-telemetry body → 200
PATCH
/v3/streams/subscriptions/occupancy
Update occupancy subscription
patch-v3-streams-subscriptions-telemetry body → 200
DELETE
/v3/streams/subscriptions/occupancy
Delete occupancy subscription
delete-v3-streams-subscriptions-telemetry → 204
POST
/v3/streams/subscriptions/position/channels
Add Channels to Position Subscription
post-v3-streams-subscriptions-type-channels body
DELETE
/v3/streams/subscriptions/position/channels
Remove Channels from Position Subscription
delete-v3-streams-subscriptions-type-channels body
POST
/v3/streams/subscriptions/telemetry/channels
Add Channels to Telemetry Subscription
post-v3-streams-subscriptions-type-channels body
DELETE
/v3/streams/subscriptions/telemetry/channels
Remove Channels from Telemetry Subscription
delete-v3-streams-subscriptions-type-channels body
POST
/v3/streams/subscriptions/occupancy/channels
Add Channels to Occupancy Subscription
post-v3-streams-subscriptions-type-channels body
DELETE
/v3/streams/subscriptions/occupancy/channels
Remove Channels from Occupancy Subscription
delete-v3-streams-subscriptions-type-channels body

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Stream-channel-kinesis (7 properties), Stream-channel-eventHub (7 properties), Stream-channel-watson (7 properties), Stream-post-eventhub (4 properties). Each schema is shown below with its type and property counts.

Stream-channel-kinesis
object
7 properties
Stream-patch-eventhub-channel
object
Update a Azure Event Hub stream channel IMPORTANT: when updating channel object, all properties are required.
3 properties
Stream-patch-watson-channel
object
Updates a IBM Watson stream channel IMPORTANT when updating channel properties, all properties are required.
3 properties
Stream-channel-eventHub
object
7 properties
Stream-patch-kinesis-channel
object
Updates a AWS Kinesis stream channel IMPORTANT: when updating channel object, all properties are required.
3 properties
Stream-post-eventhub
object
Create a Azure Event Hub stream channel
4 properties 2 required
Stream-post-watson
object
Create a IBM Watson stream channel
4 properties 2 required
Stream-post-kinesis
object
Creates a new AWS Kinesis stream channel
4 properties 2 required
Stream-channel-watson
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kontaktio-stream-api-openapi.yml Raw ↑

Other APIs Kontakt.io publishes across the network.

Kontakt.io Buildings API
AE Profile APIs.io
Kontakt.io Campuses API
AE Profile APIs.io
Kontakt.io Colocations API
AE Profile APIs.io
Kontakt.io Command API
AE Profile APIs.io
Kontakt.io Config API
AE Profile APIs.io
Kontakt.io Device (3rd party) API
AE Profile APIs.io
Kontakt.io Device API
AE Profile APIs.io
Kontakt.io Device (Portal Beam) API
AE Profile APIs.io
Kontakt.io Device tags API
AE Profile APIs.io
Kontakt.io Eddystone API
AE Profile APIs.io
Kontakt.io Entity Integration API
AE Profile APIs.io
Kontakt.io External Device API
AE Profile APIs.io
#Stream
← Back to K APIs
API Details
ID
kontaktio:kontaktio-stream-api
Base URL
https://dm-api.cloud.us.kontakt.io
Docs
https://developer.kontakt.io/docs/dev-ctr-device-api/a09dcbf0d03de-device-management-api-introduction
Provider
Kontakt.io
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=kontaktio-stream-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/kontaktio-stream-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 Kontakt.io Stream 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.