@celigo/api-specs 0.2.167 → 0.2.168

package/dist/export.yml

@@ -5580,7 +5580,10 @@ components:
               description: |-
                 When true, a file whose records partially fail parsing against the file definition
                 still emits the records that did parse, instead of failing the entire file. Applies to
-                file-definition (fixed-width, EDI) parsing only.
+                file-definition (fixed-width, EDI) parsing only. For X12 and EDIFACT the unit is the
+                transaction set (ST–SE, UNH–UNT), and it takes effect only with an EDI profile linked:
+                a failed set is set aside and reported as an error while the file's other sets go on
+                as records. Without this flag, one failed set fails the whole file.
               examples:
                 - true
                 - false

package/dist/filedefinition.yml

@@ -1163,8 +1163,12 @@ components:
             Primarily relevant for EDI EDIFACT format.
         skipEDIValidation:
           type: boolean
+          default: true
           description: |
-            Whether to skip EDI structural validation during parsing.
+            Whether to skip EDI element validation during parsing: element lengths, data types,
+            code lists, mandatory elements and element relationships. Omitted means skipped, so
+            these checks run only when it is `false`. Profile checks (`skipEDIProfileValidation`)
+            and missing mandatory segments are separate and still apply.
         skipEDIProfileValidation:
           type: boolean
           default: false
@@ -1188,6 +1192,11 @@ components:
           `maxOccurrence` is 1 or unset, matches only the first row: in fixed-width and delimited
           files the parser drops the rest without an error, and an X12 parse fails at the next row,
           naming a mandatory segment as missing.
+        - |-
+          Cloning an export that uses a file definition also creates a new file definition, with the
+          same name, and points the cloned export at it: the export's clone preview lists it as a
+          `FileDefinition` object. Two definitions with one name can follow, so tell them apart by
+          `_id`.
     ResourceResponse:
       type: object
       description: Response

package/dist/integration.yml

@@ -1024,97 +1024,6 @@ paths:
                     errors:
                       - code: invalid_ref
                         message: Integration not found.
