@celigo/api-specs 0.2.173 → 0.2.175

package/dist/account.yml

@@ -383,13 +383,12 @@ paths:
                   summary: One stack available
                   value:
                     - _id: 69f536192e7966f4032f2299
-                      name: Production On-Prem Agent
+                      name: Production extension server
                       type: server
                       server:
-                        hostURI: https://agent.example.com:7020
-                        systemToken: '********'
-                        ipRanges:
-                          - 10.0.0.0/8
+                        hostURI: https://extensions.example.com:7020
+                        systemToken: '******'
+                        ipRanges: []
                 empty:
                   summary: No stacks available
                   value: []
@@ -842,7 +841,7 @@ components:
         name:
           type: string
           examples:
-            - Production On-Prem Agent
+            - Production extension server
           description: Display name shown in the UI when selecting a stack.
         type:
           type: string
@@ -850,31 +849,32 @@ components:
             - server
             - lambda
           x-enumDescriptions:
-            server: On-premise agent installed on your own infrastructure.
+            server: Your own server, which Celigo calls to run hook and wrapper code.
             lambda: AWS Lambda function managed in your own AWS account.
           description: Execution environment type that determines which configuration block is present.
         server:
           type: object
-          description: Configuration for the on-premise agent process. Present when `type` is `server`.
+          description: Configuration of a server stack. Present when `type` is `server`.
           properties:
             systemToken:
               type: string
               description: |-
-                Token the on-premise agent uses to authenticate with the
-                Celigo platform. Masked in GET responses.
+                System token for authenticating with the server stack. Masked in
+                GET responses.
             hostURI:
               type: string
               format: uri
               examples:
-                - https://agent.example.com:7020
+                - https://extensions.example.com:7020
               description: |-
-                Base URL where the on-premise agent is reachable.
-                The platform sends integration traffic to this address.
+                Base URI of the server hosting the stack. The platform calls it to
+                run hooks and wrappers.
             ipRanges:
               type: array
               description: |-
-                CIDR ranges allowed to connect to the agent. Requests from
-                IPs outside these ranges are rejected.
+                Deprecated and not enforced: the list is stored and returned as
+                sent, but no Celigo service checks it. Restrict who can reach the
+                server at the server or its firewall.
               items:
                 type: string
                 examples:

package/dist/api.yml

@@ -5454,11 +5454,13 @@ components:
                 after which the flag switches itself off), and concurrency climbs back toward
                 `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 machinery moves it back toward the target. Recovery never runs on `ftp`
+                connections: FTP errors aren't treated as rate limits.
               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.
                 - 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 an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`; while this is true a create sets `ftp.concurrencyLevel` to `ftp.targetConcurrencyLevel`, or to 1 without one.
             enableMicroBatchForOneToMany:
               type: boolean
               default: true
@@ -6076,6 +6078,10 @@ components:
             FTP servers often have low connection limits — keep this value conservative.
             Send no more than the account's licensed maximum, the license's `concurrency` (25 standard,
             50 with an Environments license).
+            While `autoRecoverRateLimitErrors` is true, which a create gets unless it sends `false`, a create
+            ignores the value sent here and sets this field to `targetConcurrencyLevel`, or to 1 when no
+            target is sent. To start higher, send `targetConcurrencyLevel` too, or create with
+            `autoRecoverRateLimitErrors: false`.
             Unlike the rest of the `ftp` object, a `PUT` that omits this field keeps the stored value instead of clearing it.
           minimum: 1
           maximum: 50
@@ -6085,8 +6091,9 @@ components:
         targetConcurrencyLevel:
           type: integer
           description: |
-            Target concurrency level for auto-scaling. The system adjusts concurrency
-            between 1 and this value based on server response feedback.
+            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.
           minimum: 1
@@ -6117,9 +6124,9 @@ components:
           type: integer
           readOnly: true
           description: |-
-            Server-maintained mirror of `multiThreadCount` used by concurrency
-            auto-scaling. Present only when rate-limit auto-recovery applies;
-            recomputed on save.
+            Server-maintained mirror of `multiThreadCount`, present while
+            `autoRecoverRateLimitErrors` is true and `targetConcurrencyLevel` is
+            set; recomputed on save.
       if:
         properties:
           type:

package/dist/connection.yml

@@ -1034,6 +1034,10 @@ paths:
         from cannot start borrowing (422 `connection_borrowed_by_another`). A
         connection can't borrow from itself: naming its own id is rejected with 422 ("… a
         connection cannot borrow concurrency from itself."), here and on `PUT`.
