Last updated on September 16th, 2024
The data is processed and pushed to your endpoint in JSON format.
Distribution formats | Format name | Type of message |
JSON formats | Raw type Basic format V1.1 | For all messages |
Raw type Expert format V1.1 | ||
Processed type Basic | For processed messages from 28-bit address devices with a codec declared | |
Processed type Expert | ||
Location type Kinéis format V2.1 | For native location (Doppler) messages | |
ThingsBoard JSON formats | Thingsboard raw type Basic V1.1 | For all messages |
Thingsboard processed type Basic | For processed messages from 28-bit address devices with a codec declared | |
Thingsboard processed type Expert | ||
Thingsboard location format V2 | For native location (Doppler) messages | |
Live Objects JSON formats | Live objects raw type Basic V1.1 | For all messages |
Live objects processed type Basic | For processed messages from 28-bit address devices with a codec declared | |
Live objects location format V2 | For native location (Doppler) messages |
Change management
Kinéis uses versioning to ensure backward compatibility for data formats, following the structure <Major>
.<Minor>
.
Here's how the versioning works:
- Minor version: Indicates the addition of new fields to the existing data format. Customers should ensure their systems can handle these new fields. Kinéis will support only the latest minor version within each supported major version.
- Major version: Indicates a significant change in the data structure, such as the removal of fields. These changes may break compatibility with previous versions. Kinéis will provide a transition period to allow customers time to migrate to the new major format.
This versioning approach helps maintain stability while allowing for necessary updates.