API rate limiting

For Cloud efficiency and security reasons, Sigfox is moving a step forward on API rate limiting, by setting upper bounds for some API endpoints use.

Please note that following HTTP response is to be integrated by the customer information system in case of exceeded rate : “HTTP 429: too many requests”.

API rate limiting does not apply to Paging mechanism (case when a response contains more than 100 entries).

You’ll find below the list of Endpoint with the new rate limitation and reason for change :



Reason for change

Rate limitation (max)

Available from<id>/messages

Retrieve a list of device messages (GET method)

Device messages are pushed by the Backend to the customer Information System via callback and/or connector.

1 request every second.<id>

Retrieve device information (GET method)

Update a device (PUT method)

Delete a device (DELETE method)

Device information page is not likely to change frequently (name, last seen etc).

1 request every 60 minutes. the computation of the coverage margins for multiple points, for each redundancy level (POST method)Optimization of system resources5 requests every 5 minutes.{jobId}Retrieve coverage predictions computation from asynchronous job status and results (GET method)Optimization of system resources10 requests every minute. the coverage margins for each redundancy level (GET and POST method)Optimization of system resources10 requests every minute.
Modify a list of devices
Transfer a list of devices
Modify a list of Base-Stations
Optimization/Protection of system ressources5 requests every 10 minutes.


Sigfox reserves the right to modify those limits without notice.

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 >