+        Auto-recovery never runs on `ftp` connections (FTP errors aren't treated as rate limits),
+        so on them the recovery machinery never moves `/ftp/concurrencyLevel` toward the target and
+        nothing climbs back to `/ftp/targetConcurrencyLevel`; the target still persists only while
+        `autoRecoverRateLimitErrors` is true.
         Settings-only changes are recorded in the connection's audit log.
       operationId: patchConnection
       tags:
@@ -4301,11 +4305,13 @@ components:
                 after which the flag switches itself off), and concurrency climbs back toward
                 `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 machinery moves it back toward the target. Recovery never runs on `ftp`
+                connections: FTP errors aren't treated as rate limits.
               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.
                 - 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 an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`; while this is true a create sets `ftp.concurrencyLevel` to `ftp.targetConcurrencyLevel`, or to 1 without one.
             enableMicroBatchForOneToMany:
               type: boolean
               default: true
@@ -4923,6 +4929,10 @@ components:
             FTP servers often have low connection limits — keep this value conservative.
             Send no more than the account's licensed maximum, the license's `concurrency` (25 standard,
             50 with an Environments license).
+            While `autoRecoverRateLimitErrors` is true, which a create gets unless it sends `false`, a create
+            ignores the value sent here and sets this field to `targetConcurrencyLevel`, or to 1 when no
+            target is sent. To start higher, send `targetConcurrencyLevel` too, or create with
+            `autoRecoverRateLimitErrors: false`.
             Unlike the rest of the `ftp` object, a `PUT` that omits this field keeps the stored value instead of clearing it.
           minimum: 1
           maximum: 50
@@ -4932,8 +4942,9 @@ components:
         targetConcurrencyLevel:
           type: integer
           description: |
-            Target concurrency level for auto-scaling. The system adjusts concurrency
-            between 1 and this value based on server response feedback.
+            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.
           minimum: 1
@@ -4964,9 +4975,9 @@ components:
           type: integer
           readOnly: true
           description: |-
-            Server-maintained mirror of `multiThreadCount` used by concurrency
-            auto-scaling. Present only when rate-limit auto-recovery applies;
-            recomputed on save.
+            Server-maintained mirror of `multiThreadCount`, present while
+            `autoRecoverRateLimitErrors` is true and `targetConcurrencyLevel` is
+            set; recomputed on save.
       if:
         properties:
           type:
@@ -9652,6 +9663,7 @@ components:
             drops to 1 and climbs back toward the adaptor block's `targetConcurrencyLevel`, which is the
             throughput lever while this is on. Turning it on copies the current `concurrencyLevel` into
             the target; turning it off unsets the target and leaves `concurrencyLevel` at its current value.
+            Recovery never runs on `ftp` connections: FTP errors aren't treated as rate limits.
         __integrationIds:
           type: array
           maxItems: 100

package/dist/enduser.yml

@@ -2362,11 +2362,13 @@ components:
                 after which the flag switches itself off), and concurrency climbs back toward
                 `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 machinery moves it back toward the target. Recovery never runs on `ftp`
+                connections: FTP errors aren't treated as rate limits.
               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.
                 - 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 an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`; while this is true a create sets `ftp.concurrencyLevel` to `ftp.targetConcurrencyLevel`, or to 1 without one.
             enableMicroBatchForOneToMany:
               type: boolean
               default: true
@@ -2984,6 +2986,10 @@ components:
             FTP servers often have low connection limits — keep this value conservative.
             Send no more than the account's licensed maximum, the license's `concurrency` (25 standard,
             50 with an Environments license).
+            While `autoRecoverRateLimitErrors` is true, which a create gets unless it sends `false`, a create
+            ignores the value sent here and sets this field to `targetConcurrencyLevel`, or to 1 when no
+            target is sent. To start higher, send `targetConcurrencyLevel` too, or create with
+            `autoRecoverRateLimitErrors: false`.
             Unlike the rest of the `ftp` object, a `PUT` that omits this field keeps the stored value instead of clearing it.
           minimum: 1
           maximum: 50
@@ -2993,8 +2999,9 @@ components:
         targetConcurrencyLevel:
           type: integer
           description: |
-            Target concurrency level for auto-scaling. The system adjusts concurrency
-            between 1 and this value based on server response feedback.
+            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.
           minimum: 1
@@ -3025,9 +3032,9 @@ components:
           type: integer
           readOnly: true
           description: |-
