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 a new HTTP response will have to be integrated by the customer information system in case of exceeded rate : “HTTP 429: too many requests”.
You’ll find below the list of Endpoint with the new rate limitation and reason for change :
Endpoint | Description | Reason for change | Rate limitation (max) | Available from |
api.sigfox.com/v2/devices/<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. |
|
api.sigfox.com/v2/devices/<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. |
|
| api.sigfox.com/v2/coverages/global/predictions/bulk | Starting the computation of the coverage margins for multiple points, for each redundancy level (POST method) | Optimization of system resources | 5 requests every 5 minutes. |
|
| api.sigfox.com/v2/coverages/global/predictions/bulk/{jobId} | Retrieve coverage predictions computation from asynchronous job status and results (GET method) | Optimization of system resources | 10 requests every minute. | |
| api.sigfox.com/v2/coverages/global/predictions | Get the coverage margins for each redundancy level (GET and POST method) | Optimization of system resources | 10 requests every minute. | |
| api.sigfox.com/v2/devices/bulk api.sigfox.com/v2/devices/bulk/transfer api.sigfox.com/v2/base-stations/bulk | Modify a list of devices Transfer a list of devices Modify a list of Base-Stations | Optimization/Protection of system ressources | 5 requests every 10 minutes. |
|
Sigfox reserves the right to modify those limits without notice.
