In this article I will show how to use the SecMQ platform in order to receive the SigFox messages on a MQTT queue signed and timestamped from the SecMQ broker.

SigFox callback

Every time a message is received from the SigFox network one or more callbacks can be triggered in order to send an email or move some data performing a GET or a POST or a PUT request on specified URL.

You can easily add a callback on the developer website, on the tab.

Just configure the callback in this way:

  • Channel —
  • Url pattern —
  • Use HTTP method —
  • Content type — application/json
  • Body — you can decide how to decode your data, an example is in the following box. REMEMBER your JSON need a field called “d” containing the device of the board.

Confirm this configuration and you will have a callback for each received message.


If you want receive the messages login to the SecMQ broker:

  • hostname —
  • username — sigfox
  • password — test
  • client id — sigfox_broker

The SecMQ platform will receive every message on the queue

where device is the id of your SigFox board (like written in the field d of the JSON)

You can receive timestamped and signed messages on the queue

Encoded in a JSON with the following format.


  • the field data contains the original message,
  • the field ots contains the OpenTimestamps proof of the original payload,
  • the field signature contains the signature of the data using the broker private key and
  • the field sigots contains the OpenTimestamps proof of the signature.

The test account is limited to some messages per minute and all messages are public.

Engineer, Bitcoiner, Data Scientist, IoT Expert and Tech Enthusiast. Co-founder of @scamcoinbot. Dad of @otsproofbot.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store