From e0c37e87009fabeecd040564f3c20ce53cd56ac5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Luk=C3=A1=C5=A1=20K=C5=99ivka?= Date: Tue, 7 Jan 2025 21:22:19 +0100 Subject: [PATCH] fix: correct limits for dataset get items endpont --- openapi/paths/datasets/datasets@{datasetId}@items.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/openapi/paths/datasets/datasets@{datasetId}@items.yaml b/openapi/paths/datasets/datasets@{datasetId}@items.yaml index 1bd4312..f12a1f1 100644 --- a/openapi/paths/datasets/datasets@{datasetId}@items.yaml +++ b/openapi/paths/datasets/datasets@{datasetId}@items.yaml @@ -54,7 +54,7 @@ get: - Note that CSV, XLSX and HTML tables are limited to 500 columns and the column names cannot be longer than 200 characters. + Note that CSV, XLSX and HTML tables are limited to 2000 columns and the column names cannot be longer than 200 characters. JSON, XML and RSS formats do not have such restrictions. @@ -185,7 +185,7 @@ get: The pagination is always performed with the granularity of a single item, regardless whether unwind parameter was provided. By default, the **Items** in the response are sorted by the time they were stored to the database, therefore you can use pagination to incrementally fetch the items as they are being added. - The maximum number of items that will be returned in a single API call is limited to 250,000. + No limit exists to how many items can be returned in one response.