Callback integration

IP White listing

To make sure you receive callbacks, you should ensure that you've not blocking the following backend IP address range. Please refer to Classless Inter-Domain Routing (CIDR) notation for more details.

The current IP used are 
(thus any IP in to range)

These IPs may change (or be added to) in the future, and we will keep this page up to date.

Acknowledgement and retry policies

When receiving a callback, the client system must return an HTTP 2xx code within 10 seconds after receiving the request.

Because of the 10 seconds limit, it is recommended the client system manages request asynchronously. 

If the client system fails to answer the callback during this time, following retry policy is applied:

  • The 1st repetetion is sent 1min after the reception of the error of the previous request
  • The 2nd repetetion is sent 2min after the reception of the error of the previous request
  • The 3rd repetetion is sent 4min after the reception of the error of the previous request

If the client system reply too late, but the callback 10 seconds timeout has happened before, the callback will be re-emitted.

Therefore it is recommended the client system consider de-duplication, even in regular cases when the de-duplication is done at source because of such possible side effect.

Certificate Authority

General principles and explanation regarding certificate authority.

Difficulties to receive the callbacks transferred by the Sigfox Cloud

Sigfox does not trust certificates that are self-signed and so, not issued by a Certificate Authority (CA). Therefore, the Sigfox Cloud will not be able to transfer a callback to a server presenting a self-signed certificate.


What is a Certificate Authority?

A Certificate Authority (CA) is an entity that issues digital certificates.

The digital certificate certifies the ownership of a public key by the named subject of the certificate.

This allows others (relying parties) to rely upon signatures or assertions made by the private key that corresponds to the public key that is certified.

In this model of trust relationships, a CA is a trusted third party that is trusted by both the subject (owner) of the certificate and the party relying upon the certificate.

In the context of a website, when we use the term digital certificate we often refer to SSL certificates. The CA is the authority responsible for issuing SSL certificates publicly trusted by web browsers.

The CA has the responsibility to validate the entity behind an SSL certificate request and, upon successful validation, the ability to issue publicly trusted SSL certificates that will be accepted by web browsers.

Can't find what you're looking for ?

Have questions? Our worldwide Community of expert fans can answer them.
Have answers? Join the Community and help!

slack logo

Ask the community >