@celigo/api-specs 0.2.92 → 0.2.94

package/dist/integration.yml

@@ -4213,9 +4213,10 @@ components:
         syncs:
           type: boolean
           description: |-
-            Indicates whether this integration uses Sync resources.
-
-            Typically system-managed.
+            When true, the integration is a container for Celigo Sync resources — set it on
+            `POST /v1/integrations` before creating syncs in it (`POST /v1/syncs` into an
+            integration without it fails with `422 integration_not_for_sync`). Fixed at creation:
+            `PUT /v1/integrations/{_id}` ignores the field in both directions.
         aliases:
           type: array
           description: Named aliases that map to specific resources within the integration.

package/dist/mcp-server.yml

@@ -6421,11 +6421,23 @@ components:
           description: |-
             HTTP connector (pre-built application template) this connection is linked to. Linking
             lets exports and imports on the connection pick endpoints from the connector's catalog and
-            drives the `assistant` form in the UI. An id that does not resolve to an accessible
-            connector is dropped from the saved document rather than rejected — read the response back
-            to confirm the link took.
+            drives the `assistant` form in the UI. The link is resolved server-side on create and on
+            any update that changes `assistant` or a connector id, and the result overwrites
+            `_httpConnectorId`, `_httpConnectorApiId` and `_httpConnectorVersionId`: an id that does
+            not resolve to an accessible connector is dropped rather than rejected, and when the
+            top-level `assistant` names an application with a legacy adaptor (the connector's
+            `legacyId`, e.g. `shopify`) the connector resolved from that slug replaces the id you sent
+            and a sent `_httpConnectorVersionId` is dropped. Read the response back to confirm the
+            link took.
           examples:
             - 5d8f6a2b9c1e4f00112a3b4c
+          x-celigo-ai-guidance:
+            - |-
+              To link an Azure Data Lake Storage Gen2 connection to its connector, send
+              `_httpConnectorId` and `_httpConnectorVersionId` and omit the top-level `assistant`:
+              with `assistant` set (`azuredatalakestoragegen2` or any other slug) the save answers
+              201/200 and stores neither id. Dropping `assistant` and re-sending both ids on a PUT
+              restores the link.
         _httpConnectorApiId:
           type: string
           format: objectId

package/dist/sync.yml

@@ -238,7 +238,8 @@ paths:
         '422':
           description: |-
             Validation failed. `source._connectionId` is missing
-            (`missing_source_connection`), the destination duplicates another sync
+            (`missing_source_connection`), the integration was not created with
+            `syncs: true` (`integration_not_for_sync`), the destination duplicates another sync
             (`duplicate_destination_host`), the destination connector rejected the
             sync configuration (`invalid_destination_sync_config`), two enabled
             datasets resolve to the same destination table
@@ -256,6 +257,13 @@ paths:
                     errors:
                       - code: missing_source_connection
                         message: Source connection is missing in the request
+                integration_not_for_sync:
+                  summary: Integration was not created for syncs
+                  value:
+                    errors:
+                      - field: _integrationId
+                        code: integration_not_for_sync
+                        message: An integration is suppose to have either flows or syncs but not both.
   /v1/syncs/{_id}:
     get:
       x-internal: false
@@ -892,7 +900,12 @@ paths:
         is always accepted; on a normal run it is rejected unless the account has partial
         normal sync enabled.
 
-        Preconditions enforced by the platform:
+        Preconditions enforced by the platform, in order:
+        - The body must be valid (`400 invalid_parameter`).
+        - The sync must have a backing replication flow. A draft whose destination has never been
+          saved has none and answers `404 sync_flow_not_present` — before the disabled check and
+          before any `datasetIds` membership or entitlement check, so a draft never reaches
+          `422 invalid_sync`.
         - The sync must not be disabled (`422 invalid_sync`).
         - There must not be a job already queued or running for this sync (`409 sync_job_already_queued`).
 
@@ -944,15 +957,22 @@ paths:
                     flowExecutionGroupId: 6821c01c39db7c2b9cdc0e29
         '400':
           description: |-
-            Bad request. Invalid `runType`, invalid `datasetIds` shape, subset selection on a
+            Bad request. A malformed `_syncId`, an invalid `runType`, an invalid `datasetIds`
+            shape (empty array, non-array, or non-ObjectId entries), subset selection on a
             normal run when that is not enabled for the account, or datasets that do not
             belong to this sync / are disabled.
-            Error codes: `invalid_parameter`, `invalid_dataset_selection`.
+            Error codes: `invalid_ref`, `invalid_parameter`, `invalid_dataset_selection`.
           content:
             application/json:
               schema:
                 $ref: '#/components/schemas/Error'
               examples:
+                malformed_sync_id:
+                  summary: _syncId is not a valid ObjectId
+                  value:
+                    errors:
+                      - code: invalid_ref
+                        message: Please provide a valid _syncId.
                 invalid_run_type:
                   summary: Invalid runType parameter
                   value:
