@celigo/api-specs 0.2.194 → 0.2.196

package/dist/export.yml

@@ -5908,9 +5908,13 @@ components:
           type: string
           description: |-
             Bearer token that a system pushing data into this export sends as
-            `Authorization: Bearer <token>`. Optional — most distributed listeners (NetSuite,
-            Salesforce real-time) use no token. Write-only and stored encrypted; treat it as a
-            sensitive credential.
+            `Authorization: Bearer <token>`. Optional — Salesforce real-time listeners use no token.
+            For a NetSuite listener the platform generates it when the export is saved as a listener,
+            writes it to the listener's registration record in NetSuite, and generates a new one only
+            when a save re-creates the listener (a `type` change back to `distributed`) — never on a
+            flow toggle or another `PUT`; a client sets and keeps a value itself only for a system of
+            its own that pushes to the export's data endpoint. Stored encrypted and returned masked;
+            treat it as a sensitive credential.
           format: password
           examples:
             - eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
@@ -11242,6 +11246,16 @@ components:
               `netsuite.type: distributed`. Saving it creates a user event script deployment on the
               record type that runs after submit, so records arrive only when NetSuite saves one and
               `POST /v1/exports/preview` cannot sample it.
+            - |-
+              Saving the listener also registers it in NetSuite (the SuiteApp's record for this export,
+              holding its record type, contexts, types, qualifier, endpoint URL and token); a `PUT` that
+              keeps the export a listener re-pushes those fields, leaves the token as it is, and sets
+              the registration's disabled state from the body's `distributed.disabled` (omitted means
+              inactive). A `PUT` that changes `type` to a scheduled value leaves that
+              registration in place and active — NetSuite keeps queuing qualifying saves for an export
+              that no longer listens — so remove or disable the listener's flow rather than converting
+              the step in place, and never treat the conversion as reversible without re-checking
+              `distributed.disabled` afterwards.
           properties:
             recordType:
               type: string
@@ -11315,15 +11329,26 @@ components:
             disabled:
               type: boolean
               description: |-
-                When true, the listener's NetSuite deployment is inactive and record saves no longer
-                trigger the export. Maintained by the platform as the flow is disabled and re-enabled;
-                re-enabling the flow re-registers the deployment. A listener is created disabled, and
-                a flow created already enabled leaves it that way until a flow update sets
-                `disabled: false`, which activates it within seconds.
+                When true, the listener's NetSuite registration is inactive and record saves no longer
+                trigger the export. The platform keeps it in step with the flow — enabling the flow sets
+                it false within seconds, disabling or deleting the flow sets it true — and every save
+                that leaves the export a listener (a create, a `PUT` that keeps it a listener, a `PUT`
+                that makes it `distributed` again after another type) applies the body's value, an
+                omitted field meaning true: a listener is created disabled, a flow created already
+                enabled leaves it so until a flow update sets `disabled: false`, and a `PUT` that omits
+                the field inactivates it.
               x-celigo-ai-guidance:
                 - |-
-                  Pause a listener by disabling its flow, not by setting this field. A listener that has
+                  Pause or resume a listener by disabling or enabling its flow; the field follows. Every
+                  `PUT` of a listener on an enabled flow must carry `disabled: false` — an omitted field or
+                  a stale `true` inactivates the NetSuite registration while the flow stays enabled (the
+                  UI never hits this because it writes back the document it read). A listener that has
                   stopped firing is re-registered by disabling and re-enabling the flow.
+                - |-
+                  A `PUT` that changes `type` back to `distributed` after the export was another type
+                  re-creates the listener: send `disabled: false` when the flow is enabled, or it comes
+                  back inactive until a follow-up `PUT` with `disabled: false` or a disable and re-enable
+                  of the flow activates it.
             executionType:
               type: array
               description: |-

package/dist/import.yml

@@ -4145,6 +4145,10 @@ components:
             - |-
               Validated via the dedicated `PUT /v1/netsuiteDA/previewImportMappingFields`
               endpoint (NOT `/v1/processors/mapperProcessor`).
+            - |-
+              The preview resolves the mapping without writing to NetSuite: the multiselect row
+              NetSuite rejected at save time (see `fields[].dataType`) rendered exactly like the
+              row it accepted, so a passed preview does not prove the save.
           properties:
             fields:
               type: array
@@ -4180,9 +4184,21 @@ components:
                     type: string
                     description: |
                       Data type hint for the field value (e.g., "string", "number", "date", "boolean").
+                      Omit it on a multiselect reference row (`internalId: true`), which takes an array
+                      of numeric internal ids.
+                    x-celigo-ai-guidance:
+                      - |-
+                        On a multiselect reference row, `dataType: "stringarray"` with an array of string
+                        ids was written as ONE comma-joined text selection and NetSuite rejected the save
+                        with `Invalid <field> reference key <id1>,<id2>,…`, leaving the field empty; the
+                        same row with no `dataType` and an array of numeric ids saved every id as a
+                        selection.
                   internalId:
                     type: boolean
-                    description: When true, the value is a NetSuite internal ID reference.
+                    description: |-
+                      When true, the value is a NetSuite internal ID reference — the mapper's
+                      "(InternalId)" destination row, stored on the base field id in `generate` rather
+                      than as a `<field>.internalid` suffix.
                   immutable:
                     type: boolean
                     description: When true, this field is only set on record creation, not on updates.

package/dist/tool.yml

