Protocol Configuration

One significant capability of monoZ:Link is its ability to create routes, which allow you to transfer data from Notehub to various platforms including public clouds like AWS, Azure, or dashboard services like Centra-IoT or Thingsboard. You can also send data to custom HTTP or MQTT endpoints. The tutorial below explains how to send data to several popular services and provides guidance on building visualizations using that data.

Wehbook

In this guide we assume you have already have an external service ready to receive data from monoZ:Link.

1. Navigate to “Configuration” and click on “Add Configuration” from the top right corner.

2. Choose “Webhook” as destination protocol.

3. Add the destination server details and create the configurations.

   1. Specify MQTT in the Source protocol

   2. Enter your configuration name

   3. Enter suitable description for the configuration

   4. Enter the HTTP/HTTPS URL for the destination Server

   5. Select the Authorization method under the Parameters

   6. If you wish to give a custom header (e.g., group name, etc.) add your custom Header

   7. Choose Between ICCID or Topic to be sent along with the payload to the destination server

   8. Upon Submit the configuration shall be created

Webhook Data Format

monoz:Link pushes data to the specified server in the following format.When multiple packets arrive per second, data output will be output in 10 packets for each registered group. Upon data push to the specified server, the server will wait for a response for up to 90 seconds. In case of no response from server, monoZ:Link will retry the data push immediately and if the retry is unsuccessful, the data will be discarded without further attempts. If the database function is enabled, the data will be stored as failed data.

Format:

Field	Item	Remarks
Method	Post
API URL	URL	Customer defined POST API URL
Header	Authentication	This will vary depending on the security method specified in monozLink. Security can be specified as Basic, BearerToken, or API Key
	Content Type	application/json
	content-length	Auto Calculation
	host	Auto provision
	Custom Header	User specified customer header
Body	ICCID	Device ICCID registered in monoZ:Link
		When a user specifies a topic in monZ:Link setting, the topic value is provided and the field name is changed from "ICCID" to "Topic".
	Timestamp	The timestamp when the data was sent from monoZ:Link (ISO:8601 format with milliseconds)
	Payload	Raw data sent by GW device, user needs to parse, extract and decode the required data

Example 1:

Field	Item
API URL	URL
Header	Authentication: Basic dGVzdDoxMjM0NTY3ODk=
	Content-Type: application/json; charset=utf-8
	content-length: 102
	host: xxxxyyyxxxyyyxxx.net
	1_Area: Tokyo
Body	ICCID: 897612653856781234
	Timestamp: 2023-10-16T09:17:32.8383516Z
	Payload: ABC

Example 2: When multiple packets are receiverd in 1 second:

Field	Item
API URL	URL
Header	Authentication: Basic dGVzdDoxMjM0NTY3ODk=
	Content-Type: application/json; charset=utf-8
	content-length: 102
	host: xxxxyyyxxxyyyxxx.net
	1_Area: Tokyo
Body	[ { "ICCID": 897612653856781234, "Timestamp": "2023-10-16T09:17:32.1233516Z", "Payload": "ABC" }, { "ICCID": 897612653856787890, "Timestamp": "2023-10-16T09:17:32.8383516Z", "Payload": "123" } ]