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

Kontakt.io Device (Portal Beam) API

These endpoints are designed to assist with storing metadata associated with Portal Beams

Kontakt.io Device (Portal Beam) 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 Device (Portal Beam). 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 5 operations across 2 paths, and defines 10 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.

5 operations 2 paths 10 schemas 1 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
10
Base URL
https://dm-api.cloud.us.kontakt.io
Authentication
HTTP Bearer, API Key, API Key
Contact
Terms of Service
Resource Areas
1

Authentication & Security 3

Kontakt.io Device (Portal Beam) 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 5

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

Device (Portal Beam) 5

These endpoints are designed to assist with storing metadata associated with Portal Beams

POST
/portalbeam/image
Store or erase Portal Beam calibration image
body → 204401404422
GET
/portalbeam/image
List images for one or more Portal Beams
1 param → 200401404422
POST
/portalbeam/stitching
Create or update stitching between two devices
body → 204401404422
GET
/portalbeam/stitching
Get stitching by uniqueIds
1 param → 200401404422
DELETE
/portalbeam/stitching
Delete stitching between two selected beams
2 params → 204400

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are ApiError (5 properties), OccupancyImage (5 properties), StitchingImage (3 properties), StitchingPose (3 properties). Each schema is shown below with its type and property counts.

ApiError
object
5 properties
Polygon
object
2 properties
StitchingPair
object
2 properties 2 required
StitchingPose
object
3 properties 3 required
StitchingPivotLocal
object
Pivot (rotation point) of the image in the device image's local coordinates.
2 properties 2 required
StitchingImage
object
3 properties 3 required
StitchingPivotWorld
object
Pivot (rotation point) of the image in the world coordinates that are shared between stitched devices. Origin is top left corner.
2 properties 2 required
StitchingConfig
object
2 properties 2 required
OccupancyImage
object
Occupancy image taken from occupancy-capable device.
5 properties
StitchedDevice
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kontaktio-device-portal-beam-api-openapi.yml Raw ↑

Other APIs Kontakt.io publishes across the network.

Kontakt.io Buildings API
Kontakt.io Campuses API
Kontakt.io Colocations API
Kontakt.io Command API
Kontakt.io Config API
Kontakt.io Device (3rd party) API
Kontakt.io Device API
Kontakt.io Device tags API
Kontakt.io Eddystone API
Kontakt.io Entity Integration API
Kontakt.io External Device API
Kontakt.io Firmware API
Where this information came from

This is an independent, third-party profile of Kontakt.io Device (Portal Beam) 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.