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 automatically change anything on a real beacon.
Kontakt.io Config 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 Config. 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 8 operations across 8 paths, and defines 38 schemas. It is described by OpenAPI 3.2.0, at version 10.
Requests are made against 2 base URLs: https://dm-api.cloud.us.kontakt.io, https://dm-api.cloud.uk.kontakt.io.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Kontakt.io Config API declares
3 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (bearer_token).
An API key is passed in the header as Api-Key (api_key).
An API key is passed in the header as Api-Key (management_api_key).
By default, every request must be authenticated.
bearer_token— Provide a JWT in the Authorization: Bearer header. This is the standard authentication method for all API requests. Obtain a token via the OAuth2 Client Creden…api_key— Deprecated — do not use for new integrations. This method exists solely for backward compatibility and will be removed in a future release. Use JWT Bearer toke…management_api_key— Special management API Key with additional privileges used by authorized users.
Paths & Operations 8
Across 8 paths, the API surfaces 8 operations — 4 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.
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 automatic…
Schemas 38
The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are ConfigBle (12 properties), SearchMeta (9 properties), LocalAlertingSettings (9 properties), PowerSavingSettings (9 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Kontakt.io 12
Other APIs Kontakt.io publishes across the network.
This is an independent, third-party profile of Kontakt.io Config 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.