@celigo/api-specs 0.2.151 → 0.2.152

package/dist/export.yml

@@ -6615,6 +6615,8 @@ components:
             Controls how the export requests subsequent pages when the API returns multi-page responses. The `method` field determines which companion fields are required and how each next page is requested. For the page, skip, and token methods, reference the matching pagination variable (`{{export.http.paging.page}}`, `{{export.http.paging.skip}}`, or `{{export.http.paging.token}}`) in the relative URI or request body — misconfigured pagination is a common cause of incomplete data retrieval.
 
             When this export is the first lookup of a builder-mode API with `pagination.enabled` set, it is that API's volume driver: saving the export (even unchanged) invalidates the API's issued cursors, so a caller mid-walk gets an empty final page, and removing `paging` is accepted on save but makes every call to the API fail with `400 api_pagination_source_not_paged` until paging is restored or the API's flag is turned off.
+
+            When a next page's response is identical to the previous one, paging stops: the export records an open error with code `page_response_error` ("Identical response received from next page request. No more page requests will be made.") and the run completes with the pages already read, so later pages are never exported. A request that doesn't change between pages produces this, as observed with `method: page` and the pagination variable missing from the relative URI and body; reference the variable so each request asks for the next page.
           x-celigo-ai-guidance:
             - Configuration object for navigating through multi-page API responses.
             - |-
@@ -17374,16 +17376,22 @@ components:
           properties:
             postData:
               type: object
-              description: Additional data for the export preview
+              description: |-
+                Delta window for this preview. Without it, a document preview renders
+                `{{lastExportDateTime}}` and `{{currentExportDateTime}}` as empty strings (observed on
+                HTTP and RDBMS exports), so the preview doesn't reflect the export's delta window. On an
+                HTTP export these strings are substituted exactly as given; other adaptors weren't
+                checked. On an export without `delta.dateFormat`, a real run renders both as ISO 8601 UTC
+                with milliseconds, so pass them in that form to preview the request such a run would send.
               properties:
                 currentExportDateTime:
                   type: string
-                  description: Current export date time (timestamp)
-                  example: '1751909419'
+                  description: Value `{{currentExportDateTime}}` renders as in this preview (the window's end).
+                  example: '2026-01-16T00:00:00.000Z'
                 lastExportDateTime:
                   type: string
-                  description: Last export date time (timestamp)
-                  example: '1742641523'
+                  description: Value `{{lastExportDateTime}}` renders as in this preview (the window's start).
+                  example: '2026-01-15T00:00:00.000Z'
     PreviewResponse:
       type: object
       description: Response body for export data preview

package/dist/tool.yml

@@ -31090,6 +31090,8 @@ components:
             Controls how the export requests subsequent pages when the API returns multi-page responses. The `method` field determines which companion fields are required and how each next page is requested. For the page, skip, and token methods, reference the matching pagination variable (`{{export.http.paging.page}}`, `{{export.http.paging.skip}}`, or `{{export.http.paging.token}}`) in the relative URI or request body — misconfigured pagination is a common cause of incomplete data retrieval.
 
             When this export is the first lookup of a builder-mode API with `pagination.enabled` set, it is that API's volume driver: saving the export (even unchanged) invalidates the API's issued cursors, so a caller mid-walk gets an empty final page, and removing `paging` is accepted on save but makes every call to the API fail with `400 api_pagination_source_not_paged` until paging is restored or the API's flag is turned off.
+
+            When a next page's response is identical to the previous one, paging stops: the export records an open error with code `page_response_error` ("Identical response received from next page request. No more page requests will be made.") and the run completes with the pages already read, so later pages are never exported. A request that doesn't change between pages produces this, as observed with `method: page` and the pagination variable missing from the relative URI and body; reference the variable so each request asks for the next page.
           x-celigo-ai-guidance:
             - Configuration object for navigating through multi-page API responses.
             - |-

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.151",
+  "version": "0.2.152",
   "private": false,
   "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
   "keywords": [

package/schemas.json

@@ -1,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "48f349ad",
+		"iasCommit": "6336cc85",
 		"generatedAt": "2026-10-21"
 	},
 	"roots": {