One transaction of Data Output is counted for each register read from a data bucket. Learn more about Getting Data.
You need to define the Data Output limit per month for each Profile where your applications are running.
Here is one example: a device reads one variable resulting in a response of 100 registers at every 10 minutes (100 temperature data points), the operations will result in 100 * 6 = 600 transactions per hour, which can then be converted by multiplying by 720 to result in 600 * 720 = 432,000 transactions/mo.
If the limit is exceeded, any attempt to read data (GET) will be denied for the rest of the month.
Accessing data from the dashboards, including when it's downloaded in .csv format from the widgets, does not count towards the general Data Output limit. Instead, a separate data output limit, specifically for dashboards, is consumed. For more information, please refer to our documentation on Data Output for Dashboards.
The system will also count data output when using the function 'Export Data' from the bucket.
Request limits are applied to a wide range of interactions within the platform, including activities such as reading and exporting data. Read more about our Rate Limits.