The Sigfox Cloud can automatically forward some events using Callback services.
Callback services send custom requests named "Callback" containing device data, along with other variables, to a given server/platform.
Depending on callback service, a callback is triggered by a specific event occurring on the Sigfox Cloud.
The Sigfox Cloud provides 2 main categories of Callback services:
- Data and Service Callback services triggered by a network event (device message or device communication behavior). Those callback services are configured at device type level.
- Event Callback service triggered by an event on the device's cloud entity (its lifecycle, communication status, and subscription) and configured at group level
The available Callback services are listed below. All Callback services are optional, we recommend using those that are the most relevant to your own integration.
Multiple callbacks for the same service are allowed, but Sigfox might restrict this possibility in case of abuse.
Send the uplink Message received on the Sigfox cloud
|Reception of the first frame|
Send the uplink Message received on the Sigfox cloud and retrieve a downlink answer from the third-party server
Send device battery and temperature information received for modules allowing Out-Of-Band status messages.
Send the network acknowledgment confirming the downlink message emission.
Service messages (battery, number of repeated messages,…) only applicable for repeater devices.
Send the uplink Message received on the Sigfox cloud with metadata:
|25 seconds after Reception of the first frame|
|ERROR||Send an alert when a device does not comply with the keep alive delay set at device type level.||Device Type Setting|
Send alerts that are triggered upon event occurrence (see Event types)
You can configure a callback service to forward events directly to your servers using either Custom callbacks (see Custom callback creation) or callbacks for one of the 4 platforms integrated with Sigfox's backend (see Callback and Connectors article).
In such cases, some Callbacks services might be restricted, as all callbacks services are not available to all platforms, for more information please refer to the Partner callback creation article.