Data restrictions FAQ

A “16 MB maximum data capacity” is listed. Does this data capacity restriction
refer to the data capacity limit for data stored to a single resource path?
The 16 MB data capacity restriction is a limit to the amount of data written to
the Body text with a single API registration for a resource. It is not a resource
path restriction.
The maximum data capacity for a single registration of JSON data is listed as 16MB. Do any other restrictions apply?
Depending on its contents, you may not be able to register some JSON data evenif it is within the above-mentioned size restriction.
JSON data is converted to BSON format when saving within the IoT-PF. You will not be able to store data that exceeds 16 MB after being converted to BSON format.
・More information about JSON-BSON size conversions can be found at:  http://bsonspec.org/spec.html 
We recommend checking this URL when dealing with large data sizes.
Is there a limit to the number of data items that can be acquired with a single API use?
If such restrictions apply, how should we continue to acquire data with subsequent API uses?
The most amount of data that can be acquired with a single API use is 1,000.
Even if the amount of data is less than 1,000 items, you will not be able to acquire all data with a single API use when the total size of the data being acquired exceeds 16 MB.
You can acquire data from the 1,000th data item onwards by using the skipvariable.
For example, if 2,000 data items are registered, use “<Resourcepath>?$top=1000&$skip=1000” to acquire data items 1,001 to 2,000.
You can also retrieve items by specifying conditions in a filter search.