Kontakt.io · Schema
Position Device History
Historical location (position) information for a particular device.
CompanyIoTRTLSHealthcareAsset TrackingLocationOccupancyBluetoothDevice ManagementTelemetrySensorsStreaming
Properties
| Name | Type | Description |
|---|---|---|
| content | array |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/kontaktio/main/json-schema/kontaktio-position-device-history-schema.json",
"title": "Position Device History",
"description": "Historical location (position) information for a particular device.",
"x-generated": "2026-10-12",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/kontaktio-positions-api-openapi.yml#/components/schemas/Position-Device-History",
"type": "object",
"properties": {
"content": {
"type": "array",
"items": {
"type": "object",
"properties": {
"trackingId": {
"type": "string",
"description": "MAC address of the device."
},
"level": {
"type": "string",
"x-stoplight": {
"id": "ffs1lpcr0w3gl"
},
"description": "Reference purposes only; floor."
},
"timestamp": {
"type": "string",
"description": "Timestamp of device location. ISO 8601 UTC format (yyyy-mm-ddThh:mm:sssz)."
},
"floorId": {
"type": "integer",
"description": "ID of the floor location."
},
"roomId": {
"type": "integer",
"description": "ID of the room location."
},
"x": {
"type": "number",
"description": "X coordinate position."
},
"y": {
"type": "number",
"description": "Y coordinate position."
},
"origin": {
"type": "string",
"description": "Identifies the source of the position calculation when the position is calculated by a third-party."
},
"lost": {
"type": "boolean",
"description": "Lost flag. Set to true when the device is out of range."
},
"irAssisted": {
"type": "boolean",
"description": "Flag that indicates whether device was located using IR technology."
},
"moving": {
"type": "boolean",
"description": "Flag that indicates whether device was moving when the position was calculated."
},
"roomName": {
"type": "string",
"description": "Name of the room location."
},
"floorName": {
"type": "string",
"description": "Name of the floor location."
},
"buildingId": {
"type": "integer",
"description": "ID of the building location."
},
"buildingName": {
"type": "string",
"description": "Name of the building location."
},
"campusId": {
"type": "integer",
"description": "ID of the campus location."
},
"campusName": {
"type": "string",
"description": "Name of the campus location."
}
}
}
}
}
}
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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/kontaktio-position-device-history"
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.