@@ -16154,6 +16154,10 @@ components:
             - |-
               Validated via the dedicated `PUT /v1/netsuiteDA/previewImportMappingFields`
               endpoint (NOT `/v1/processors/mapperProcessor`).
+            - |-
+              The preview resolves the mapping without writing to NetSuite: the multiselect row
+              NetSuite rejected at save time (see `fields[].dataType`) rendered exactly like the
+              row it accepted, so a passed preview does not prove the save.
           properties:
             fields:
               type: array
@@ -16189,9 +16193,21 @@ components:
                     type: string
                     description: |
                       Data type hint for the field value (e.g., "string", "number", "date", "boolean").
+                      Omit it on a multiselect reference row (`internalId: true`), which takes an array
+                      of numeric internal ids.
+                    x-celigo-ai-guidance:
+                      - |-
+                        On a multiselect reference row, `dataType: "stringarray"` with an array of string
+                        ids was written as ONE comma-joined text selection and NetSuite rejected the save
+                        with `Invalid <field> reference key <id1>,<id2>,…`, leaving the field empty; the
+                        same row with no `dataType` and an array of numeric ids saved every id as a
+                        selection.
                   internalId:
                     type: boolean
-                    description: When true, the value is a NetSuite internal ID reference.
+                    description: |-
+                      When true, the value is a NetSuite internal ID reference — the mapper's
+                      "(InternalId)" destination row, stored on the base field id in `generate` rather
+                      than as a `<field>.internalid` suffix.
                   immutable:
                     type: boolean
                     description: When true, this field is only set on record creation, not on updates.
@@ -31205,9 +31221,13 @@ components:
           type: string
           description: |-
             Bearer token that a system pushing data into this export sends as
-            `Authorization: Bearer <token>`. Optional — most distributed listeners (NetSuite,
-            Salesforce real-time) use no token. Write-only and stored encrypted; treat it as a
-            sensitive credential.
+            `Authorization: Bearer <token>`. Optional — Salesforce real-time listeners use no token.
+            For a NetSuite listener the platform generates it when the export is saved as a listener,
+            writes it to the listener's registration record in NetSuite, and generates a new one only
+            when a save re-creates the listener (a `type` change back to `distributed`) — never on a
+            flow toggle or another `PUT`; a client sets and keeps a value itself only for a system of
+            its own that pushes to the export's data endpoint. Stored encrypted and returned masked;
+            treat it as a sensitive credential.
           format: password
           examples:
             - eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
@@ -36539,6 +36559,16 @@ components:
               `netsuite.type: distributed`. Saving it creates a user event script deployment on the
               record type that runs after submit, so records arrive only when NetSuite saves one and
               `POST /v1/exports/preview` cannot sample it.
+            - |-
+              Saving the listener also registers it in NetSuite (the SuiteApp's record for this export,
+              holding its record type, contexts, types, qualifier, endpoint URL and token); a `PUT` that
+              keeps the export a listener re-pushes those fields, leaves the token as it is, and sets
+              the registration's disabled state from the body's `distributed.disabled` (omitted means
+              inactive). A `PUT` that changes `type` to a scheduled value leaves that
+              registration in place and active — NetSuite keeps queuing qualifying saves for an export
+              that no longer listens — so remove or disable the listener's flow rather than converting
+              the step in place, and never treat the conversion as reversible without re-checking
+              `distributed.disabled` afterwards.
           properties:
             recordType:
               type: string
@@ -36612,15 +36642,26 @@ components:
             disabled:
               type: boolean
               description: |-
-                When true, the listener's NetSuite deployment is inactive and record saves no longer
-                trigger the export. Maintained by the platform as the flow is disabled and re-enabled;
-                re-enabling the flow re-registers the deployment. A listener is created disabled, and
-                a flow created already enabled leaves it that way until a flow update sets
-                `disabled: false`, which activates it within seconds.
+                When true, the listener's NetSuite registration is inactive and record saves no longer
+                trigger the export. The platform keeps it in step with the flow — enabling the flow sets
+                it false within seconds, disabling or deleting the flow sets it true — and every save
+                that leaves the export a listener (a create, a `PUT` that keeps it a listener, a `PUT`
+                that makes it `distributed` again after another type) applies the body's value, an
+                omitted field meaning true: a listener is created disabled, a flow created already
+                enabled leaves it so until a flow update sets `disabled: false`, and a `PUT` that omits
+                the field inactivates it.
               x-celigo-ai-guidance:
                 - |-
-                  Pause a listener by disabling its flow, not by setting this field. A listener that has
+                  Pause or resume a listener by disabling or enabling its flow; the field follows. Every
+                  `PUT` of a listener on an enabled flow must carry `disabled: false` — an omitted field or
+                  a stale `true` inactivates the NetSuite registration while the flow stays enabled (the
+                  UI never hits this because it writes back the document it read). A listener that has
                   stopped firing is re-registered by disabling and re-enabling the flow.
+                - |-
+                  A `PUT` that changes `type` back to `distributed` after the export was another type
+                  re-creates the listener: send `disabled: false` when the flow is enabled, or it comes
+                  back inactive until a follow-up `PUT` with `disabled: false` or a disable and re-enable
+                  of the flow activates it.
             executionType:
               type: array
               description: |-

package/package.json

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

package/schemas.json

@@ -1,8 +1,8 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "15622d32",
-		"generatedAt": "2026-10-26"
+		"iasCommit": "f53bf606",
+		"generatedAt": "2026-10-27"
 	},
 	"roots": {
 		"aiagent": 128,