Overview

This guide provides instructions for configuring your Sigfox Backend to forward device data to the IoT Pro Software Platform.

Prerequisites

• Administrative access to a Sigfox Backend

• The IoT Pro application ID (app_id) for the target application. This can be fetched from Applications.

Device Type Configuration

Organization Strategy

Create a separate Device Type for each IoT Pro application to:

• Maintain logical separation of device groups

• Enable application-specific integration endpoints

• Simplify device management and troubleshooting

• Support independent configuration and monitoring

Naming Convention

Use the following naming pattern for new Device Types:

{YYYYMMDD}_IoTPro_{app_id}_IoTSolutions_Callback

Example: 20260623_IoTPro_3_IoTSolutions_Callback

Callback Configuration

For each Device Type, create a new Custom Callback with the following settings::

• Type: Data Uplink

• Channel: URL

• URL pattern: http://57.129.34.12:8900/iotpro/sigfox?device_param_application_id={app_id}

• Use HTTP method: POST

• Content type: application/json

• Body: The uplink payload forwarded to IoT Pro Platform must use this format:

{ "timestamp" : {time}, "device" : "{device}", "seq_number" : "{seqNumber}", "data" : "{data}" }

Registering Devices

When adding a new device to a Device Type, register it as a prototype for the End Product Certificate (PC), rather than under a final certified product profile, until this becomes available.