Data ingestion is limited in two ways:
Token limit: Determines how many requests can you send using the same auth token.
Global account limit (or "Throughput"): Determines how many dots can you send across all tokens in your account, in a time window of 1 hour.
Here we explain each type of limit:
Token limit
You can send up to 4 requests per second per token, each one can have a maximum of 10,000 bytes. This is valid across all supported protocols — HTTP, MQTT, and TCP & UDP.
Nonetheless, there are some applications, such as the following examples, that require account or Organizational tokens with extended limits and different time windows for data ingestion:
Centralize data from several devices from a Device management platform (i.e., LoRaWAN Network Servers, Particle Cloud, Sigfox backend), from which a single account or Organizational token is used.
Centralize data from several devices in a single gateway, from which a single account or Organizational token is used.
For those kinds of applications, you can edit the rate limit and time window of the account or Organizational tokens to be used. Please note that these rate limits don’t apply to Device tokens as they’re fixed to 4 request per second.
Custom API rate limits are available from the Industrial license and above. Each plan has its own rate limit and time window options following the below tables:
Professional license:
Time window (minutes) | Rate limit (requests in time window) |
1 second | 1, 2, 4 |
1 | 5, 10, 30, 60 |
5 | 10, 30, 90, 180 |
Industrial license:
Time window (minutes) | Rate limit (requests in time window) |
1 second (default) | 1, 2, 4 |
1 | 5, 10, 30, 60 |
5 | 10, 30, 90, 180 |
15 | 90, 180, 240, 480 |
Time window (minutes) | Rate limit (requests in time window) |
1 second (default) | 1, 2, 4 |
1 | 5, 10, 30, 60 |
5 | 10, 30, 90, 180 |
15 | 90, 180, 240, 480 |
30 | 90, 240, 480, 720 |
60 | 90, 240, 480, 720, 960 |
Editing account tokens rate limit
To edit the rate limit of an account token just press the edit button from the API Credentials section under the profile settings. Then, choose the limit and time window that best fit your application.
Editing Organizational tokens rate limit
To edit the rate limit of an organizational token just press the edit button from the tokens section of the Organization's settings. Then, choose the limit and time window that best fit your application.
What if I need a rate limit that is higher than the available options?
Often times, you might need to send data from many devices, from a single source, be it a physical gateway, or a cloud broker (i.e Particle, LoRaWAN Network Servers, etc.). If none of the above options work for you, please reach out to us in order to have your use case analyzed for either a custom rate limit per token, or a dedicated cloud deployment.
Global account limit ("Throughput")
Ubidots plans are designed to include enough throughput for most IoT applications, including a max burst allowance per hour, in order to accept occasional peaks of data ingestion:
Plan | Sustained dots per second | Max burst in a 1-hour window |
Professional | 6 dots/s | 12 dots/s |
Industrial | 20 dots/s | 40 dots/s |
Enterprise I | 50 dots/s | 100 dots/s |
Enterprise II | 100 dots/s | 200 dots/s |
Enterprise III | 200 dots/s | 400 dots/s |
Enterprise III - Private deployment | Up to 1,000 dots/s depending on server size. | Up to 2,000 dots/s depending on server size. |