Skip to content

Data Retrieval

When an integration is configured on a device or a group, all data received from those devices will be redirected to the endpoint specified in the integration. For more information on how to add an integration to a device, refer to section: Register Your Device.

An integration consists of a name and an HTTP/S REST endpoint (e.g., https://production.example.com/sensors). You can also configure it to include metadata or just the raw payload.

The FOSSA Network will issue a POST request to the configured endpoint whenever new data is received.

Your server should expect the following structure depending if you selected to include metadata or not:

With metadata

POST https://production.example.com/sensors
header "Content-Type": "application/json"

{
  "mac": "01504B004800", 
  "queue_timestamp": 1760091985,
  "sat_timestamp": 1760092185
  "rssi": -87,
  "message": "aGVsbG8gd29ybGQ=", 
  "nodeId": "67dd4ee23f647d4b31e0f8c8",
  "source": "satellite"
}

Parameters description

  • mac: The MAC address of the device in hexadecimal format without colons.
    Example: 01504B004800
  • queue_timestamp: The Unix timestamp (in seconds) when the IoT packet was enqueued on the device.
  • sat_timestamp: The Unix timestamp (in seconds) when the IoT packet was received by the satellite.
  • rssi: The ambient RSSI value measured by the device at the time of packet enqueueing, in dBm.
  • message: The payload of the IoT packet, encoded in base64.
  • nodeId: The device ID on the API, which can be used for further queries to the REST API.
  • source: The source of the message. It can be satellite if the message arrived through the satellite network or cellular if it arrived though the cellular network.

Without metadata

Without metadata the payload will be sent in the body of the request with no extra parameters as shown bellow:

POST https://production.example.com/sensors
header "Content-Type": "Application/octet-stream"

<binary representation of the raw payload>