Supported Connector Types

UnaConnect supports both low-level protocols and dedicated solutions for you to integrate and connect easily to your platform or infrastructure. If you have sufficient permissions, you will be able to create and configure the connectors by simply completing the required input fields in the Connectors page.
To simplify the integration of the messages into various solutions such as IoT dashboards, UnaConnect also includes custom-made connectors:
  • Splunk
  • AWS IoT
  • Others such as Microsoft PowerBI will be added in the future
By offering the open-standard protocols such as HTTPS, MQTT and UDP, UnaConnect is natively compliant with most of the IoT dashboards and solutions on the market. The following sections will introduce more details on HTTP/HTTPS - the most common protocol used.

The HTTP/HTTPS Connector has several customizable elements:
  • Headers: The header of the request allows you to add Authorization header, an api-key or any headers.
  • Method: UnaConnect is set at "POST" by default, however "GET" is also supported.
  • URL: The destination for UnaConnect to send the data.
  • Body: You can define a specific format for your message body.
  • URL Query String or URL Search Params: Parameters are added to the URL to enter as a JSON. For example: &device=12345&timestamp=123124.
We recommend you define the following parameters:
Headers: {"Authorization":"ABCDEF1233456789"}
Format: JSON
Body: {"deviceId":"{deviceId}","deviceType":"{deviceType}","deviceName":"{deviceName}","groupId":"{groupId}","dataType":"{dataType}","data":{data},"timestamp":{timestamp}}
URL Query String: {"deviceId":"{deviceId}","timestamp":{timestamp}}
You will receive the data on your end user platform as:

Content-Type: application/json
  "deviceId": "sigfox-DEVICE_ID",
  "deviceType": "deviceType1",
  "deviceName": "UnaSensor A in Office A",
  "groupId": "1234567890987654321",
  "dataType": "DATA",
  "data": {
    "mode": "timer",
    "temperature": 27.52,
    "humidity": 62.62
  "timestamp": 1621925764

Each of these elements can integrate variables, however they must follow the format: {variable} to be used. For example, if the connector is linked to an UnaSense temperature sensor, {temperature} will be replaced by the current temperature.
⚠️ The variables must be a string.
The following variables are always available:
  • Headers: The header of the request allows you to add Authorization header, an api-key or any headers.
  • {deviceId} string representing the id of the device
  • {timestamp} number representing when the data was recorded in seconds (eg. 1639600000)
  • {dateTime} string representing when the data was recorded in ISO8601 format (eg "2021-12-15T10:00:00.000Z")
  • {deviceName} string representing the name of the device
  • {groupId} string representing the ID of the Group where the device belongs to
  • {dataType} can be "DATA", "GEOLOC", "EVENT", "TELEMETRY"
  • {deviceType} string representing the type of the device eg. "unasenseV1"
  • {data} which contains all the decoded data as an object
  • {configuration} which is the configuration of the device when UnaConnect received the message
  • {information} which contains all the extra information as an object
If available in the message and according to the data type, you can receive:
Data Type = DATA
  • {mode} if available
  • {temperature} if available
  • {humidity} if available
  • {motionCount} if available
Data Type = GEOLOC
  • {radius}
  • {lat}
  • {lng}
  • {lastLocation}