-            Server-maintained mirror of `multiThreadCount` used by concurrency
-            auto-scaling. Present only when rate-limit auto-recovery applies;
-            recomputed on save.
+            Server-maintained mirror of `multiThreadCount`, present while
+            `autoRecoverRateLimitErrors` is true and `targetConcurrencyLevel` is
+            set; recomputed on save.
       if:
         properties:
           type:

package/dist/export.yml

@@ -17666,6 +17666,18 @@ components:
           example:
             5f7c579b6411271af4e7cefa: 64a1234567890abcdef12345
             5f7c579b6411271af4e7cefb: 64a1234567890abcdef12346
+        _stackId:
+          type: string
+          format: objectId
+          x-celigo-refModel: stacks
+          description: |-
+            Stack that every stack reference in the cloned resources (hooks and wrapper
+            connections running on a stack) points at. Required when the clone preview reports
+            `stackRequired: true`: without it the clone fails with 400 `stack_not_found`. The
+            stack must belong to the target environment or be shared with it (404
+            `stack_not_found` for an unknown id, 400 `invalid_stack` otherwise).
+          examples:
+            - 5f8d43a1b9e5a80011a35f2c
       additionalProperties: true
     CloneResponse:
       description: Response body for a clone operation. Some clone endpoints return the cloned resource, while others may return a list of related created resources.

package/dist/filedefinitionrules.yml

@@ -359,16 +359,20 @@ components:
           type: string
           description: |-
             Base64-encoded EDI specification PDF. Must decode to a text-bearing
-            PDF — scanned/image-only documents fail the job with
-            `PDF_EXTRACTION_FAILED`. Encoded payloads over 50 MB are rejected
-            with `413 PAYLOAD_TOO_LARGE`.
+            PDF: a scanned or image-only document is accepted, and the job then
+            fails with `DETECTION_FAILED`. A value that isn't base64 or doesn't
+            decode to a PDF is rejected with `422 PDF_EXTRACTION_FAILED`, and
+            encoded payloads over 50 MB with `413 PAYLOAD_TOO_LARGE`.
         documentType:
           type: integer
           description: |-
             X12 transaction set number (e.g. 850), or 0 to auto-detect an
             EDIFACT specification from the PDF contents. Values outside the
             supported set fail with `400 INVALID_DOCUMENT_TYPE`; discover the
-            supported set via `GET /v1/filedefinitionrules/document-types`.
+            supported set via `GET /v1/filedefinitionrules/document-types`. A
+            supported value that names a different transaction set than the PDF
+            (an 850 guide submitted as 810) is accepted, and the job then fails
+            with `INVALID_DOCUMENT_TYPE`.
           examples:
             - 850
     ErrorCode:
@@ -388,7 +392,7 @@ components:
         - GENERATION_FAILED
         - SERVICE_UNAVAILABLE
       x-enumDescriptions:
-        INVALID_DOCUMENT_TYPE: documentType is not 0 and not a supported X12 set
+        INVALID_DOCUMENT_TYPE: documentType is not 0 and not a supported X12 set (400), or a failed job's PDF is not the submitted documentType
         INVALID_REQUEST: Request body failed schema validation
         UNAUTHORIZED: Missing or non-Bearer Authorization header
         FORBIDDEN: Invalid, expired, or insufficient token or AShare
@@ -397,7 +401,7 @@ components:
         RATE_LIMIT_EXCEEDED: Caller exceeded the endpoint token bucket
         PDF_EXTRACTION_FAILED: pdf is not valid base64 or not a PDF
         UNSUPPORTED_TYPE: Worker could not generate an FDR for the detected type
-        DETECTION_FAILED: Worker could not classify the PDF as X12 or EDIFACT
+        DETECTION_FAILED: Worker could not classify the PDF as X12 or EDIFACT, including a PDF with no text (a scanned or image-only one)
         GENERATION_FAILED: Unexpected pipeline or server failure
         SERVICE_UNAVAILABLE: Job store or PDF storage is unavailable
     ErrorItem:
@@ -499,8 +503,10 @@ components:
             code:
               type: string
               description: |-
-                Failure code — typically UNSUPPORTED_TYPE, DETECTION_FAILED,
-                PDF_EXTRACTION_FAILED, or GENERATION_FAILED.
+                Failure code — typically DETECTION_FAILED (no text to read, as in
+                a scanned or image-only PDF, or not recognizably X12 or EDIFACT),
+                INVALID_DOCUMENT_TYPE (the PDF is for a different transaction set
+                than `documentType`), UNSUPPORTED_TYPE, or GENERATION_FAILED.
               examples:
                 - UNSUPPORTED_TYPE
             message:
@@ -567,8 +573,10 @@ components:
             code:
               type: string
               description: |-
