Kontakt.io · Schema

NewExternalDevice

CompanyIoTRTLSHealthcareAsset TrackingLocationOccupancyBluetoothDevice ManagementTelemetrySensorsStreaming

Properties

Name Type Description
uniqueId string Unique ID of the new external device
mac string MAC address of the new external device
bleMac string BLE MAC address of the new external device
wifiMac string Wi-Fi MAC address of the new external device
eddystoneMac string Eddystone MAC address of the new external device
iBeaconMac string iBeacon MAC address of the new external device
productName string Product name of the new external device
productCode string Product code of the new external device
alias stringnull Alternative description for the Device, stored only on Kontakt.io backend - it's not possible to read this value via Bluetooth directly from the Device itself. In Device Management App represented as
tags array Comma-separated list of maximum 20 user-defined labels (no longer than 32 characters).
deploymentStatus object
category object
View JSON Schema on GitHub

JSON Schema

kontaktio-new-external-device-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/kontaktio/main/json-schema/kontaktio-new-external-device-schema.json",
  "title": "NewExternalDevice",
  "x-generated": "2026-10-12",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/kontaktio-external-device-api-openapi.yml#/components/schemas/NewExternalDevice",
  "type": "object",
  "properties": {
    "uniqueId": {
      "type": "string",
      "description": "Unique ID of the new external device"
    },
    "mac": {
      "type": "string",
      "description": "MAC address of the new external device"
    },
    "bleMac": {
      "type": "string",
      "description": "BLE MAC address of the new external device"
    },
    "wifiMac": {
      "type": "string",
      "description": "Wi-Fi MAC address of the new external device"
    },
    "eddystoneMac": {
      "type": "string",
      "description": "Eddystone MAC address of the new external device"
    },
    "iBeaconMac": {
      "type": "string",
      "description": "iBeacon MAC address of the new external device"
    },
    "productName": {
      "type": "string",
      "description": "Product name of the new external device"
    },
    "productCode": {
      "type": "string",
      "description": "Product code of the new external device"
    },
    "alias": {
      "type": [
        "string",
        "null"
      ],
      "description": "Alternative description for the Device, stored only on Kontakt.io backend - it's not possible to read this value via Bluetooth directly from the Device itself. In Device Management App represented as a Notes."
    },
    "tags": {
      "description": "Comma-separated list of maximum 20 user-defined labels (no longer than 32 characters).",
      "type": "array",
      "maxItems": 20,
      "uniqueItems": true,
      "items": {
        "type": "string",
        "maxLength": 32
      }
    },
    "deploymentStatus": {
      "$ref": "#/$defs/DeploymentStatus"
    },
    "category": {
      "$ref": "#/$defs/DeviceCategory"
    }
  },
  "$defs": {
    "DeploymentStatus": {
      "type": "string",
      "description": "Current deployment status of this device - e.g. whether is it deployed or not.\n\n`END_OF_LIFE` means the device is not going to be used anymore. Can occur for many reasons: battery dead, unserviceable device, contract with owning company was discontinued, etc.",
      "enum": [
        "TO_BE_DEPLOYED",
        "DEPLOYED",
        "END_OF_LIFE"
      ]
    },
    "DeviceCategory": {
      "type": "string",
      "enum": [
        "TAG",
        "INFRASTRUCTURE"
      ],
      "description": "Category of the device, whether it's a moving (TAG) or static (INFRASTRUCTURE) device."
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/kontaktio-new-external-device"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.