@celigo/api-specs 0.2.86 → 0.2.88

package/dist/integration.yml

@@ -25,7 +25,9 @@ tags:
       - **Standard integrations** — user-created containers that group custom flows.
       - **Integration App installations** — created from a published connector/template,
         with install/uninstall steps, settings forms, editions, and optional child
-        integrations. These have `_connectorId` and `_templateId` set.
+        integrations. `_connectorId` is what identifies one. The wizard fields (`mode`,
+        `install`, `installSteps`) also appear on a standard integration created by the
+        UI's clone-and-install, so they do not by themselves mean Integration App.
 
       Integrations support **Integration Lifecycle Management (ILM)**: clone an integration
       across environments, then use revisions (snapshot, pull, revert) to promote changes
@@ -99,8 +101,10 @@ paths:
       summary: Create an integration
       description: |-
         Creates a new integration. Only `name` is required — the server populates all other
-        fields with defaults. Do not include Integration App fields (`_connectorId`, `_templateId`,
-        `install`, `installSteps`, etc.) unless you are creating an IA installation.
+        fields with defaults. Do not include `_connectorId` unless you are creating an
+        Integration App installation, or `_templateId` unless the integration is created from
+        a template; leave the install-wizard fields (`mode`, `install`, `installSteps`) to the
+        platform's installers.
       operationId: createIntegration
       tags:
         - Integrations
@@ -3418,16 +3422,18 @@ components:
           examples:
             - 5c1a7b8d4f2e6a0011556677
           description: |-
-            Template identifier used to create/initialize this integration (commonly for Integration Apps).
+            Marketplace template this integration was installed from. Absent on integrations built from scratch and on
+            clones. It does not make the integration an Integration App — `_connectorId` does.
 
             Omit unless you are creating/updating an integration from a template.
         install:
           type: array
           description: |-
-            Install "cards" shown during an Integration App installation.
+            Install "cards" an Integration App installer shows during installation — UI workflow metadata, not runtime
+            configuration. The platform also writes it (empty) on a plain custom integration created by the UI's
+            clone-and-install, so its presence does not indicate an Integration App.
 
-            These are primarily UI/workflow metadata. Unless you are explicitly modeling an Integration App install experience,
-            omit this field.
+            Unless you are explicitly modeling an install experience, omit this field.
           items:
             type: object
             additionalProperties: true
@@ -3502,17 +3508,19 @@ components:
         mode:
           type: string
           description: |-
-            Integration App lifecycle mode.
+            Where the integration stands in its install or uninstall wizard. The platform writes it on a plain custom
+            integration created by the UI's clone-and-install as much as on an Integration App, and leaves it set after
+            the wizard completes, so it does not indicate an Integration App (`_connectorId` does).
 
-            Use this only when dealing with Integration App lifecycle workflows.
+            Omit when creating an integration directly.
           enum:
             - install
             - settings
             - uninstall
           x-enumDescriptions:
-            install: The integration is being installed or is in the install workflow.
-            settings: The integration is in settings configuration mode.
-            uninstall: The integration is being uninstalled.
+            install: Install steps are still pending and the UI shows the setup wizard
+            settings: Setup is complete and the integration is in normal use
+            uninstall: The integration is being uninstalled
           examples:
             - install
         settings:
@@ -3634,9 +3642,12 @@ components:
         installSteps:
           type: array
           description: |-
-            Ordered list of lifecycle steps used by the Integration App installer.
+            Ordered steps of the install wizard that created this integration, each marked completed as it finishes.
+            Written by the UI's clone-and-install of a plain custom integration (a `template_zip` step with `isClone`
+            true) as well as by Integration App installers, and kept after completion — so a populated list does not
+            indicate an Integration App.
 
-            This is primarily Integration App workflow metadata. Omit unless you are working with Integration Apps.
+            Omit unless you are building an installer.
           items:
             type: object
             additionalProperties: true

package/package.json

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

package/schemas.json

@@ -1,8 +1,8 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "2d9562f",
-		"generatedAt": "2026-10-10"
+		"iasCommit": "2e26fe6e",
+		"generatedAt": "2026-10-12"
 	},
 	"roots": {
 		"aiagent": 133,