-                Failure code — typically UNSUPPORTED_TYPE, DETECTION_FAILED,
-                PDF_EXTRACTION_FAILED, or GENERATION_FAILED.
+                Failure code — typically DETECTION_FAILED (no text to read, as in
+                a scanned or image-only PDF, or not recognizably X12 or EDIFACT),
+                INVALID_DOCUMENT_TYPE (the PDF is for a different transaction set
+                than `documentType`), UNSUPPORTED_TYPE, or GENERATION_FAILED.
             message:
               type: string
               description: Human-readable failure reason.

package/dist/flow.yml

@@ -6207,6 +6207,18 @@ components:
           example:
             5f7c579b6411271af4e7cefa: 64a1234567890abcdef12345
             5f7c579b6411271af4e7cefb: 64a1234567890abcdef12346
+        _stackId:
+          type: string
+          format: objectId
+          x-celigo-refModel: stacks
+          description: |-
+            Stack that every stack reference in the cloned resources (hooks and wrapper
+            connections running on a stack) points at. Required when the clone preview reports
+            `stackRequired: true`: without it the clone fails with 400 `stack_not_found`. The
+            stack must belong to the target environment or be shared with it (404
+            `stack_not_found` for an unknown id, 400 `invalid_stack` otherwise).
+          examples:
+            - 5f8d43a1b9e5a80011a35f2c
       additionalProperties: true
     CloneResponse:
       description: Response body for a clone operation. Some clone endpoints return the cloned resource, while others may return a list of related created resources.
@@ -6264,12 +6276,18 @@ components:
                 additionalProperties: true
         stackRequired:
           type: boolean
-          description: Whether the clone requires a stack (connector-level) environment to proceed.
+          description: |-
+            `true` when the resource or one of its dependencies references a stack (a hook or
+            wrapper connection that runs on a stack). Send `_stackId` in the clone request: without
+            it the clone fails with 400 `stack_not_found`.
         _stackId:
           type:
             - string
             - 'null'
-          description: The stack id associated with the resource, or null if no stack is involved.
+          description: |-
+            The first stack the resource or a dependency references, or null. Pass it, or another
+            stack in the target environment, as `_stackId` in the clone request; the clone points
+            every stack reference at that one stack.
           examples:
             - 5f8d43a1b9e5a80011a35f2c
     FlowDescendantsResponse:

package/dist/import.yml

@@ -17773,6 +17773,18 @@ components:
           example:
             5f7c579b6411271af4e7cefa: 64a1234567890abcdef12345
             5f7c579b6411271af4e7cefb: 64a1234567890abcdef12346
+        _stackId:
+          type: string
+          format: objectId
+          x-celigo-refModel: stacks
+          description: |-
+            Stack that every stack reference in the cloned resources (hooks and wrapper
+            connections running on a stack) points at. Required when the clone preview reports
+            `stackRequired: true`: without it the clone fails with 400 `stack_not_found`. The
+            stack must belong to the target environment or be shared with it (404
+            `stack_not_found` for an unknown id, 400 `invalid_stack` otherwise).
+          examples:
+            - 5f8d43a1b9e5a80011a35f2c
       additionalProperties: true
     CloneResponse:
       description: Response body for a clone operation. Some clone endpoints return the cloned resource, while others may return a list of related created resources.
@@ -17823,12 +17835,18 @@ components:
                 additionalProperties: true
         stackRequired:
           type: boolean
-          description: Whether the clone requires a stack (connector-level) environment to proceed.
+          description: |-
+            `true` when the resource or one of its dependencies references a stack (a hook or
+            wrapper connection that runs on a stack). Send `_stackId` in the clone request: without
+            it the clone fails with 400 `stack_not_found`.
         _stackId:
           type:
             - string
             - 'null'
-          description: The stack id associated with the resource, or null if no stack is involved.
+          description: |-
+            The first stack the resource or a dependency references, or null. Pass it, or another
+            stack in the target environment, as `_stackId` in the clone request; the clone points
+            every stack reference at that one stack.
           examples:
             - 5f8d43a1b9e5a80011a35f2c
     ImportRecordResult:

package/dist/integration.yml

@@ -4609,6 +4609,18 @@ components:
           example:
             5f7c579b6411271af4e7cefa: 64a1234567890abcdef12345
             5f7c579b6411271af4e7cefb: 64a1234567890abcdef12346
