The REST API documentation for " Upload a Set of Timestamped Data" states that:
LIMIT: You can send a max of 10,000 data points per day per device. No matter if you split it into multiple sets or send all data once.
This limit can vary based on the plan you are using.
I am looking for information on how the limit varies with different plans?
What are the limits to use Blynk platform features
If you are using Business Plan, the limits below can be increased. Contact your support engineer.
HTTPS API Limits
Max request size: 2 MB (headers + request body)
Max number of file uploads (product/organization logos, firmware for shipment, data import) per user per day: 25
Max number of Export Data calls (/external/api/data/get ) per device per day (both UI and HTTPS API export): 10
Max number of the Update requests (/external/api/update ) per device per day: 500,000
https://docs.blynk.io/en/blynk.console/limits
Pete.
Thank you for this information. I did read this section, but I could not see a reference to the “10,000 data points per day per device.” limit which is only mentioned for this specific REST API call.
For instance, the page describing the closely related " Update Datastream Value" REST API call does not mention this limit. link
The only limit mentioned on the page you mention is under the Hardware section and states:
“Max number of data points per device per day you can import into the device: 10,000 points”
But the API call I am using is not importing data into the device and so this limit does not seem to be relevant to this scenario?
It might help if you explained more about what you’re trying to achieve and why, and the type of plan you currently have.
Pete.
This project uses the Particle System for data collection and processing and Blynk for the UI and potentially some event based logic.
I currently use “Update Datastream Value” endpoint. The documentation for this endpoint does not mention a 10,000 daily data point limit and so far I do not seem to have hit any daily limit.
Particle charges by “Data Operation” i.e. each webhook call to the Particle server and so if practical it is beneficial to batch up data points to send to Blynk to reduce the number of data operations.
I do not understand why the “Upload a Set of Timestamped Data” endpoint should be different to the “Update Datastream Value” endpoint in terms of limits. Maybe they both have the same daily limit, and it is just a documentation issue…
A separate issue which I am hoping will be addressed is that due to timing skew I think Blynk is occasionally receiving 2 consecutive data points out of order when I call the “Update Datastream Value” endpoint from the Particle device. This could be happening as this endpoint does not include a timestamp.
I am hoping that when I use the “Upload a Set of Timestamped Data” endpoint the data will be correctly displayed even if received “out of sequence”.
I am currently on the free plan and looking to understand whether the Plus or Pro plan will address this.
I don’t really know anything about Particle hardware or their ecosystem, but I assume that you’re using some form of GPRS communication, which needs to go via their server, rather than being able to communicate directly with Blynk via WiFi ?
How many datastreams are you updating, and what sort of frequency are you using for your data logging?
What type of Blynk subscription do you have, and are you using Raw data in your datastreams?
Pete.
Correct. One of the reasons for selecting the Particle platform is that it natively supports cellular data connections to its cloud server. Some of their boards come with either a sim slot or embedded sim.
I am updating 9 datastreams at different and variable data rates.
When there is an anomaly we read 4 of the sensors every 10s so that quickly creates a fair amount of data.
We need to view instantaneous readings so we are using raw data.
I am currently on the free plan and looking to understand whether the Plus or Pro plan might help address any limits we encounter.
Patrick
I didn’t think that the the Free plan allowed Raw data to be used in the datastream Advanced settings.
Doesn’t that conflict with this approach?…
Pete.
See attached. Seems to be working 
Not sure what the conflict would be? Raw displays data as sent:
"By default server stores only 1 data point per data stream per minute. In case you sent more than 1 point within 1 minute interval - value for that data stream will be averaged.
Raw data allows you to store every value that hardware sends."
Patrick
That’s strange.
If I log-in with my free account then I’m not allowed to turn on the “Save raw data” option for datastreams, it says that an upgrade is required…
Pete.
Hello, @pfischer. When did you create this datastream? And also you have FREE or PLUS plan? Looks like you have PLUS plan before, your first subscription was 25.11.2022
Apologies for this - I forgot I obviously signed up so I could access the raw data option and then had a MIB moment Yes I have the PLUS plan!
