This document describes the IoT-A Representational State Transfer (REST) API rate limits for enterprises.
The rate limits described in this document are only applied on the IoT-A cloud environment users.
The rate limit indicates the maximum number of allowed API requests in a given time frame. If an API path has a rate limit, the rate limit information is displayed in the 200 and the 429 response headers. When the rate limit is exceeded, the 429 Too Many Requests response is returned.
The following table lists the rate limit response headers:
Name |
Description |
Type |
|---|---|---|
X-RateLimit-Limit-Second |
The maximum number of requests allowed in a second. |
Integer |
X-RateLimit-Limit-Minute |
The maximum number of requests allowed in a minute. |
Integer |
|
X-RateLimit-Remaining-Second
|
The number of requests remaining in a second. |
Integer |
| X-RateLimit-Remaining-Minute | The number of requests remaining in a minute. |
Integer |
Note: The iot/api/eco and iot/api/eim-info API paths return these headers in the 200 response only. The 429 Too Many Requests response for these paths does not include rate limit headers. When you receive a 429 response, wait until the next second before you retry. If you still receive a 429 response, wait until the next minute.
The following table lists the default rate limit for each corresponding API path:
API path |
Maximum Requests per Second |
Maximum Requests per Minute |
|---|---|---|
| iot/api/auth | 5 |
60 |
| iot/api/business-analytics-service/v1/aggregated-traffic-usages/top-usage-subscriptions | 5 |
50 |
| iot/api/business-analytics-service/v1/invoices | 5 |
50 |
| iot/api/business-analytics-service/v1/reports | 5 |
50 |
| iot/api/business-analytics-service/v1/usages | 5 |
50 |
| iot/api/business-automation/triggered-actions | 10 |
100 |
| iot/api/business-automation/rulesets | 10 |
100 |
| iot/api/consumer-connectivity | 10 |
100 |
| iot/api/ecm/enterprises | 10 |
100 |
| iot/api/eco | 10 |
100 |
| iot/api/eim-info | 10 |
100 |
| iot/api/localization-tables | 10 |
100 |
| iot/api/euicc-agreements | 10 |
100 |
| iot/api/activation-codes | 2 |
20 |
| iot/api/subscriptions/imsi-ranges | 10 |
100 |
| iot/api/subscriptions/msisdn-pools | 10 |
100 |
| iot/api/subscriptions/msisdn-ranges | 10 |
100 |
| iot/api/subscriptions/number-schemes | 10 |
100 |
| iot/api/diagnostic-analytics/signaling-aggregations/traffic-usages | 10 |
100 |
| iot/api/apns | 5 |
50 |
| iot/api/esm-context-qos | 5 |
50 |
| iot/api/esm-contexts | 5 |
50 |
| iot/api/esm-profile-qos | 5 |
50 |
| iot/api/esm-profiles | 5 |
50 |
| iot/api/network-nodes | 5 |
50 |
| iot/api/operator-networks | 5 |
50 |
| iot/api/pdp-context-profiles | 5 |
50 |
| iot/api/pdp-context-qos | 5 |
50 |
| iot/api/roaming-profiles-2g3g | 5 |
50 |
| iot/api/roaming-profiles-4g | 5 |
50 |
| iot/api/shared-bundles | 15 |
300 |
| iot/api/file-shares | 5 |
50 |
| iot/api/specifications | 5 |
50 |
| iot/api/sica/subscriptions/sim-orders | 10 |
100 |
| iot/api/subscriptions/locations | 15 |
300 |
| iot/api/subscriptions | 10 |
100 |
| iot/api/subscriptions/details | 10 |
150 |
| iot/api/subscriptions/devices | 10 |
100 |
| /iot/api/subscriptions/devices/ | 20 |
500 |
| iot/api/sica/subscriptions/regions | 10 |
100 |
| iot/api/sica/subscriptions/sim-resource | 30 |
1000 |
| iot/api/sica/subscriptions/sim-resources | 10 |
100 |
| iot/api/sica/subscriptions/sims | 10 |
150 |
| iot/api/sica/subscriptions/requests | 10 |
100 |
| iot/api/xdr/events | 5 |
25 |
| iot/api/xdr/reports | 5 |
25 |
Note: iot/api/ts/incidents rate limits are not included in the table because of Incident Management API planned deprecation.
0 Comments