@celigo/api-specs 0.2.183 → 0.2.185

package/dist/tool.yml

@@ -8511,6 +8511,17 @@ components:
           minimum: 1
           maximum: 50
           default: 5
+        _tpConnectorId:
+          type: string
+          format: objectId
+          x-celigo-refModel: tradingpartnerconnectors
+          description: |-
+            Trading partner connector this S3 connection was provisioned from during partner
+            onboarding. Stored and returned here, under `s3`, like `ftp._tpConnectorId` and
+            `as2._tpConnectorId` on the other partner transports; a top-level `_tpConnectorId` on
+            the connection body is not stored. Omit for a standalone S3 connection.
+          examples:
+            - 66a1b2c3d4e5f60718293a4b
       if:
         properties:
           authType:
@@ -10612,8 +10623,35 @@ components:
                 sa-east-1: South America (Sao Paulo).
                 ca-central-1: Canada (Central).
               x-lowercase: true
+        useSSL:
+          type: boolean
+          writeOnly: true
+          description: |-
+            When true, the database connection is made over SSL/TLS and the certificate material in
+            `ssl` applies — the connection form's **Use SSL** switch (offered for MySQL, MariaDB and
+            PostgreSQL). Accepted on POST and PUT only: the platform stores it as `ssl.enabled`, which
+            is the field GET returns. A PUT that omits `useSSL` clears the stored `ssl.enabled` — send
+            it on every update that should keep SSL on.
+          examples:
+            - true
+          x-celigo-ai-guidance:
+            - |-
+              A body built from a GET carries `ssl.enabled` but never `useSSL`, so sending it back as a
+              PUT turns SSL off: add `"useSSL": true` to every update of a connection that uses SSL.
+              Setting `ssl.enabled` in the body changes nothing (verified live 2026-10-23 on a PostgreSQL
+              connection: a PUT of the GET body cleared `ssl`, a PUT with `useSSL: true` set it again,
+              and a PUT with `ssl.enabled: true` but no `useSSL` cleared it).
         ssl:
-          $ref: '#/components/schemas/SSL'
+          allOf:
+            - $ref: '#/components/schemas/SSL'
+            - type: object
+              properties:
+                enabled:
+                  type: boolean
+                  readOnly: true
+                  description: |-
+                    When true, SSL/TLS is on for this database connection. Set from `useSSL` on
+                    write and returned here on read; a value sent in this field is ignored.
         options:
           type: array
           description: |
@@ -16335,7 +16373,11 @@ components:
                           description: When true, the value is a NetSuite internal ID reference.
                         isKey:
                           type: boolean
-                          description: When true, this field is a key field for matching existing sublist lines.
+                          description: |-
+                            When true, this field is a key for matching the record's existing sublist lines: a
+                            mapped line updates the one existing line whose key fields hold the same values. `lists`
+                            says which records match lines, the keys used when no field sets `isKey`, and what a
+                            line that matches no line, or several, does.
                         immutable:
                           type: boolean
                           description: When true, this field is only set on record creation, not on updates.
@@ -16511,6 +16553,40 @@ components:
                     description: Field mappings for each column in the sublist.
               description: |
                 Sublist (line-item) mappings. Each entry maps source data to a NetSuite sublist.
+
+                Each mapped line updates the one existing line whose key fields hold the same values: its
+                `isKey` fields, or, with none, the sublist's default key. The existing lines are the stored
+                record's on an update, and on a transform (`Created From`: the body field
+                `celigo_nlobjTransformId` holds the source transaction's internal id) the lines the transform
+                fills in. Default keys:
+
+                - the item (`item`, else `itemkey` or `itemname`) on item fulfillments, item receipts,
+                  invoices, cash sales, cash refunds, return authorizations, bin worksheets, inbound shipment
+                  receipts and inventory counts, and on an assembly build's `component` sublist;
+                - the applied transaction (`refnum`) on the `apply`, `credit` and `deposit` sublists of
+                  customer and vendor payments, credit memos, vendor credits and customer refunds;
+                - `docnumber` on a deposit's `payment` sublist;
+                - `vendor` and `language` on an item record's `itemvendor` and `translations` sublists.
+
+                A sublist with neither, such as a sales order's or purchase order's `item`, matches nothing, so
+                an update adds every mapped line after the existing ones. Two matching lines fail the record
+                with `MULTIPLE_LINES_WITH_SAME_KEYS` ("Multiple lines found with keys item=<value> ..."). A
+                line that matches none is added as a new line, which an item fulfillment's `item` sublist
+                refuses with `SSS_INVALID_SUBLIST_OPERATION`: its lines are its order's.
+              x-celigo-ai-guidance:
+                - |-
+                  To make an update replace a sublist's lines, also map the body field
+                  `celigo_replaceAllLines_<sublist id>` (for example `celigo_replaceAllLines_item`) to `true`:
+                  the existing lines no mapped line matched are removed, then the mapped lines are written. Where
+                  lines can't be removed it clears them instead: `itemreceive` false on an item fulfillment or
+                  item receipt, `apply` false on an `apply` sublist. On a sublist with no `isKey` field and no
+                  default key every existing line is unmatched, so all are replaced; with a default key, the lines
+                  it matches stay.
+                - |-
+                  Key an update on a value each line holds once: a line id the record's create wrote to a line
+                  field, or, on a fulfillment, the order line's id mapped to `orderline`. Keying on the item fails
+                  with `MULTIPLE_LINES_WITH_SAME_KEYS` when an order holds the same item on two lines, and records
+                  that already hold repeated lines fail the same way once a key is set.
           x-celigo-agent:
             - mapping
         lookups:
@@ -33132,6 +33208,12 @@ components:
         sendAuthForFileDownloads:
           type: boolean
           description: When true, includes authentication headers when downloading files.
+        isRest:
+          type: boolean
+          description: |-
+            Internal flag marking an export built with the legacy REST form and stored in the unified
+            HTTP framework. Set by the platform when it converts a legacy `rest` body; not configured
+            directly. Returned on every HTTP export, `false` unless the export was converted.
         _httpConnectorEndpointId:
           type: string
           format: objectId

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.183",
+  "version": "0.2.185",
   "private": false,
   "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
   "keywords": [