@celigo/api-specs 0.2.200 → 0.2.202

package/dist/filestorage.yml

@@ -34,7 +34,9 @@ paths:
         `partUrls`, and `completeUrl` for larger files. Upload the bytes directly
         to those URLs — a single PUT must carry the
         `x-amz-server-side-encryption: AES256` header — then the item flips to
-        active once S3 confirms it; no further API call is needed. Each URL's
+        active once S3 confirms it; no further API call is needed. If the
+        uploaded object is empty (0 bytes), the file is not activated: it is
+        deleted permanently, without passing through the recycle bin. Each URL's
         lifetime is in its `X-Amz-Expires` parameter; once every part already
         issued has been uploaded, a multipart upload fetches further part URLs by
         posting again with the item's `_id`, `uploadId`, and `issuedPartsCount`,
@@ -222,7 +224,12 @@ paths:
                   downloadUrl:
                     type: string
                     format: uri
-                    description: Presigned S3 URL to GET the file's bytes from.
+                    description: |-
+                      Presigned S3 URL to GET the file's bytes from. The bytes are
+                      served as an attachment named after the item: the
+                      `Content-Disposition` header carries an ASCII `filename` in
+                      which non-ASCII characters are replaced with `_`, plus
+                      `filename*=UTF-8''` with the full name percent-encoded.
                     examples:
                       - https://integrator-file-storage.s3.us-west-2.amazonaws.com/file-storage/...
                   expiresIn:
@@ -611,6 +618,17 @@ paths:
                           description: Folder name.
                           examples:
                             - My Files
+                        _integrationId:
+                          type: string
+                          format: objectId
+                          x-celigo-refModel: integrations
+                          description: |-
+                            Integration whose system folder tree contains the listed
+                            folder. Present only on the last entry (the listed folder
+                            itself), and only when that folder is the integration's
+                            root folder or inside it.
+                          examples:
+                            - 6ab1e7ab38d7733b4594d0d2
               examples:
                 listMode:
                   summary: List a folder's children
@@ -839,7 +857,10 @@ paths:
 
         Only files are looked up: a folder's id is treated as unknown, so it
         fails the request or comes back as a `notFound` entry. Read folder
-        metadata from `GET /v1/storage/items`.
+        metadata from `GET /v1/storage/items`. A pending file is returned, as
+        active, once its bytes have landed in storage, even if the upload has not
+        finalized yet; a pending file whose bytes have not been uploaded is
+        treated as unknown.
       operationId: batchGetStorageItems
       tags:
         - File Storage
@@ -1293,9 +1314,12 @@ paths:
         Updates an item's `name` and/or `description`. Renaming keeps the item's
         `_id` stable, so references from flows, exports, imports, and tokens
         survive; a name already held by another live item in the same folder is
-        rejected with 409 `STORAGE_ITEM_ALREADY_EXISTS`. To move an item to a
-        different folder, use `PATCH /v1/storage/items/{_id}/move`; to replace a
-        file's content, use `PATCH /v1/storage/items/{_id}/replace`.
+        rejected with 409 `STORAGE_ITEM_ALREADY_EXISTS`. An integration's root
+        folder (`isSystem`) can be renamed and described too; renaming the
+        integration updates only the folder's `integrationName`, never its
+        `name`. To move an item to a different folder, use
+        `PATCH /v1/storage/items/{_id}/move`; to replace a file's content, use
+        `PATCH /v1/storage/items/{_id}/replace`.
       operationId: updateStorageItem
       tags:
         - File Storage
@@ -1450,7 +1474,9 @@ paths:
         placement are preserved, so every reference to the file stays intact — use
         this instead of delete-and-recreate when a file is referenced by flows or
         exports. The previous content remains downloadable until the replacement
-        finalizes. Rename with `PUT /v1/storage/items/{_id}` instead; this
+        finalizes. Uploading empty (0-byte) content does not replace it: the file
+        itself is deleted permanently, without passing through the recycle bin.
+        Rename with `PUT /v1/storage/items/{_id}` instead; this
         endpoint does not accept a name.
       operationId: replaceStorageFileContent
       tags:
@@ -1565,7 +1591,13 @@ paths:
         file: the destination file keeps its `_id` and takes the source file's
         content, its previous content is discarded, and the source file's `_id`
         is removed — neither goes to the recycle bin, so references to the
