@celigo/api-specs 0.2.23 → 0.2.25

package/dist/ai-agent.yml

@@ -4958,11 +4958,6 @@ components:
         `hooks.preSavePage` script, or for a file-definition export make the repeating segment the
         record boundary in the definition's rules.
       x-celigo-ai-guidance:
-        - |-
-          Two modes, decided by the SHAPE of the record entering the step. Object record with a child
-          array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
-          export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
-          element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
         - |-
           Only imports and lookups (exports placed as page processors) fan out. On a standalone export
           (a flow's page generator) the API saves ``oneToMany`` / ``pathToMany`` and applies neither:
@@ -4971,6 +4966,12 @@ components:
           the setting on the export, and as THREE child records with the same setting on the import.
           Never propose these fields as the way to split a standalone export's records; that is
           ``hooks.preSavePage`` work (or, for a file definition, the definition's record boundary).
+          The rules below apply only on a step that receives a record.
+        - |-
+          Two modes, decided by the SHAPE of the record entering the step. Object record with a child
+          array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
+          export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
+          element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
         - |-
           Blank ``pathToMany`` on an OBJECT record fails every record with code ``oneToMany_error``:
           "Failed to extract child records from oneToMany import data. Record at index 0 was not an

package/dist/api.yml

@@ -3001,14 +3001,37 @@ components:
             - Customer API
             - Order Management API
         _integrationId:
-          type: string
+          type:
+            - string
+            - 'null'
           format: objectId
           x-celigo-refModel: integrations
-          description: Integration this API belongs to. Omitted for standalone APIs (an API can be created without an integration).
+          description: |-
+            Integration this API belongs to. **Builder mode only** — a script-mode
+            API is always account-level and the server silently drops this field.
+            Send `null` (or omit) to keep the API account-level; on reads the field
+            is omitted when unset, never `null`.
           examples:
             - 5e9a8f7c6b3d2a0011c4e5f6
           x-celigo-ai-guidance:
             - To move the API to a different integration, PUT with a changed _integrationId; the platform registers the API's step connections in the target integration on save.
+            - |-
+              PUT is a full replace: omitting _integrationId (or sending null) on an
+              integration-owned API moves it back to the account level and clears
+              _apiGroupingId with it.
+        _apiGroupingId:
+          type:
+            - string
+            - 'null'
+          format: objectId
+          description: |-
+            One of the owning integration's `apiGroupings`, subdividing its APIs.
+            Requires `_integrationId` in the same write — sent without it, the server
+            silently drops both — so builder mode only. `PUT /v1/apis/updateApiGrouping`
+            regroups many APIs at once; this field carries the same value on a single
+            API. On reads the field is omitted when unset, never `null`.
+          examples:
+            - 60a1b2c3d4e5f60012345678
         description:
           type: string
           description: Optional description of the API's purpose.
@@ -3208,18 +3231,6 @@ components:
               description: Unique identifier for the API.
               examples:
                 - 68ae4264b5f755d2dd3796b4
-            _apiGroupingId:
-              type:
-                - string
-                - 'null'
-              format: objectId
-              readOnly: true
-              description: |-
-                API grouping this API belongs to. Set only via
-                `PUT /apis/grouping`; the server ignores this field in POST/PUT
-                bodies on this resource. May be `null` after ungrouping.
-              examples:
-                - 60a1b2c3d4e5f60012345678
             _scriptId:
               type: string
               format: objectId

package/dist/connection.yml

@@ -927,6 +927,87 @@ paths:
           Deletes a connection permanently. This operation cannot be undone.
           The connection must not be in use by any active flows or integrations.
   /v1/connections/{_id}/ping:
+    get:
+      x-internal: false
+      summary: Ping an existing connection via GET
+      description: |-
+        GET variant of the saved-connection ping — identical behavior to
+        `POST /v1/connections/{_id}/ping`, with no request body to send. Runs the adaptor's ping
+        routine against the connection identified by `_id` to verify its credentials and network
+        configuration still work; no data is read, written, or modified.
+
+        Inspect the response body, not the HTTP status, to determine the outcome: success and
+        adaptor-level failures both return HTTP 200 — success is `{code: 200}`, failures are
+        `{errors: [...]}`. The only non-success status is 404, when `_id` does not resolve to a
+        connection.
+      operationId: pingConnectionByGet
+      tags:
+        - Connections
+      parameters:
+        - in: path
+          name: _id
+          required: true
+          schema:
+            type: string
+            format: objectId
+            x-celigo-refModel: connections
+          description: Connection ID to ping.
+      responses:
+        '200':
+          description: |-
+            Ping executed. **Inspect the body** to determine outcome — success and
+            adaptor-level failures both return HTTP 200. Success returns
+            `{code: 200}`; adaptor-level failures return `{errors: [...]}`.
+          content:
+            application/json:
+              schema:
+                oneOf:
+                  - title: Ping success
+                    type: object
+                    required:
+                      - code
+                    properties:
+                      code:
+                        type: integer
+                        description: Mirrors the HTTP status — always 200 on success.
+                        example: 200
+                    additionalProperties: true
+                  - $ref: '#/components/schemas/Error'
+              examples:
+                success:
+                  summary: Connection reachable
+                  value:
+                    code: 200
+                dns_failure:
+                  summary: Connection's baseURI host could not be resolved
+                  value:
+                    errors:
+                      - code: invalid_host
+                        message: 'Unknown host: api.example.invalid. We were unable to verify this host using a DNS lookup.'
+                        source: resource
+        '401':
+          $ref: '#/components/responses/401-unauthorized'
+        '404':
+          description: |-
+            No connection found for the given `_id`. The body is an `invalid_ref`
+            error — note this is a 404, not a 400, and the field pointer is `_id`.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+              examples:
+                invalid_ref:
+                  value:
+                    errors:
+                      - field: _id
+                        code: invalid_ref
+                        message: unable to find connection for the given id.
+      x-celigo-ai-guidance:
+        - |-
+          Behaves identically to POST /v1/connections/{_id}/ping and takes no request body — use
+          whichever verb the client supports. Both verbs return HTTP 200 with {code: 200} on
+          success and HTTP 200 with {errors: [...]} on adaptor-level failure, so inspect the body,
+          not the status code.
     post:
       x-internal: false
       summary: Ping an existing connection

package/dist/editransaction.yml

@@ -1047,13 +1047,13 @@ components:
               - rejected
               - failed
           x-enumDescriptions:
-            inProgress: Acknowledgment is pending from the trading partner
-            notApplicable: Transaction type does not require a functional acknowledgment
-            notReceived: Acknowledgment window expired without a response
-            accepted: Trading partner accepted the transaction without errors
-            acceptedWithErrors: Trading partner accepted but reported non-fatal errors
-            rejected: Trading partner rejected the transaction entirely
-            failed: Acknowledgment processing failed due to a system error
+            inProgress: Awaiting functional acknowledgment from the trading partner.
+            notApplicable: No functional acknowledgment expected — the document is itself an FA, or the trading partner does not require one.
+            notReceived: Functional acknowledgment expected but not yet received.
+            accepted: Functional acknowledgment received and transaction was accepted.
+            acceptedWithErrors: Functional acknowledgment received with errors but transaction was accepted.
+            rejected: Functional acknowledgment received and transaction was rejected.
+            failed: Functional acknowledgment processing failed.
           description: |-
             Filter by functional acknowledgment status. Pass an array of one or
             more values to match. Must be an array, not a bare string. Omit to

package/dist/export.yml

@@ -810,11 +810,6 @@ components:
         `hooks.preSavePage` script, or for a file-definition export make the repeating segment the
         record boundary in the definition's rules.
       x-celigo-ai-guidance:
-        - |-
-          Two modes, decided by the SHAPE of the record entering the step. Object record with a child
-          array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
-          export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
-          element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
         - |-
           Only imports and lookups (exports placed as page processors) fan out. On a standalone export
           (a flow's page generator) the API saves ``oneToMany`` / ``pathToMany`` and applies neither:
@@ -823,6 +818,12 @@ components:
           the setting on the export, and as THREE child records with the same setting on the import.
           Never propose these fields as the way to split a standalone export's records; that is
           ``hooks.preSavePage`` work (or, for a file definition, the definition's record boundary).
+          The rules below apply only on a step that receives a record.
+        - |-
+          Two modes, decided by the SHAPE of the record entering the step. Object record with a child
+          array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
+          export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
+          element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
         - |-
           Blank ``pathToMany`` on an OBJECT record fails every record with code ``oneToMany_error``:
           "Failed to extract child records from oneToMany import data. Record at index 0 was not an
@@ -15528,6 +15529,8 @@ components:
                 - prepareFormData
             _scriptId:
               type: string
+              format: objectId
+              x-celigo-refModel: scripts
               description: |
                 Reference to a predefined script resource containing the initialization function.
 
@@ -15740,6 +15743,8 @@ components:
             - prepareResourceForSave
         _scriptId:
           type: string
+          format: objectId
+          x-celigo-refModel: scripts
           description: |
             Reference to a predefined script resource containing the preSave function.
 

package/dist/import.yml

@@ -10592,11 +10592,6 @@ components:
         `hooks.preSavePage` script, or for a file-definition export make the repeating segment the
         record boundary in the definition's rules.
       x-celigo-ai-guidance:
-        - |-
-          Two modes, decided by the SHAPE of the record entering the step. Object record with a child
-          array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
-          export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
-          element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
         - |-
           Only imports and lookups (exports placed as page processors) fan out. On a standalone export
           (a flow's page generator) the API saves ``oneToMany`` / ``pathToMany`` and applies neither:
@@ -10605,6 +10600,12 @@ components:
           the setting on the export, and as THREE child records with the same setting on the import.
           Never propose these fields as the way to split a standalone export's records; that is
           ``hooks.preSavePage`` work (or, for a file definition, the definition's record boundary).
+          The rules below apply only on a step that receives a record.
+        - |-
+          Two modes, decided by the SHAPE of the record entering the step. Object record with a child
+          array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
+          export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
+          element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
         - |-
           Blank ``pathToMany`` on an OBJECT record fails every record with code ``oneToMany_error``:
           "Failed to extract child records from oneToMany import data. Record at index 0 was not an
@@ -13856,6 +13857,8 @@ components:
                 - prepareFormData
             _scriptId:
               type: string
+              format: objectId
+              x-celigo-refModel: scripts
               description: |
                 Reference to a predefined script resource containing the initialization function.
 
@@ -13924,6 +13927,8 @@ components:
             - prepareResourceForSave
         _scriptId:
           type: string
+          format: objectId
+          x-celigo-refModel: scripts
           description: |
             Reference to a predefined script resource containing the preSave function.
 

package/dist/integration.yml

@@ -2751,6 +2751,8 @@ components:
                 - prepareFormData
             _scriptId:
               type: string
+              format: objectId
+              x-celigo-refModel: scripts
               description: |
                 Reference to a predefined script resource containing the initialization function.
 
@@ -2819,6 +2821,8 @@ components:
             - prepareResourceForSave
         _scriptId:
           type: string
+          format: objectId
+          x-celigo-refModel: scripts
           description: |
             Reference to a predefined script resource containing the preSave function.
 

package/dist/tool.yml

@@ -19450,11 +19450,6 @@ components:
         `hooks.preSavePage` script, or for a file-definition export make the repeating segment the
         record boundary in the definition's rules.
       x-celigo-ai-guidance:
-        - |-
-          Two modes, decided by the SHAPE of the record entering the step. Object record with a child
-          array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
-          export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
-          element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
         - |-
           Only imports and lookups (exports placed as page processors) fan out. On a standalone export
           (a flow's page generator) the API saves ``oneToMany`` / ``pathToMany`` and applies neither:
@@ -19463,6 +19458,12 @@ components:
           the setting on the export, and as THREE child records with the same setting on the import.
           Never propose these fields as the way to split a standalone export's records; that is
           ``hooks.preSavePage`` work (or, for a file definition, the definition's record boundary).
+          The rules below apply only on a step that receives a record.
+        - |-
+          Two modes, decided by the SHAPE of the record entering the step. Object record with a child
+          array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
+          export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
+          element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
         - |-
           Blank ``pathToMany`` on an OBJECT record fails every record with code ``oneToMany_error``:
           "Failed to extract child records from oneToMany import data. Record at index 0 was not an
@@ -20635,6 +20636,8 @@ components:
                 - prepareFormData
             _scriptId:
               type: string
+              format: objectId
+              x-celigo-refModel: scripts
               description: |
                 Reference to a predefined script resource containing the initialization function.
 
@@ -20703,6 +20706,8 @@ components:
             - prepareResourceForSave
         _scriptId:
           type: string
+          format: objectId
+          x-celigo-refModel: scripts
           description: |
             Reference to a predefined script resource containing the preSave function.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.23",
+  "version": "0.2.25",
   "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": "ed5e198",
+		"iasCommit": "a1f6b8b",
 		"generatedAt": "2026-09-18"
 	},
 	"roots": {
@@ -1629,7 +1629,8 @@
 				"object"
 			],
 			"p": {
-				"_integrationId": 1,
+				"_apiGroupingId": 88,
+				"_integrationId": 88,
 				"builder": 162,
 				"description": 1,
 				"disabled": 9,
@@ -2058,7 +2059,7 @@
 			"p": {
 				"_apiGroupingId": 88,
 				"_id": 1,
-				"_integrationId": 1,
+				"_integrationId": 88,
 				"_scriptId": 1,
 				"_templateId": 1,
 				"apim": 199,