@@ -965,8 +985,14 @@ paths:
                     errors:
                       - code: invalid_parameter
                         message: datasetIds is not supported for normal sync runs
+                empty_dataset_ids:
+                  summary: datasetIds is an empty array
+                  value:
+                    errors:
+                      - code: invalid_parameter
+                        message: datasetIds must contain at least one dataset ID
                 invalid_dataset_ids_shape:
-                  summary: datasetIds is not a non-empty array of ObjectIds
+                  summary: datasetIds is not an array of ObjectIds
                   value:
                     errors:
                       - code: invalid_parameter
@@ -981,8 +1007,11 @@ paths:
           $ref: '#/components/responses/401-unauthorized'
         '404':
           description: |-
-            Sync not found.
-            Error code: `invalid_ref`.
+            Sync not found (`invalid_ref`), or the sync has no backing replication flow because
+            its destination has never been saved (`sync_flow_not_present`). The second check runs
+            before the disabled, membership, and entitlement checks, so a draft sync answers this
+            way whatever the body.
+            Error codes: `invalid_ref`, `sync_flow_not_present`.
           content:
             application/json:
               schema:
@@ -993,7 +1022,13 @@ paths:
                   value:
                     errors:
                       - code: invalid_ref
-                        message: Sync not found.
+                        message: 'Sync not found: 6ac4949901f0467e95366000'
+                sync_flow_not_present:
+                  summary: Draft sync with no saved destination
+                  value:
+                    errors:
+                      - code: sync_flow_not_present
+                        message: The flow is not present in the sync.
         '409':
           description: |-
             A sync job is already queued or running for this sync.
@@ -3952,14 +3987,24 @@ components:
         - |-
           When scaffolding a draft sync before the destination is known, send only
           _integrationId and source._connectionId; the sync is created disabled and the
-          destination can be filled in with a later PUT.
+          destination can be filled in with a later PUT. A draft with no saved destination
+          has no backing flow, so POST /v1/syncs/{_syncId}/run answers 404 sync_flow_not_present
+          (ahead of the disabled check) rather than 422 invalid_sync.
+        - |-
+          Create the parent integration with syncs: true in the POST /v1/integrations body. An
+          integration created without it fails the sync create with 422 integration_not_for_sync
+          ("An integration is suppose to have either flows or syncs but not both"), and PUT
+          /v1/integrations/{_id} ignores the syncs field, so the only fix is a new integration.
       properties:
         _integrationId:
           type: string
           format: objectId
           x-celigo-refModel: integrations
           description: |-
-            Integration to create the sync in. Required on create; forbidden on update —
+            Integration to create the sync in. It must have been created with `syncs: true`
+            (`POST /v1/integrations`) — an integration without that flag fails the create with
+            `422 integration_not_for_sync`, and the flag cannot be added afterwards because
+            `PUT /v1/integrations/{_id}` ignores it. Required on create; forbidden on update —
             the integration cannot be changed once assigned (`400 sync_integration_id_update`).
           examples:
             - 69f4ffd395ec28be9cb8c12e

package/dist/tool.yml

@@ -9570,11 +9570,23 @@ components:
           description: |-
             HTTP connector (pre-built application template) this connection is linked to. Linking
             lets exports and imports on the connection pick endpoints from the connector's catalog and
-            drives the `assistant` form in the UI. An id that does not resolve to an accessible
-            connector is dropped from the saved document rather than rejected — read the response back
-            to confirm the link took.
+            drives the `assistant` form in the UI. The link is resolved server-side on create and on
+            any update that changes `assistant` or a connector id, and the result overwrites
+            `_httpConnectorId`, `_httpConnectorApiId` and `_httpConnectorVersionId`: an id that does
+            not resolve to an accessible connector is dropped rather than rejected, and when the
+            top-level `assistant` names an application with a legacy adaptor (the connector's
+            `legacyId`, e.g. `shopify`) the connector resolved from that slug replaces the id you sent
+            and a sent `_httpConnectorVersionId` is dropped. Read the response back to confirm the
+            link took.
           examples:
             - 5d8f6a2b9c1e4f00112a3b4c
+          x-celigo-ai-guidance:
+            - |-
+              To link an Azure Data Lake Storage Gen2 connection to its connector, send
+              `_httpConnectorId` and `_httpConnectorVersionId` and omit the top-level `assistant`:
+              with `assistant` set (`azuredatalakestoragegen2` or any other slug) the save answers
+              201/200 and stores neither id. Dropping `assistant` and re-sending both ids on a PUT
+              restores the link.
         _httpConnectorApiId:
           type: string
           format: objectId

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.92",
+  "version": "0.2.94",
   "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": "ec12d5c1",
+		"iasCommit": "29615c6c",
 		"generatedAt": "2026-10-12"
 	},
 	"roots": {