-  /v1/integrations/{_id}/clonefamily:
-    get:
-      x-internal: false
-      operationId: listIntegrationCloneFamily
-      tags:
-        - Integrations
-      summary: List an integration's clone family
-      description: |-
-        Returns every member of the integration's clone family -- the original plus every clone
-        (recursively, across environments). Used by ILM to decide which integrations can be pull/push
-        sources or targets for the current integration.
-
-        This endpoint requires the `integrator-ashareid` header to establish a shared-account context.
-        For simpler clone-relationship lookups, the integration's own `_sourceId` field points to the
-        parent it was cloned from, and `GET /v1/integrations?_sourceId=<id>` lists the children.
-      parameters:
-        - name: integrator-ashareid
-          in: header
-          required: true
-          description: |-
-            Account-share id that scopes the request to a specific shared-account context. The bearer
-            token's user must be the `sharedWithUser` of this ashare.
-          schema:
-            type: string
-            format: objectId
-            examples:
-              - 6798f4dc43db9184f4bc8ee0
-        - name: _id
-          in: path
-          required: true
-          description: Integration id.
-          schema:
-            type: string
-            format: objectId
-            x-celigo-refModel: integrations
-            examples:
-              - 6842261335b64c0bcb308e4f
-      responses:
-        '200':
-          description: Clone family members.
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/CloneFamilyResponse'
-              examples:
-                family:
-                  summary: Original integration plus one clone in another environment
-                  value:
-                    - _id: 6842261335b64c0bcb308e4f
-                      name: Shopify → NetSuite Orders
-                    - _id: 68f52162f00a35a1b26eaafb
-                      name: Clone - Shopify → NetSuite Orders
-                      _envId: 67b123456789abcdef012345
-        '401':
-          $ref: '#/components/responses/401-unauthorized'
-        '403':
-          description: |-
-            Either the `integrator-ashareid` header is malformed (code: `invalid_header_value`) or it
-            was omitted entirely (code: `get_not_allowed`, "GET resource not allowed for the given
-            model.").
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/Error'
-              examples:
-                get_not_allowed:
-                  summary: Header omitted entirely
-                  value:
-                    errors:
-                      - code: get_not_allowed
-                        message: GET resource not allowed for the given model.
-                invalid_header_value:
-                  summary: Header malformed (not a 24-char hex id)
-                  value:
-                    errors:
-                      - code: invalid_header_value
-                        message: The value provided for request header Integrator-AShareId is invalid.
-        '404':
-          description: |-
-            Integration unknown, or the `integrator-ashareid` references a share whose `sharedWithUser`
-            isn't the bearer token's user (code: `access_restricted`).
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/Error'
-              examples:
-                access_restricted:
-                  value:
-                    errors:
-                      - code: access_restricted
-                        message: Your access to an integrator.io environment or account has been disabled. For more information, contact account administrator.
   /v1/integrations/{_id}/flows:
     get:
       x-internal: false
@@ -2575,103 +2484,6 @@ paths:
           $ref: '#/components/responses/401-unauthorized'
         '404':
           $ref: '#/components/responses/404-not-found'
-  /v1/integrations/{_id}/iLMIgnore:
-    get:
-      x-internal: false
-      operationId: getIntegrationILMIgnoreFields
-      tags:
-        - Integrations
-      summary: List available ILM ignore fields
-      description: |-
-        Returns the catalog of *available* fields that can be ignored when pulling changes between
-        related integrations. Keys are lowercase resource types (`integration`, `flow`, `export`,
-        `import`, `connection`, `script`, ...); values are arrays of dot-path field names that can be
-        excluded from an ILM pull/revert. The key set is platform-driven — treat the response, not
-        the example list, as the authoritative catalog.
-
-        This endpoint requires the `integrator-ashareid` header to establish a shared-account context.
-        The current ignore configuration lives on the integration's `iLMIgnore` field (readable via
-        `GET /v1/integrations/{_id}`); this endpoint only returns the menu of what *can* be ignored.
-        To change the configuration, PATCH the integration with
-        `[{op:"replace", path:"/iLMIgnore", value:{...}}]`.
-      parameters:
-        - name: integrator-ashareid
-          in: header
-          required: true
-          description: |-
-            Account-share id that scopes the request to a specific shared-account context. The bearer
-            token's user must be the `sharedWithUser` of this ashare.
-          schema:
-            type: string
-            format: objectId
-            examples:
-              - 6798f4dc43db9184f4bc8ee0
-        - name: _id
-          in: path
-          required: true
-          description: Integration id.
-          schema:
-            type: string
-            format: objectId
-            x-celigo-refModel: integrations
-            examples:
-              - 6842261335b64c0bcb308e4f
-      responses:
-        '200':
-          description: Available ignore fields per resource type.
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/ILMIgnoreResponse'
-              examples:
-                default:
-                  value:
-                    integration:
-                      - name
-                      - description
-                    flow:
-                      - disabled
-                      - name
-                    export:
-                      - name
-                      - http.body
-        '401':
-          $ref: '#/components/responses/401-unauthorized'
-        '403':
-          description: |-
-            Either the `integrator-ashareid` header is malformed (code: `invalid_header_value`) or it
-            was omitted entirely (code: `get_not_allowed`).
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/Error'
-              examples:
-                get_not_allowed:
-                  summary: Header omitted entirely
-                  value:
-                    errors:
-                      - code: get_not_allowed
-                        message: GET resource not allowed for the given model.
-                invalid_header_value:
-                  summary: Header malformed (not a 24-char hex id)
-                  value:
-                    errors:
-                      - code: invalid_header_value
-                        message: The value provided for request header Integrator-AShareId is invalid.
-        '404':
-          description: |-
-            Integration unknown, or the `integrator-ashareid` references a share whose `sharedWithUser`
-            isn't the bearer token's user (code: `access_restricted`).
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/Error'
-              examples:
-                access_restricted:
-                  value:
-                    errors:
-                      - code: access_restricted
-                        message: Your access to an integrator.io environment or account has been disabled. For more information, contact account administrator.
   /v1/integrations/{_id}/template:
     get:
       x-internal: false
@@ -4957,36 +4769,6 @@ components:
             type: string
             examples:
               - '6044134138'
-    CloneFamilyResponse:
-      type: array
-      description: |-
-        Members of an integration's clone family — the original integration plus every clone (including
-        clones of clones, across environments). Used by ILM to decide which integrations can pull from or
-        push to the current one.
-      items:
-        type: object
-        description: One integration in the clone family.
-        properties:
-          _id:
-            type: string
-            format: objectId
-            description: Integration id.
-            x-celigo-refModel: integrations
-            examples:
-              - 6842261335b64c0bcb308e4f
-          name:
-            type: string
-            description: Display name of the integration.
-            examples:
-              - Shopify → NetSuite Orders
-          _envId:
-            type: string
-            format: objectId
-            x-celigo-refModel: environments
-            examples:
-              - 67b123456789abcdef012345
-            description: Environment id the integration belongs to.
-        additionalProperties: true
     LookupCacheBase:
       type: object
       description: Writable fields shared by the request and response schemas.
@@ -5345,38 +5127,6 @@ components:
             - To register an existing topic instead, use `PUT /v1/integrations/{_id}/topics/{_topicId}/register`.
           examples:
             - - 6ab1f4a138d7733b45998d99