+        _stackId:
+          type: string
+          format: objectId
+          x-celigo-refModel: stacks
+          description: |-
+            Stack that every stack reference in the cloned resources (hooks and wrapper
+            connections running on a stack) points at. Required when the clone preview reports
+            `stackRequired: true`: without it the clone fails with 400 `stack_not_found`. The
+            stack must belong to the target environment or be shared with it (404
+            `stack_not_found` for an unknown id, 400 `invalid_stack` otherwise).
+          examples:
+            - 5f8d43a1b9e5a80011a35f2c
       additionalProperties: true
     CloneResponse:
       description: Response body for a clone operation. Some clone endpoints return the cloned resource, while others may return a list of related created resources.
@@ -4669,12 +4681,18 @@ components:
                 additionalProperties: true
         stackRequired:
           type: boolean
-          description: Whether the clone requires a stack (connector-level) environment to proceed.
+          description: |-
+            `true` when the resource or one of its dependencies references a stack (a hook or
+            wrapper connection that runs on a stack). Send `_stackId` in the clone request: without
+            it the clone fails with 400 `stack_not_found`.
         _stackId:
           type:
             - string
             - 'null'
-          description: The stack id associated with the resource, or null if no stack is involved.
+          description: |-
+            The first stack the resource or a dependency references, or null. Pass it, or another
+            stack in the target environment, as `_stackId` in the clone request; the clone points
+            every stack reference at that one stack.
           examples:
             - 5f8d43a1b9e5a80011a35f2c
     Revision:

package/dist/lookupcache.yml

@@ -452,12 +452,14 @@ paths:
         strings, or objects — arrays at the top level are rejected (wrap them in an
         object). One invalid entry fails the entire batch and nothing in it is written:
         a bad value returns `400 invalid_value`, an empty, missing, or over-length
-        key returns `400 cache_dynamodb_invalid_key`, and a key that appears twice in
-        the batch returns 400 "Duplicate keys found in the request".
+        key, or one holding a tab, newline, carriage return or NUL, returns
+        `400 cache_dynamodb_invalid_key`, and a key that appears twice in the batch
+        returns 400 "Duplicate keys found in the request".
 
-        The service rejects batches larger than ~1000 entries or ~5 MB of JSON.
-        Callers uploading more than that should split their payload; the Celigo CLI
-        auto-batches at 1000 entries / 5 MB and concatenates the per-key results.
+        One request takes at most 1000 entries, each entry at most 64 KB, and at most 5 MB of
+        JSON in all (413, "request entity too large!"). Callers uploading more than that should
+        split their payload; the Celigo CLI auto-batches at 1000 entries / 5 MB and concatenates
+        the per-key results.
         Each cache is capped at 50 MB and the per-environment aggregate is 1 GB.
       parameters:
         - name: _id
@@ -511,6 +513,17 @@ paths:
           $ref: '#/components/responses/401-unauthorized'
         '404':
           $ref: '#/components/responses/404-not-found'
+        '413':
+          description: The request body is over 5 MB of JSON. Split the batch.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+              examples:
+                too_large:
+                  value:
+                    errors:
+                      - message: request entity too large!
     delete:
       x-internal: false
       operationId: deleteLookupCacheDataKeys
@@ -1009,12 +1022,18 @@ components:
                 additionalProperties: true
         stackRequired:
           type: boolean
-          description: Whether the clone requires a stack (connector-level) environment to proceed.
+          description: |-
+            `true` when the resource or one of its dependencies references a stack (a hook or
+            wrapper connection that runs on a stack). Send `_stackId` in the clone request: without
+            it the clone fails with 400 `stack_not_found`.
         _stackId:
           type:
             - string
             - 'null'
-          description: The stack id associated with the resource, or null if no stack is involved.
+          description: |-
+            The first stack the resource or a dependency references, or null. Pass it, or another
+            stack in the target environment, as `_stackId` in the clone request; the clone points
+            every stack reference at that one stack.
           examples:
             - 5f8d43a1b9e5a80011a35f2c
     LookupCacheDataEntry:
@@ -1034,7 +1053,8 @@ components:
           description: |-
             Lookup key. Treated as an opaque string by the cache — case-sensitive, no
             normalization. The same cache can hold multiple entries that differ only in
-            case (e.g. `CA` and `ca`).
+            case (e.g. `CA` and `ca`). An upsert also refuses a key that holds a tab, a newline,
+            a carriage return or a NUL character, with the same `cache_dynamodb_invalid_key`.
           examples:
             - CA
             - ext-customer-12345
@@ -1071,9 +1091,9 @@ components:
         Request body for upserting key-value entries into a lookup cache. `data` must be
         a non-empty array. Keys already present are overwritten; new keys are created.
 
