Skip to content

Layrz Protocol Specification

Layrz Protocol is our way to define how the devices should communicate with each other and/or with the cloud. It is a set of data packets, which are used to send and receive data between the devices and the cloud. The protocol is designed to be simple, efficient, and easy to use.

Protocol Overview

The specification defines the structure of the data packets, and the behavior of comunication of the devices with the server or with other device capable of that. However, you can implement the protocol in any way you want, as long as you follow the structure of the data packets.

Segmentation

The packets are segmented in different types, normally you can determine the type of the packet by the first letter of the packet name:

Packet TypeDescription
<A*>
Server packets, sent by the server to the device.
<P*>
Device packets, sent by the device to the server.
<T*>
Trips packets, used to data exchange between services
<I*>
AI packets, used to exchange AI messages between services

Now, if you want to integrate Layrz Protocol to your device, normally you will use the

<P*>
packets to send data from the device to the server, and the
<A*>
packets to receive data from the server.

Also, if you want to use our AI services, or trips services, you will use the

<I*>
packets to send AI data from the device to the server, and the
<T*>
packets to send trips data from the device to the server.

Devices using it

Device NameTypeManufacturer
Layrz LinkMobile app on Android and iOSLayrz LTD
Layrz HUB One Series 1HardwareLayrz LTD
Layrz HUB One Series 2HardwareLayrz LTD
Layrz BLEfier Series 1HardwareLayrz LTD

Services using it

Yes, Layrz Protocol is not only for devices, but also for services. The following services are using Layrz Protocol:

Service NameDeveloperDescriptionPackets used
Layrz Trips fetcherLayrz LTDThe Trips engine that allows data streaming when you request the trips for an specific Asset
<Pd>
,
<Ts>
and
<Te>
Layrz AILayrz LTDAI Chats API with standarized output, allowing multi-model conversations
<Im>