-        source file break. A soft-deleted source folder may be
+        source file break. A sub-folder whose name the destination also holds as
+        a folder is merged into it the same way. When the names match but the
+        types differ (a file against a folder), both are kept: the destination
+        item is unchanged, and the source item moves in with its `_id` under the
+        first free `<name> (k)` — the suffix follows the full name, so
+        `report.pdf` lands as `report.pdf (1)`, or `report.pdf (2)` when
+        `report.pdf (1)` is taken. A soft-deleted source folder may be
         merged, which restores its contents into the destination. Folders only —
         move individual files with the move endpoint. Requires delete access on
         the source folder and write access on the destination.
@@ -2425,7 +2457,7 @@ components:
         size:
           type: integer
           format: int64
-          minimum: 0
+          minimum: 1
           description: |-
             Declared size in bytes. Used to reserve quota up front. When omitted,
             the backend reserves a worst-case estimate (1 GB for single,
@@ -2765,6 +2797,18 @@ components:
             integration purges them.
           examples:
             - 6ab1e7ab38d7733b4594d0d2
+        _fileServerAccountId:
+          type: string
+          format: objectId
+          readOnly: true
+          x-celigo-refModel: fileserveraccounts
+          description: |-
+            File Server account that uploaded the file over SFTP, or that most
+            recently replaced its content over SFTP. Absent for folders and for
+            files uploaded through this API; replacing the content through this
+            API keeps the current value.
+          examples:
+            - 6ac0f3e1b2d4a5001c7e9f10
         integrationName:
           type: string
           readOnly: true
@@ -2772,6 +2816,9 @@ components:
             Name of the integration an integration root folder belongs to. Present
             only on that root folder (the `isSystem` folder at the account root);
             items inside the tree carry `_integrationId` but not this field.
+            Follows the integration's name when the integration is renamed, while
+            the folder's own `name` keeps the value it was created with or last
+            renamed to, so the two can differ.
           examples:
             - Order to cash
         __ancestorIds:
@@ -2802,10 +2849,15 @@ components:
           maxLength: 256
           readOnly: true
           description: |-
-            Media type recorded at upload time, used to set the download
-            Content-Type. Present when type is file; absent for folders and for
-            files uploaded without a declared type. Matched case-sensitively by
-            the `mimeType` and `mimeType_nin` list filters.
+            Media type used to set the download Content-Type. Present when type is
+            file; absent for folders and for files uploaded through this API
+            without a declared type. A file uploaded over the SFTP file server gets
+            the type its name's extension maps to, ignoring a trailing `.filepart`,
+            `.part`, or `.tmp`, or `application/octet-stream` when the extension is
+            unknown. An SFTP rename replaces an absent or `application/octet-stream`
+            value when the new extension maps to a known type; renames made with an
+            API token leave the value unchanged. Matched case-sensitively by the
+            `mimeType` and `mimeType_nin` list filters.
           examples:
             - image/png
         description:
@@ -2831,11 +2883,13 @@ components:
           type: boolean
           readOnly: true
           description: |-
-            When true, the platform created the item (for example a system or
-            integration folder) and protects it — rename, move, content replace,
-            copy, delete, and purge are rejected with 403
-            `STORAGE_SYSTEM_ITEM_PROTECTED` ("System items cannot be modified or
-            deleted").
+            When true, the platform created the item (for example an
+            integration's root folder) and protects it: moving it, merging it
+            into another folder, deleting it, and restoring or purging it from
+            the recycle bin are rejected with 403 `STORAGE_SYSTEM_ITEM_PROTECTED`
+            ("System items cannot be modified or deleted"; a per-item error in a
+            bulk move). Renaming it and editing its description with
+            `PUT /v1/storage/items/{_id}` are allowed.
         deletedAt:
           type: string
           format: date-time
@@ -3049,7 +3103,7 @@ components:
         size:
           type: integer
           format: int64
-          minimum: 0
+          minimum: 1
           description: |-
             Declared size in bytes of the replacement content, used to reserve
             quota. Reconciled to the real size when the upload finalizes.

package/dist/flow.yml

@@ -4369,6 +4369,12 @@ components:
         step's response is discarded after the call.
 
         `fields` and `lists` are plain arrays — exactly the shape GET returns.
+        Entries sent empty (`null`, `{}`, or every value `null`) are dropped on
+        save. Any other `fields` entry left with neither `extract` nor
+        `generate`, or `lists` entry with neither `generate` nor `fields` —
+        what is left of a wrapped or misspelled value such as
+        `"fields": {"type": [...]}` — fails the save with 422
+        `invalid_field_value`.
 
         Extract paths do NOT read the raw application response — the platform
         wraps every response in a canonical per-record envelope first, and
@@ -4425,10 +4431,10 @@ components:
           runs on top of it in a test run).
         - |-
           Send `fields` and `lists` as bare arrays, exactly as GET returns them.
-          Never wrap either in an object (e.g. `"fields": {"type": [...]}`): the
-          API does not reject that shape — it returns 200 and silently persists
-          `fields: [null]` / `lists: [{"fields": []}]`, erasing the step's
-          response mappings.
+          A wrapped value (e.g. `"fields": {"type": [...]}`), an empty object
+          (`"fields": {}`), or an entry holding only unknown keys fails the save
+          with 422 `invalid_field_value`, and the error's `field` names the array
+          (e.g. `pageProcessors[0].responseMapping.fields`).
         - |-
           responseMapping is fully replaced on PUT: omitting it resets the step
           to empty `{"fields": [], "lists": []}`. Always send the complete

package/dist/integration.yml

@@ -1597,11 +1597,13 @@ paths:
       operationId: registerConnectionToIntegrationByBody
       tags:
         - Integrations
-      summary: Register a connection to an integration (by body)
+      summary: Register connections to an integration (by body)
       description: |-
-        Registers a single connection to the integration by passing the connection id in the request
-        body. Alternatively, use `PUT /v1/integrations/{_id}/connections/{_connectionId}/register` to
-        register by path parameter.
+        Registers one or more connections to the integration, adding them to its
+        `_registeredConnectionIds` list. The request body is a bare JSON array of
+        connection ids; duplicates and ids that are already registered are ignored.
+        Alternatively, use `PUT /v1/integrations/{_id}/connections/{_connectionId}/register`
+        to register a single connection by path parameter.
       parameters:
         - name: _id
           in: path
@@ -1618,24 +1620,40 @@ paths:
         content:
           application/json:
             schema:
-              type: object
-              required:
-                - _connectionId
-              properties:
-                _connectionId:
-                  type: string
-                  format: objectId
-                  x-celigo-refModel: connections
-                  examples:
-                    - 626168f90b6ef816b50c82d7
-                  description: The id of the connection to register.
+              type: array
+              description: Connection ids to register.
+              items:
+                type: string
+                format: objectId
+                x-celigo-refModel: connections
             examples:
               default:
                 value:
-                  _connectionId: 69680d7111d1437fbcbce534
+                  - 626168f90b6ef816b50c82d7
+                  - 6553ebdeda62bb22e7fa81ff
       responses:
         '204':
-          description: Connection registered successfully. No body returned.
+          description: Connections registered successfully. No body returned.
+        '400':
+          description: |-
+            The body is not a JSON array (`invalid_request`), or an entry in the
+            array is not a valid ObjectId (`invalid_ref`).
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+              examples:
+                notAnArray:
+                  summary: 'An object body such as {"_connectionId": "..."}'
+                  value:
+                    errors:
+                      - code: invalid_request
+                        message: Request body should be a JSON array of _connectionId values.
+                invalidId:
+                  value:
+                    errors:
+                      - code: invalid_ref
+                        message: Please provide a valid _connectionId.
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '404':
@@ -1934,11 +1952,25 @@ paths:
         '204':
           description: Lookup caches registered successfully. No body returned.
         '400':
-          description: An entry in the array is not a valid ObjectId.
+          description: |-
+            The body is not a JSON array (`invalid_request`), or an entry in the
+            array is not a valid ObjectId (`invalid_ref`).
           content:
             application/json:
               schema:
                 $ref: '#/components/schemas/Error'
+              examples:
+                notAnArray:
+                  summary: 'An object body such as {"_lookupCacheId": "..."}'
+                  value:
+                    errors:
+                      - code: invalid_request
+                        message: Request body should be a JSON array of _lookupCacheId values.
+                invalidId:
+                  value:
+                    errors:
+                      - code: invalid_ref
+                        message: Please provide a valid _lookupCacheId.
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '404':

package/dist/marketplace.yml

@@ -435,6 +435,7 @@ paths:
                       name: Error automation via integrator.io APIs
                       docType: Template
                       type: integration
+                      celigoAgentSupported: false
                       description: Template that automates flow error handling via integrator.io APIs.
                       applications:
                         - integrator.io
@@ -544,6 +545,15 @@ components:
             on Connector entries, which install through their own route.
           examples:
             - integration
+        celigoAgentSupported:
+          type: boolean
+          description: |-
+            When true, the template is flagged for installation through the Celigo Agent (Ora)
+            guided install. Present on every `docType: Template` entry of
+            `POST /v1/published/combined`; absent on Connector entries and from
+            `GET /v1/templates/published`.
+          examples:
+            - false
         imageURL:
           type: string
           description: |-