-    ILMIgnoreResponse:
-      type: object
-      description: |-
-        Catalog of resource-type → field-path lists that are *available* to be ignored during ILM pulls
-        and reverts. This is the full menu of what can be configured — to see the current ignore
-        configuration, read the `iLMIgnore` field on the integration itself via
-        `GET /v1/integrations/{_id}`.
-
-        Keys are lowercase resource type names (e.g. `integration`, `flow`, `export`, `import`,
-        `connection`, `script`). Each value is an array of dot-path strings naming fields that can be
-        excluded. Only resource types that have configurable ignores appear as keys.
-      additionalProperties:
-        type: array
-        description: Field paths (dotted) that can be ignored for this resource type.
-        items:
-          type: string
-      example:
-        integration:
-          - settings.general.description
-          - settings.general.name
-        flow:
-          - scheduling.startTime
-          - disabled
-        export:
-          - http.relativeURI
-          - delta.dateField
-        import:
-          - http.relativeURI
-          - mapping
-        connection:
-          - http.baseURI
-          - http.auth.token.token
     DependencyEntry:
       type: object
       description: A single resource that depends on the queried resource.

package/dist/recyclebin.yml

@@ -419,9 +419,13 @@ paths:
         Resources are auto-purged after 30 days. A purge removes only the
         named resource: purge the bin entries that still reference it first
         (a deleted flow references its integration and the exports and imports
-        it used). An integration's Celigo Storage system folder is the
-        exception: the folder and everything in it go to the bin with the
-        integration and are purged with it.
+        it used). Purging a flow leaves its integration, exports, imports and
+        scripts where they are. A few purges remove more than the named
+        document: an integration's Celigo Storage system folder (with
+        everything in it) goes to the bin with the integration and is purged
+        with it; purging a connection first deletes the end users' own copies
+        of it (their MCP connections) for good; and purging a topic deletes
+        its stored messages.
       parameters:
         - $ref: '#/components/parameters/ResourceType'
         - name: _id

package/dist/sync.yml

@@ -242,7 +242,10 @@ paths:
           description: |-
             Validation failed. `source._connectionId` is missing
             (`missing_source_connection`), the integration was not created with
-            `syncs: true` (`integration_not_for_sync`), the destination duplicates another sync
+            `syncs: true` (`integration_not_for_sync`), `destination._connectionId` isn't a
+            connection in the account (`missing_destination_connection`), the destination
+            connection is offline while a `database` or `schema` is set
+            (`offline_destination_connection`), 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
@@ -444,14 +447,21 @@ paths:
           description: |-
             Validation failed. `source._connectionId` is missing
             (`missing_source_connection`), the sync is not ready to enable
