@celigo/api-specs 0.2.117 → 0.2.118

package/dist/sync.yml

@@ -2547,6 +2547,11 @@ paths:
         Returns the catalog of applications that can be used as the **source** of a sync — the system
         a sync extracts records from. Use the returned `id` as the source application when building a
         sync, and `category` to group the options in a picker.
+
+        The list is the set of applications that offer object-based extraction (a browsable catalog of
+        tables/objects, no export resource needed); HTTP connectors join it as they are enabled, so read
+        it at build time rather than caching it. An application missing from the list can still feed a
+        sync through export-backed datasets — see `GET /v1/di/metadata/connections/{_connectionId}/datasets`.
       tags:
         - Syncs
       operationId: listSyncSources
@@ -2565,7 +2570,10 @@ paths:
                   properties:
                     id:
                       type: string
-                      description: Application identifier to use as the sync source.
+                      description: |-
+                        Application identifier to use as the sync source. For HTTP-connector-backed
+                        sources this is the connector's display name, identical to `displayName`
+                        (for example `Stripe`, `Loop Returns`), not a lowercase key.
                       examples:
                         - salesforce
                     category:
@@ -2621,7 +2629,7 @@ paths:
                       category: Sales & Marketing
                     - id: netsuite
                       category: Sales & Marketing
-                    - id: stripe
+                    - id: Stripe
                       category: HTTP Connector
                       displayName: Stripe
                       source: httpConnectorMetadata
@@ -2740,7 +2748,14 @@ paths:
                 properties:
                   datasets:
                     type: array
-                    description: Tables/objects the source application exposes. Present unless `type` is `exports`.
+                    description: |-
+                      Tables/objects the source application exposes. Present unless `type` is `exports`.
+                      Empty — with a `200`, not an error — when the connection offers no object-based
+                      extraction: an HTTP connector that `GET /v1/di/metadata/sources` does not list, an
+                      HTTP connection with no connector, or a connection on a listed connector whose API
+                      or version is not the one the sources entry names (`httpConnector._apiId` /
+                      `_versionId`). Such a connection feeds a sync only through export-backed datasets
+                      (`exports`).
                     items:
                       type: object
                       description: One syncable table/object in the source application.
@@ -3878,8 +3893,13 @@ components:
               format: objectId
               x-celigo-refModel: connections
               description: |-
-                Connection to the source application. The application must be one of the
-                supported sync sources returned by `GET /v1/di/metadata/sources`.
+                Connection to the source application. Any application can be the source; the
+                connection's dataset mode is read from
+                `GET /v1/di/metadata/connections/{_connectionId}/datasets`: a non-empty
+                `datasets` array is object mode, an empty one means the connection feeds the
+                sync through export-backed datasets (`isExport: true`) only — including a
+                connection on a listed HTTP connector whose API or version is not the one
+                `GET /v1/di/metadata/sources` names.
               examples:
                 - 6a2a95909e994395f3c2a4e6
         destination:
@@ -4063,9 +4083,14 @@ components:
               format: objectId
               x-celigo-refModel: connections
               description: |-
-                Connection to the source application. The application must be one of the
-                supported sync sources returned by `GET /v1/di/metadata/sources`. Omitting
-                it fails with `422 missing_source_connection`.
+                Connection to the source application. Any application can be the source; the
+                connection's dataset mode is read from
+                `GET /v1/di/metadata/connections/{_connectionId}/datasets`: a non-empty
+                `datasets` array is object mode, an empty one means the connection feeds the
+                sync through export-backed datasets (`isExport: true`) only — including a
+                connection on a listed HTTP connector whose API or version is not the one
+                `GET /v1/di/metadata/sources` names. Omitting it fails with
+                `422 missing_source_connection`.
               examples:
                 - 6a2a95909e994395f3c2a4e6
         destination:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.117",
+  "version": "0.2.118",
   "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": "e8037248",
+		"iasCommit": "289007c3",
 		"generatedAt": "2026-10-16"
 	},
 	"roots": {