@celigo/api-specs 0.2.205 → 0.2.207

package/dist/import.yml

@@ -8567,9 +8567,23 @@ components:
           description: |-
             Tool resource this import executes. The tool supplies the input schema, routing, page
             processors, and output mapping; the import runs that tool when records reach it. Required —
-            a `ToolImport` has no behavior without a tool to run.
+            a `ToolImport` has no behavior without a tool to run. Saving the import fails with 422 when the
+            tool has no routers, a step still being set up, or a branch that does not merge back; the
+            message names the tool.
           x-celigo-ai-guidance:
             - Reference to the Celigo Tool resource this wrapper invokes.
+            - |-
+              Finish the tool before saving its wrapper: a create or update of this import fails with 422
+              tool_empty_router when the tool has no `routers` (missing or empty; the message reads "…has
+              no steps. Add at least one step to the tool, then save again."), router_setup_in_progress
+              when a step is still being set up (setupInProgress), and tool_dangling_branch when a branch
+              has no nextRouterId ("outputRouter" ends the tool). Fix the tool with PUT /v1/tools/{_id},
+              then save the import again.
+            - |-
+              A save that passes doesn't mean the tool runs: a branch with empty `pageProcessors` passes
+              it, and the tool then fails at invoke with 400 tool_empty_router. Creating a parent tool, or
+              a disabled flow, whose step is this wrapper is not checked either: both saved while the
+              wrapped tool had no routers.
             - |-
               Required.
               The Tool must already exist;
@@ -8973,16 +8987,20 @@ components:
               The `key` + `batchSize` combination has not been probed (it needs a B2B Manager
               account) — treat it as unverified, neither allowed nor forbidden.
         encrypt:
-          type: boolean
+          type: string
+          enum:
+            - pgp
+          x-enumDescriptions:
+            pgp: Encrypt the file with PGP before it is written.
           description: |-
-            Whether to encrypt the output file.
-
-            **Values**
-            - `true`: Encrypt the file (requires PGP configuration)
-            - `false`: No encryption
-
-            **Default:** `false`
-          default: false
+            Encrypts the output file; omit it for an unencrypted file. `pgp` requires
+            `pgp.symmetricKeyAlgorithm` and a connection holding the recipient's public key
+            (`pgp.publicKey`) — without either the save fails with 422 `missing_required_field`.
+            The public-key check runs first: on a connection without one, any `encrypt` value,
+            `false` included, fails with 422 `missing_required_field` "pgp publicKey is required
+            when encrypt is selected to perform file encryption." before the value is checked.
+            Blob (file-transfer) imports follow the same rule and return `encrypt` and `pgp` even
+            without `file.type`.
         csv:
           type: object
           description: CSV-specific configuration. Only used when `type` is `"csv"`.
@@ -9149,8 +9167,8 @@ components:
         pgp:
           type: object
           description: |-
-            PGP encryption settings applied when encrypt is true; selects the symmetric cipher and the
-            signing hash. The connection must hold the recipient's public key.
+            PGP encryption settings applied when `encrypt` is `pgp`; selects the symmetric cipher and
+            the signing hash. The connection must hold the recipient's public key.
           properties:
             symmetricKeyAlgorithm:
               type: string
@@ -9167,9 +9185,10 @@ components:
                 3des: Triple DES block cipher (legacy).
                 aes128: AES with a 128-bit key.
                 aes192: AES with a 192-bit key.
-                aes256: AES with a 256-bit key (default, recommended).
-              default: aes256
-              description: Symmetric cipher used to encrypt the file body; aes256 unless the recipient requires another.
+                aes256: AES with a 256-bit key (recommended).
+              description: |-
+                Symmetric cipher used to encrypt the file body; required when `encrypt` is `pgp` (no
+                server default). Use aes256 unless the recipient requires another.
               examples:
                 - aes256
                 - 3des
@@ -18086,8 +18105,9 @@ components:
       type: object
       description: |-
         The outcome of running one input record through an import — one element
-        per record, in input order — shared by `POST /v1/imports/{_id}/invoke`
-        and the virtual import `POST /v1/connections/{_id}/import`. A record the
+        per record, in input order — shared by `POST /v1/imports/{_id}/invoke`,
+        the virtual import `POST /v1/connections/{_id}/import` and its
+        integration-scoped forms. A record the
         import itself ignored before any request carries `ignored: true` and the
         `stage` that dropped it; a record the destination accepted carries its
         parsed response; a record the destination rejected — or that the

package/dist/mcp-server.yml

@@ -3874,7 +3874,7 @@ components:
           description: |-
             Required label for the limit, echoed verbatim in the 429 error message
             that rejected clients receive — name it the way consumers should read
-            it. A missing or empty name is rejected with 422.
+            it. A missing or empty name is rejected with 422 `missing_required_field`.
           examples:
             - Server-level rate limit
             - Per-user rate limit
@@ -5280,10 +5280,12 @@ components:
                 `targetConcurrencyLevel`. While true, `targetConcurrencyLevel` is the throughput lever: a
                 `concurrencyLevel` sent in a PUT is ignored, and one sent in a PATCH is stored but the
                 recovery machinery moves it back toward the target. Recovery never runs on `ftp`
-                connections: FTP errors aren't treated as rate limits.
+                connections: FTP errors aren't treated as rate limits. A rate limit hit by a Tool
+                invocation (`POST /v1/tools/{_id}/invoke`) or an export preview
+                (`POST /v1/exports/preview`) leaves the connection's concurrency as it is.
               x-celigo-ai-guidance:
                 - To change throughput while this is true, write `targetConcurrencyLevel`; a `concurrencyLevel` sent in a PUT returns 200 and changes nothing.
-                - Turning it on copies `concurrencyLevel` into `targetConcurrencyLevel`; turning it off unsets the target and leaves `concurrencyLevel` at its current value, which may be below the old target if a recovery was in progress. A `targetConcurrencyLevel` written while this is false is unset by the save.
+                - Turning it on copies `concurrencyLevel` into `targetConcurrencyLevel`; turning it off unsets the target and leaves `concurrencyLevel` at its current value, which may be below the old target if a recovery was in progress. A `targetConcurrencyLevel` sent on a create that sets this false, or with the write that turns this off, is dropped; on a connection where this is already false, writing one fails with 422 `invalid_concurrency_level`.
                 - These four settings (`concurrencyLevel`, `targetConcurrencyLevel`, `_borrowConcurrencyFromConnectionId`, this flag) accept a credential-free `PATCH /v1/connections/{_id}`. A PUT replaces the whole document, so send each secret back as its masked `******` value (that keeps it) or as a new value, and never drop one to keep it — an omitted password or `http.encrypted` is cleared, and a static token left out (with no `refreshMethod`) fails the PUT with 422.
                 - On a create, while this is true, set the level with `targetConcurrencyLevel`: on `http`, `ftp`, `rdbms` and `mongodb` connections the save stores the target sent, or the adaptor's default without one (1 for `ftp`, 5 for `rdbms` and `mongodb`, 25 for `http` where the license's `concurrency` is at least 25), as both fields, whatever `concurrencyLevel` the body carried. A create that sends this as `false` keeps its `concurrencyLevel`.
                 - On an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`.
@@ -5920,8 +5922,10 @@ components:
             While `autoRecoverRateLimitErrors` is true, a create sets `concurrencyLevel` to this value, and a
             create that omits it gets 1 for both. Auto-recovery never runs on FTP connections (FTP errors
             aren't treated as rate limits), so nothing climbs back to it.
-            Kept on a `PUT` that omits it, like `concurrencyLevel`; unset by the save while
-            `autoRecoverRateLimitErrors` is false.
+            Kept on a `PUT` that omits it, like `concurrencyLevel`. A create that sends
+            `autoRecoverRateLimitErrors` false, or a write that turns it off, drops it; on a connection
+            where the flag is already false, sending it fails with 422 `invalid_concurrency_level`
+            ("cannot be set when autoRecoverRateLimitErrors is false").
           minimum: 1
           maximum: 50
           examples:
@@ -6662,9 +6666,10 @@ components:
             Higher values increase throughput but may trigger API rate limits.
             Set this based on the target API's rate limit documentation.
             Send no more than the account's licensed maximum (25 standard, 50 with an Environments license).
-            A decimal is rejected with 422 `invalid_field_value` on every write (the same rule applies to every
-            adaptor's `concurrencyLevel` and `targetConcurrencyLevel`, and to `ftp.multiThreadCount`).
-            Platform-managed while `autoRecoverRateLimitErrors` is true — a create or PUT ignores the value (a create without `targetConcurrencyLevel` stores 25 where the license's `concurrency` is at least 25) and the recovery machinery moves it toward the target; set `targetConcurrencyLevel` instead.
+            A create, a PATCH, and a PUT while `autoRecoverRateLimitErrors` is false reject a decimal with 422
+            `invalid_field_value` and a boolean or a non-numeric string with 422 `invalid_concurrency_level`
+            ("must be an integer").
+            Platform-managed while `autoRecoverRateLimitErrors` is true — a create still checks the value but stores the target in its place (25 without a `targetConcurrencyLevel`, where the license's `concurrency` is at least 25), a PUT ignores it without checking it, and the recovery machinery moves it toward the target; set `targetConcurrencyLevel` instead.
             At level 1 an import's pages run one at a time, so a record's existence lookup and write finish before the next record's start (measured on a single import); the import's `idLockTemplate` serializes only same-key records and leaves the rest parallel.
           minimum: 1
           maximum: 50
@@ -6677,7 +6682,9 @@ components:
             Ceiling the platform climbs back to after rate-limit recovery, in steps of 25% of this value.
             Writing it also sets `concurrencyLevel` to the same value and stops any recovery in progress.
 
-            Honored only while `autoRecoverRateLimitErrors` is true; ignored, and unset, when it is false.
+            Honored only while `autoRecoverRateLimitErrors` is true. A create that sends the flag as false, or a
+            write that turns it off, drops it; on a connection where the flag is already false, sending it fails with 422
+            `invalid_concurrency_level` ("cannot be set when autoRecoverRateLimitErrors is false").
           minimum: 1
           maximum: 50
           examples:
@@ -7448,6 +7455,26 @@ components:
               examples:
                 - - rate_limit_exceeded
                   - too_many_requests
+            failHeaders:
+              type: array
+              description: |
+                Response-header rules for detecting rate limiting, each a header `name` with an
+                optional `value`. A rule with an empty `name` fails the save with 422
+                `invalid_header_format`.
+              items:
+                type: object
+                required:
+                  - name
+                properties:
+                  name:
+                    type: string
+                    description: Response header the rule checks.
+                  value:
+                    type: string
+                    description: Header value the rule checks; omit to check the header alone.
+              examples:
+                - - name: X-RateLimit-Remaining
+                    value: '0'
             limit:
               type: number
               minimum: 1

package/dist/sync.yml

@@ -654,6 +654,17 @@ paths:
             type: string
             examples:
               - WyJBY2NvdW50IiwiNmE1NTk3MGM1Zjk0OThhMTc1OGEwYWQzIl0
+        - name: enable
+          in: query
+          required: false
+          description: |-
+            When true, returns only enabled datasets; when false, only disabled ones. Omit to
+            return both. Only the lowercase strings `true` and `false` are accepted; any other
+            value fails with `400 invalid_query_param`.
+          schema:
+            type: boolean
+            examples:
+              - true
         - $ref: '#/components/parameters/Include'
         - $ref: '#/components/parameters/Exclude'
       responses:
@@ -723,7 +734,24 @@ paths:
                           children: []
                       mismatchSyncConnection: true
         '204':
-          description: The sync has no datasets, or the sync does not exist.
+          description: |-
+            The sync has no datasets (none matching `enable`, when it is sent), or the sync
+            does not exist.
+        '400':
+          description: |-
+            `enable` is something other than `true` or `false` (`invalid_query_param`). The
+            value is checked before the sync is looked up.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+              examples:
+                invalid_enable:
+                  summary: enable=yes
+                  value:
+                    errors:
+                      - code: invalid_query_param
+                        message: The query parameter "enable" has invalid value.
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '422':
@@ -2678,7 +2706,8 @@ paths:
         data warehouse a sync loads records into. A sync's destination application is the type of
         its destination connection (`rdbms.type` for warehouse connections), which must match one
         of the returned ids. Identifiers include `snowflake` (Snowflake), `nsaw` (NetSuite
-        Analytics Warehouse), `bigquery` (Google BigQuery), and `mssql` (Microsoft SQL Server).
+        Analytics Warehouse), `bigquery` (Google BigQuery), `mssql` (Microsoft SQL Server), and
+        `redshift` (Amazon Redshift).
       tags:
         - Syncs
       operationId: listSyncDestinations
@@ -2706,6 +2735,7 @@ paths:
                     - id: bigquery
                     - id: mssql
                     - id: nsaw
+                    - id: redshift
                     - id: snowflake
         '401':
           $ref: '#/components/responses/401-unauthorized'
@@ -2837,6 +2867,27 @@ paths:
                           description: Adaptor the export runs on (e.g. `SalesforceExport`).
                           examples:
                             - SalesforceExport
+                        exportDocProperties:
+                          type: object
+                          description: |-
+                            Extraction behavior read from the export resource. Use `exportType`
+                            rather than `type`, which is absent for exports that extract every record.
+                          required:
+                            - exportType
+                          properties:
+                            exportType:
+                              type: string
+                              enum:
+                                - all
+                                - delta
+                              description: |-
+                                Whether the export extracts every record or only changed records.
+                                `delta` when the export's `type` is `delta`; `all` otherwise.
+                              x-enumDescriptions:
+                                all: The export extracts every record on every run.
+                                delta: The export extracts only records changed since its previous run.
+                              examples:
+                                - delta
               examples:
                 default:
                   value:
@@ -2850,6 +2901,8 @@ paths:
                         _id: 6a3e7c54c2387aaa87881b80
                         type: delta
                         adaptorType: SalesforceExport
+                        exportDocProperties:
+                          exportType: delta
         '400':
           description: |-
             Bad request. The connection id is not a valid id, or `type` is not one of the
@@ -3465,6 +3518,28 @@ paths:
                           description: Number of enabled fields.
                           examples:
                             - 16
+                        exportDocProperties:
+                          type: object
+                          description: |-
+                            Extraction behavior read from the export resource itself, not from the
+                            saved dataset. Absent on entries whose export is no longer among the
+                            source connection's exports.
+                          required:
+                            - exportType
+                          properties:
+                            exportType:
+                              type: string
+                              enum:
+                                - all
+                                - delta
+                              description: |-
+                                Whether the export extracts every record or only changed records.
+                                `delta` when the export's `type` is `delta`; `all` otherwise.
+                              x-enumDescriptions:
+                                all: The export extracts every record on every run.
+                                delta: The export extracts only records changed since its previous run.
+                              examples:
+                                - delta
               examples:
                 merged:
                   summary: Saved and unsaved entries side by side
@@ -3499,6 +3574,8 @@ paths:
                         userActionRequired: false
                         totalFieldCount: 16
                         selectedFieldCount: 16
+                        exportDocProperties:
+                          exportType: delta
         '400':
           $ref: '#/components/responses/400-bad-request'
         '401':
@@ -3821,7 +3898,17 @@ components:
                 configured. Choose `ignore` to keep the replicated set fixed and add new
                 tables manually. A sync created through the API starts at `ignore`, and a PUT
                 that omits `driftPolicy` or sends an empty `dataset` object keeps the stored
-                value, so moving back from `automate` takes an explicit `ignore`.
+                value, so moving back from `automate` takes an explicit `ignore`. `automate` is
+                kept only for object-mode sources: Salesforce, NetSuite, NetSuite JDBC, and HTTP
+                connector connections whose connector, API and version match an entry in
+                `GET /v1/di/metadata/sources`. For any other source a POST or PUT stores `ignore`.
+              x-celigo-ai-guidance:
+                - |-
+                  On a source that is not object-mode (a plain HTTP connection, or an HTTP connector
+                  connection that matches no GET /v1/di/metadata/sources entry), a save with
+                  dataset.added automate still succeeds (201 on POST, 200 on PUT) but stores ignore.
+                  Read the sync back rather than assuming automate took, and tell the user new tables
+                  must be enabled by hand.
               x-enumDescriptions:
                 automate: Automatically add newly discovered tables to the sync and start replicating them.
                 ignore: Leave newly discovered tables out of the sync until a user enables them.
@@ -3963,7 +4050,7 @@ components:
               x-celigo-refModel: connections
               description: |-
                 Connection to the destination warehouse. Its application (`rdbms.type` such as
-                `snowflake`, `bigquery` or `mssql`, or a NetSuite Analytics Warehouse JDBC
+                `snowflake`, `bigquery`, `mssql` or `redshift`, or a NetSuite Analytics Warehouse JDBC
                 connection) is one of the ids returned by `GET /v1/di/metadata/destinations`.
               examples:
                 - 68d02dbe0839a514623c1d6d
@@ -4160,7 +4247,10 @@ components:
             dataset. A `database` and `schema` pair, in any letter case, can back only one sync,
             even across integrations (`422 duplicate_destination_host`, "Duplicate destination host found"). All syncs in
             an integration must target the same destination application type, and a sync's
-            destination type can't change once saved.
+            destination type can't change once saved. An Amazon Redshift destination is checked
+            on every save that sends `_connectionId`: a missing `database` or `schema` fails with
+            422 `invalid_destination_sync_config` ("Redshift database is required on sync
+            destination" / "Redshift schema is required on sync destination").
           x-celigo-ai-guidance:
             - |-
               Send the block complete or not at all. A partial block is rejected in the destination's
@@ -4174,9 +4264,9 @@ components:
               Saving a complete destination connects to the warehouse to create the schema
               (dataset) when it is missing. When the host resolves but the connection fails, or
               the credentials are unusable, the save fails with the connection's error — 422
-              `invalid_host` for SQL Server, `big_query_unexpected_error` for BigQuery — and no
-              sync document is created or updated; fix the connection rather than changing
-              database or schema names.
+              `invalid_host` for SQL Server, `big_query_unexpected_error` for BigQuery,
+              `redshift_auth_fail` for Amazon Redshift — and no sync document is created or
+              updated; fix the connection rather than changing database or schema names.
             - |-
               A destination host that doesn't resolve can leave the save without a response for
               more than 30 seconds, with nothing saved (seen on SQL Server and Snowflake
@@ -4204,7 +4294,7 @@ components:
               x-celigo-refModel: connections
               description: |-
                 Connection to the destination warehouse. Its application (`rdbms.type` such as
-                `snowflake`, `bigquery` or `mssql`, or a NetSuite Analytics Warehouse JDBC
+                `snowflake`, `bigquery`, `mssql` or `redshift`, or a NetSuite Analytics Warehouse JDBC
                 connection) must be one of the ids returned by `GET /v1/di/metadata/destinations`;
                 any other connection fails with `422 invalid_destination_type`.
               examples:
@@ -4214,7 +4304,8 @@ components:
               description: |-
                 Database in the destination warehouse the sync loads into; it must already exist.
                 For Google BigQuery this is the GCP project id the tables are created in
-                (`project.dataset.table`).
+                (`project.dataset.table`). For Amazon Redshift it must be an unquoted identifier,
+                under the same rule as `schema`.
               x-celigo-ui-override: For a BigQuery destination the Create Sync wizard shows no database picker and fills this field with the selected connection's rdbms.bigquery.projectId.
               examples:
                 - ANALYTICS_DB
@@ -4223,7 +4314,10 @@ components:
               description: |-
                 Schema within `database` where the sync creates and loads tables; created on save
                 when it does not exist. For Google BigQuery this is the dataset name, with case
-                preserved.
+                preserved. For Amazon Redshift it must start with a letter or underscore, contain
+                only letters, digits and underscores, stay within 127 bytes, and carry no leading
+                or trailing whitespace; anything else fails with 422 `invalid_destination_sync_config`
+                (for example "Redshift schema contains invalid identifier characters").
               x-celigo-ui-override: For a BigQuery destination the Create Sync wizard labels this field "dataset" and accepts only letters, digits and underscore (no $), starting with a letter or underscore, at most 1024 characters; Snowflake and NSAW validation is unchanged.
               examples:
                 - salesforce_raw