Kontakt.io
Kontakt.io is an AI-powered real-time location system (RTLS) and IoT platform for healthcare operations, founded in 2013 with offices in New York and Krakow. Its Kio Cloud platform combines BLE/UWB tags, badges, gateways and sensors with software for asset tracking, staff safety, patient flow, room and seat occupancy, and environmental telemetry. Developers integrate through the Kontakt.io Developer Center, which publishes four OpenAPI contracts: a Device Management API for provisioning, configuring and firmware-upgrading devices, a Location & Occupancy API for real-time and historical positions, presences, occupancy and telemetry plus a Streams API for event subscriptions, a Spaces API, and an Entity Management Integration API for batch import of staff and asset entities. Kio Cloud runs in US and UK regions and ships iOS and Android SDKs.
Kontakt.io publishes 30 APIs on the APIs.io network, including Buildings API, Campuses API, Colocations API, and 27 more. Tagged areas include Company, IoT, RTLS, Healthcare, and Asset Tracking.
The Kontakt.io catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Kontakt.io’s developer surface includes authentication, documentation, API reference, getting-started guide, support, engineering blog, signup flow, and 29 more developer resources.
What this lets a business do 2
Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →
Kin Score
APIs 30
Individual APIs this provider publishes, each with its own machine-readable definition.
Kontakt.io Buildings API
The Buildings API from Kontakt.io — 2 operation(s) for buildings.
Kontakt.io Campuses API
The Campuses API from Kontakt.io — 2 operation(s) for campuses.
Kontakt.io Colocations API
The Colocations API from Kontakt.io — 1 operation(s) for colocations.
Kontakt.io Command API
Commands are a special type of Configs used for initiating some management tasks, e.g. entering bootloader mode
Kontakt.io Config API
Pending configs represent new values for beacon settings that should be applied to actual devices via e.g. Kontakt.io Administration Apps. Creating a new config does not automat...
Kontakt.io Device (3rd party) API
NOTE: this set of endpoints has been superseded by External Devices functionality. These endpoints provide a way to integrate 3rd party Bluetooth-enabled scanning devices into K...
Kontakt.io Device API
The Device resource represents Kontakt.io devices assigned to a particular Kontakt.io Panel account, as well as devices shared with that account from different accounts.
Kontakt.io Device (Portal Beam) API
These endpoints are designed to assist with storing metadata associated with Portal Beams
Kontakt.io Device tags API
The device tags
Kontakt.io Eddystone API
Helper resources for working with Eddystone beacons
Kontakt.io Entity Integration API
The entity-integration API from Kontakt.io — 2 operation(s) for entity-integration.
Kontakt.io External Device API
External Device feature is a method of adding arbitrary external devices to the system. Such devices have MAC, unique id, and other virtual attributes, but they cannot be manage...
Kontakt.io Firmware API
Firmware resources
Kontakt.io Floors API
The Floors API from Kontakt.io — 1 operation(s) for floors.
Kontakt.io Footfall Spaces API
The Footfall Spaces API from Kontakt.io — 1 operation(s) for footfall spaces.
Kontakt.io Gateways API
The Gateways API from Kontakt.io — 1 operation(s) for gateways.
Kontakt.io Location Images API
The Location Images API from Kontakt.io — 1 operation(s) for location images.
Kontakt.io Manager API
Managers represent user accounts that can manage Kontakt.io Devices. Everyone can freely create an account on [Kontakt.io Web Panel](https://panel.kontakt.io) and then use it to...
Kontakt.io Occupancy API
The Occupancy API from Kontakt.io — 1 operation(s) for occupancy.
Kontakt.io Occupancy: Footfall API
The Occupancy: Footfall API from Kontakt.io — 2 operation(s) for occupancy: footfall.
Kontakt.io Occupancy: Room API
The Occupancy: Room API from Kontakt.io — 2 operation(s) for occupancy: room.
Kontakt.io Occupancy: Seats API
The Occupancy: Seats API from Kontakt.io — 2 operation(s) for occupancy: seats.
Kontakt.io Order API
An Order represents all devices that have been purchased in Kontakt.io Web Store in a single transaction. Before these devices can be used with Kontakt.io platform, they need to...
Kontakt.io Positions API
The Positions API from Kontakt.io — 2 operation(s) for positions.
Kontakt.io Presences API
The Presences API from Kontakt.io — 2 operation(s) for presences.
Kontakt.io Proximities API
List of iBeacon Proximity UUIDs used on beacons belonging to a Manager
Kontakt.io Rooms API
The Rooms API from Kontakt.io — 2 operation(s) for rooms.
Kontakt.io Spaces API
The Spaces API from Kontakt.io — 2 operation(s) for spaces.
Kontakt.io Stream API
The Stream API from Kontakt.io — 9 operation(s) for stream.
Kontakt.io Telemetry API
The Telemetry API from Kontakt.io — 1 operation(s) for telemetry.
Scroll for all 30
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Kontakt.io MCP Server
MCP SERVERPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Kontaktio Rate Limits
RATE LIMITSEvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Kontaktio Streams Events
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.