-            (`sync_not_enabled`), the destination duplicates another sync
+            (`sync_not_enabled`), the update drops the saved destination connection or names a
+            connection that doesn't exist (`missing_destination_connection`, "Destination
+            connection is missing in the request"), the new destination connection is another
+            warehouse type than the saved one (`duplicate_destination_type`, "Destination
+            connection type is not same as the previous destination connection type"), a new
+            `database` or `schema` was sent while the destination connection is offline
+            (`offline_destination_connection` — the platform creates the schema when the
+            destination is saved), 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
             (`conflicting_table_name`), a field exceeds its size limit
             (`size_limit_exceeded`), the drift policy is inconsistent
             (`drift_policy_invalid_setup`), or the destination's application differs from
-            the integration's other syncs or from the sync's saved destination.
+            the integration's other syncs.
           content:
             application/json:
               schema:
@@ -798,8 +808,9 @@ paths:
           description: |-
             Bad request. The body is not a non-empty array (`INVALID_REQUEST_BODY` /
             `EMPTY_REQUEST_BODY`), an item has both or neither of `_id`/`externalId`
-            (`dataset_externalId_id_required`), an `externalId` already exists or an `_id`
-            does not belong to the sync, `tableName` values collide
+            (`dataset_externalId_id_required`), an `externalId` already exists on the sync
+            (`create_dataset_present`) or an `_id` does not belong to it
+            (`update_dataset_not_present`), `tableName` values collide
             (`duplicate_dataset_table_names`), or an export dataset's export uses a
             different connection than the sync (`connection_mismatch`).
           content:
@@ -3016,8 +3027,10 @@ paths:
                       deltaFields:
                         type: array
                         description: |-
-                          Column names usable as the incremental-extraction cursor
-                          (`exportProperties.delta.dateField`).
+                          Column names usable as the incremental-extraction cursor. A
+                          Salesforce dataset uses the first entry itself; a NetSuite
+                          saved-search dataset names its cursor in
+                          `exportProperties.delta.dateField`.
                         items:
                           type: string
                         examples:
@@ -3438,7 +3451,8 @@ paths:
                           type: boolean
                           description: |-
                             Only present (as `true`) when the export no longer uses the
-                            sync's source connection.
+                            sync's source connection, or is no longer among the source
+                            connection's exports (for example, it was deleted).
                           examples:
                             - true
                         totalFieldCount:
@@ -4421,8 +4435,10 @@ components:
                   type: string
                   description: |-
                     Source field that carries each record's last-modified timestamp, used as
-                    the delta cursor. Required for NetSuite datasets that extract via a
-                    `netsuite.recordType`; Salesforce datasets derive it automatically.
+                    the delta cursor. Used by NetSuite saved-search datasets, where it is
+                    required when a `netsuite.recordType` is set. Salesforce datasets take the
+                    first entry of the column read's `deltaFields` instead, and HTTP-connector
+                    datasets have no date field: their delta filter is part of the request.
                   examples:
                     - lastmodifieddate
             netsuite:
@@ -4431,9 +4447,13 @@ components:
               properties:
                 recordType:
                   type: string
+                  writeOnly: true
                   description: |-
                     NetSuite record type backing a saved-search dataset. When set with
-                    `exportProperties.type: delta`, a `delta.dateField` is required.
+                    `exportProperties.type: delta`, a `delta.dateField` is required. Write-only:
+                    dataset reads don't return it, so an update item built from a read-back
+                    clears it; the sync's next run restores a missing value from the saved
+                    search's catalog entry (`appSpecificProperties.recordType`).
                   examples:
                     - salesorder
         driftPolicy:
@@ -4466,8 +4486,10 @@ components:
           readOnly: true
           description: |-
             Only present (as `true`) in list responses, on export-backed datasets whose
-            export no longer uses the sync's source connection. Repoint the export or
-            recreate the dataset to resume replicating it.
+            export no longer uses the sync's source connection. The source catalog listing
+            also flags an export-backed dataset whose export it no longer lists, such as a
+            deleted export. Repoint the export or recreate the dataset to resume replicating
+            it.
           examples:
             - true
     DatasetUpsertItem:
@@ -4595,8 +4617,10 @@ components:
                   type: string
                   description: |-
                     Source field carrying each record's last-modified timestamp, used as the
-                    delta cursor. Required for NetSuite datasets extracted via a
-                    `netsuite.recordType`; Salesforce datasets derive it automatically.
+                    delta cursor. Used by NetSuite saved-search datasets, where it is required
+                    when a `netsuite.recordType` is set; it isn't checked against the column
+                    read's `deltaFields`. Salesforce datasets take the first `deltaFields` entry
+                    instead, and HTTP-connector datasets take no date field.
                   examples:
                     - lastmodifieddate
             netsuite:
@@ -4606,8 +4630,11 @@ components:
                 recordType:
                   type: string
                   description: |-
-                    NetSuite record type backing a saved-search dataset. When set with
-                    `exportProperties.type: delta`, a `delta.dateField` is required.
+                    NetSuite record type backing a saved-search dataset, from the saved search's
+                    catalog entry (`appSpecificProperties.recordType`). When set with
+                    `exportProperties.type: delta`, a `delta.dateField` is required. Reads never
+                    return it, so an update item built from a read-back clears it unless you add
+                    it back; the sync's next run restores a missing value from the catalog.
                   examples:
                     - salesorder
         driftPolicy:
@@ -4649,7 +4676,11 @@ components:
             Scopes this run to these datasets on the sync. Omit the field to run every
             enabled dataset; an empty array is rejected. Each id must belong to this sync
             and be enabled, and subset selection on a normal run is rejected unless the
-            account has partial normal sync enabled.
+            account has partial normal sync enabled. A selection larger than the per-run
+            maximum is accepted here but stops the run as it starts: no table runs, and
+            the sync's errors record `max_datasets_exceeded` ("Selected datasets exceed the
+            maximum allowed per run (N). Reduce the selection and retry."). Split a large
+            selection across runs.
           items:
             type: string
             format: objectId

package/dist/tool.yml

@@ -30253,7 +30253,10 @@ components:
               description: |-
                 When true, a file whose records partially fail parsing against the file definition
                 still emits the records that did parse, instead of failing the entire file. Applies to
-                file-definition (fixed-width, EDI) parsing only.
+                file-definition (fixed-width, EDI) parsing only. For X12 and EDIFACT the unit is the
+                transaction set (ST–SE, UNH–UNT), and it takes effect only with an EDI profile linked:
+                a failed set is set aside and reported as an error while the file's other sets go on
+                as records. Without this flag, one failed set fails the whole file.
               examples:
                 - true
                 - false

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.167",
+  "version": "0.2.168",
   "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": "560182fc",
+		"iasCommit": "80cddc9b",
 		"generatedAt": "2026-10-22"
 	},
 	"roots": {