-        The service rejects batches larger than ~1000 entries or ~5 MB — callers inserting
-        more than that should split into multiple requests (the Celigo CLI auto-batches
-        at 1000 entries / 5 MB).
+        One request takes at most 1000 entries, each entry at most 64 KB, and at most 5 MB of
+        JSON in all (413) — callers inserting more than that should split into multiple
+        requests (the Celigo CLI auto-batches at 1000 entries / 5 MB).
       properties:
         data:
           type: array

package/dist/marketplace.yml

@@ -154,9 +154,17 @@ paths:
         `type` tells you which install route to use afterwards:
         `POST /v1/integrations/template/{_id}` for `integration`,
         `POST /v1/mcpservers/template/{_templateId}` for `mcpserver`.
-        `stackRequired` is `true` when the template includes NetSuite-distributed
-        resources that need a dedicated stack — the installer prompts for one
-        before the install proceeds.
+        `stackRequired` is `true` when the template has hooks or wrapper
+        connections that run on a stack: the marketplace installer prompts for
+        one; `POST /v1/integrations/template/{_id}`, for a template it accepts
+        (no `template_zip` install step), needs it as `_stackId`; and an
+        MCP-server template's install adds a stack step to the integration it
+        creates.
+
+        Previewing an MCP-server template needs the same install permission as
+        installing it (403 for a monitor or integration-level user whose access
+        doesn't allow creating integrations); an integration template's preview
+        needs none.
 
         The ID must belong to a Template, not a Connector (Integration App).
         Connector IDs from `/v1/published` return 404 here -- pull template
@@ -234,6 +242,14 @@ paths:
                             concurrencyLevel: 1
         '401':
           $ref: '#/components/responses/401-unauthorized'
+        '403':
+          description: |-
+            An MCP-server template previewed by a user who may not install templates (a monitor
+            or integration-level user whose access doesn't allow creating integrations).
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
         '404':
           description: |-
             No template matched the id. Most commonly: the id belongs to a
@@ -887,10 +903,15 @@ components:
         stackRequired:
           type: boolean
           description: |-
-            `true` when the template includes NetSuite-distributed resources
-            that need a dedicated stack — the installer prompts for one before
-            the install proceeds. `false` for Shopify / HTTP / file-only
-            templates.
+            `true` when the template has an export or import hook, or a wrapper
+            connection, that runs on a stack (a function with no script). The
+            marketplace installer asks for the stack. Through the API, an
+            integration template that `POST /v1/integrations/template/{_id}`
+            accepts (no `template_zip` install step) needs `_stackId` in the body,
+            or the install fails with 400 `stack_not_found`; so does a zip
+            installed with `POST /v1/integrations/template`. An MCP-server
+            template's install takes no body: the integration it creates for a
+            tool-bearing template gets a stack install step instead.
   responses:
     401-unauthorized:
       description: |-

package/dist/mcp-server.yml

@@ -4198,11 +4198,13 @@ components:
                 after which the flag switches itself off), and concurrency climbs back toward
                 `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 machinery moves it back toward the target. Recovery never runs on `ftp`
+                connections: FTP errors aren't treated as rate limits.
               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.
                 - 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 an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`; while this is true a create sets `ftp.concurrencyLevel` to `ftp.targetConcurrencyLevel`, or to 1 without one.
             enableMicroBatchForOneToMany:
               type: boolean
               default: true
@@ -4820,6 +4822,10 @@ components:
             FTP servers often have low connection limits — keep this value conservative.
             Send no more than the account's licensed maximum, the license's `concurrency` (25 standard,
             50 with an Environments license).
+            While `autoRecoverRateLimitErrors` is true, which a create gets unless it sends `false`, a create
+            ignores the value sent here and sets this field to `targetConcurrencyLevel`, or to 1 when no
+            target is sent. To start higher, send `targetConcurrencyLevel` too, or create with
+            `autoRecoverRateLimitErrors: false`.
             Unlike the rest of the `ftp` object, a `PUT` that omits this field keeps the stored value instead of clearing it.
           minimum: 1
           maximum: 50
@@ -4829,8 +4835,9 @@ components:
         targetConcurrencyLevel:
           type: integer
           description: |
-            Target concurrency level for auto-scaling. The system adjusts concurrency
-            between 1 and this value based on server response feedback.
+            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.
           minimum: 1
@@ -4861,9 +4868,9 @@ components:
           type: integer
           readOnly: true
           description: |-
-            Server-maintained mirror of `multiThreadCount` used by concurrency
-            auto-scaling. Present only when rate-limit auto-recovery applies;
-            recomputed on save.
+            Server-maintained mirror of `multiThreadCount`, present while
+            `autoRecoverRateLimitErrors` is true and `targetConcurrencyLevel` is
+            set; recomputed on save.
       if:
         properties:
           type:

package/dist/stack.yml

@@ -106,7 +106,7 @@ paths:
         after creation via `GET /v1/stacks/{_id}/systemToken`.
       x-celigo-ai-guidance:
         - |-
-          - For `type=server`, provide `server.hostURI` (and optional `server.ipRanges`).
+          - For `type=server`, provide `server.hostURI`. Don't send `server.ipRanges`: it's deprecated and nothing enforces it.
           - For `type=lambda`, provide AWS credentials and function details under `lambda`.
       operationId: createStack
       tags:

package/dist/template.yml

@@ -22,8 +22,13 @@ tags:
 
       The template lifecycle is: create → upload zip (via `GET /v1/s3SignedURL`) → publish.
 
-      All endpoints require a **Partner account** — non-partner callers
-      receive 403 `access_restricted`.
+      Creating, updating, uploading and publishing templates requires a
+      **Partner account** — non-partner callers receive 403
+      `access_restricted`. Installing a template (`/v1/integrations/template`
+      routes) needs install permission instead: the account owner,
+      administrators and manage users have it, and monitor or
+      integration-level users only when their access allows creating
+      integrations.
 
       ## Template schema
 
@@ -377,6 +382,18 @@ paths:
                   example:
                     61f92026dd053843b5d72350: 64a1234567890abcdef12345
                     61f92026dd053843b5d72351: 64a1234567890abcdef12346
+                _stackId:
+                  type: string
+                  format: objectId
+                  x-celigo-refModel: stacks
+                  description: |-
+                    Stack for the template's hooks and wrapper connections that run on a stack.
+                    Required when the template preview reports `stackRequired: true`: without
+                    it the install fails with 400 `stack_not_found`. The stack must belong to
+                    the environment or be shared with it (404 `stack_not_found` for an unknown
+                    id, 400 `invalid_stack` otherwise).
+                  examples:
+                    - 5f8d43a1b9e5a80011a35f2c
               required:
                 - connectionMap
             examples:
@@ -419,9 +436,12 @@ paths:
                       _id: 6405b9d83496e05ff253d594
         '400':
           description: |-
-            Missing or empty `connectionMap`, or the template is an MCP server
+            Missing or empty `connectionMap`; the template is an MCP server
             template that must be installed through
-            `POST /v1/mcpservers/template/{_templateId}`.
+            `POST /v1/mcpservers/template/{_templateId}`; the template needs a
+            stack and the body has no `_stackId` (`stack_not_found`); or the
+            `_stackId` names a stack that neither belongs to this environment nor
+            is shared with it (`invalid_stack`).
           content:
             application/json:
               schema:
@@ -438,12 +458,18 @@ paths:
                     errors:
                       - code: invalid_template
                         message: MCP server templates cannot be installed through the Integration template path.
+                missingStack:
+                  summary: The preview reported stackRequired and no _stackId was sent
+                  value:
+                    errors:
+                      - code: stack_not_found
+                        message: The integration template has stack reference but _stackId not found in the request body.
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '403':
-          $ref: '#/components/responses/403-forbidden'
+          $ref: '#/components/responses/403-cannot-install'
         '404':
-          description: Template not found.
+          description: Template not found, or no stack has the `_stackId` sent (`stack_not_found`).
           content:
             application/json:
               schema:
@@ -539,7 +565,7 @@ paths:
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '403':
-          $ref: '#/components/responses/403-forbidden'
+          $ref: '#/components/responses/403-cannot-install'
         '404':
           description: The `runKey` does not match any uploaded zip.
           content:
@@ -583,6 +609,16 @@ paths:
                     the template zip file.
                   examples:
                     - abc123def456
+                _stackId:
+                  type: string
+                  format: objectId
+                  x-celigo-refModel: stacks
+                  description: |-
+                    Stack for the template's hooks and wrapper connections that run on a stack.
+                    Required when the preview reports `stackRequired: true` (400
+                    `stack_not_found` without it).
+                  examples:
+                    - 5f8d43a1b9e5a80011a35f2c
               required:
                 - runKey
             examples:
@@ -618,7 +654,7 @@ paths:
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '403':
-          $ref: '#/components/responses/403-forbidden'
+          $ref: '#/components/responses/403-cannot-install'
         '404':
           description: The `runKey` does not match any uploaded zip.
           content:
@@ -978,5 +1014,27 @@ components:
                 errors:
                   - code: invalid_request
                     message: The request body failed validation.
+    403-cannot-install:
+      description: |-
+        The caller may not install templates. The account owner, administrators and manage users
+        can; a monitor user or a user with access to specific integrations only can install a
+        template only when their access allows creating integrations
+        (`allowIntegrationWorkspaceCreation`).
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/Error'
+          examples:
+            cannotInstall:
+              value:
+                errors:
+                  - code: access_restricted
+                    message: Users with monitor or tile level manage permissions cannot install templates. Ask an account owner or administrator to increase your permissions, or contact another user with at least account level manage permissions to install the template.
+            otherRole:
+              summary: Any other role without install permission
+              value:
+                errors:
+                  - code: access_restricted
+                    message: The role which you are associated with doesn't have the required permissions to perform the action.
 x-enable-proxy: true
 x-internal: false

package/dist/tool.yml

@@ -776,6 +776,15 @@ paths:
                     format: objectId
                   examples:
                     - 6ac1ef4a38b24d95ffac2545: 6ac1ef4a38b24d95ffac2545
+                _stackId:
+                  type: string
+                  format: objectId
+                  x-celigo-refModel: stacks
+                  description: |-
+                    Stack that the cloned steps' stack references point at. Required when the clone
+                    preview reports `stackRequired: true` (400 `stack_not_found` without it).
+                  examples:
+                    - 5f8d43a1b9e5a80011a35f2c
             examples:
               default:
                 summary: Clone a tool with no connection-bearing steps into the same integration
@@ -7723,11 +7732,13 @@ components:
                 after which the flag switches itself off), and concurrency climbs back toward
                 `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 machinery moves it back toward the target. Recovery never runs on `ftp`
+                connections: FTP errors aren't treated as rate limits.
               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.
                 - 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 an `ftp` connection recovery never runs, and transfer threads are `ftp.multiThreadCount`; while this is true a create sets `ftp.concurrencyLevel` to `ftp.targetConcurrencyLevel`, or to 1 without one.
             enableMicroBatchForOneToMany:
               type: boolean
               default: true
@@ -8345,6 +8356,10 @@ components:
             FTP servers often have low connection limits — keep this value conservative.
             Send no more than the account's licensed maximum, the license's `concurrency` (25 standard,
             50 with an Environments license).
+            While `autoRecoverRateLimitErrors` is true, which a create gets unless it sends `false`, a create
+            ignores the value sent here and sets this field to `targetConcurrencyLevel`, or to 1 when no
+            target is sent. To start higher, send `targetConcurrencyLevel` too, or create with
+            `autoRecoverRateLimitErrors: false`.
             Unlike the rest of the `ftp` object, a `PUT` that omits this field keeps the stored value instead of clearing it.
           minimum: 1
           maximum: 50
@@ -8354,8 +8369,9 @@ components:
         targetConcurrencyLevel:
           type: integer
           description: |
-            Target concurrency level for auto-scaling. The system adjusts concurrency
-            between 1 and this value based on server response feedback.
+            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.
           minimum: 1
@@ -8386,9 +8402,9 @@ components:
           type: integer
           readOnly: true
           description: |-
-            Server-maintained mirror of `multiThreadCount` used by concurrency
-            auto-scaling. Present only when rate-limit auto-recovery applies;
-            recomputed on save.
+            Server-maintained mirror of `multiThreadCount`, present while
+            `autoRecoverRateLimitErrors` is true and `targetConcurrencyLevel` is
+            set; recomputed on save.
       if:
         properties:
           type:
@@ -38466,12 +38482,18 @@ components:
                 additionalProperties: true
         stackRequired:
           type: boolean
-          description: Whether the clone requires a stack (connector-level) environment to proceed.
+          description: |-
+            `true` when the resource or one of its dependencies references a stack (a hook or
+            wrapper connection that runs on a stack). Send `_stackId` in the clone request: without
+            it the clone fails with 400 `stack_not_found`.
         _stackId:
           type:
             - string
             - 'null'
-          description: The stack id associated with the resource, or null if no stack is involved.
+          description: |-
+            The first stack the resource or a dependency references, or null. Pass it, or another
+            stack in the target environment, as `_stackId` in the clone request; the clone points
+            every stack reference at that one stack.
           examples:
             - 5f8d43a1b9e5a80011a35f2c
     DependencyEntry:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.173",
+  "version": "0.2.175",
   "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": "752a338e",
+		"iasCommit": "89a6949a",
 		"generatedAt": "2026-10-22"
 	},
 	"roots": {