@celigo/api-specs 0.2.28 → 0.2.30

package/dist/tool.yml

@@ -2075,9 +2075,11 @@ components:
             This field supports THREE DISTINCT PATTERNS that are easily distinguished:
 
             **1. json Path Syntax**
-            - MUST start with '$.' prefix
+            - MUST start with '$' — the record root. An object record is addressed as
+              '$.field'; a grouped (array) record as '$[0].field' / '$[*].field'
             - Used for precisely targeting data in structured JSON objects
-            - Examples: '$.customer.firstName', '$.items[0].price', '$.addresses[*].street'
+            - Examples: '$.customer.firstName', '$.items[0].price', '$.addresses[*].street',
+              '$[*].Tax' (every row of a grouped record)
             - Wildcards like [*] extract multiple values/objects
 
             ```json
@@ -2088,7 +2090,8 @@ components:
             - Contains '{{' and '}}' pattern
             - Evaluated by the AFE 2.0 handlebars template engine
             - Can include logic, formatting, and computation
-            - Access input record fields with {{record.fieldName}} notation
+            - Access input record fields with {{record.fieldName}} notation; a grouped
+              (array) record binds as `rows` instead — {{rows.0.fieldName}} / {{#each rows}}
             - Examples: "{{record.firstName}} {{record.lastName}}", "{{#if record.isActive}}Active{{else}}Inactive{{/if}}"
             - Valid on `object`, `objectarray`, and primitive-array dataTypes as
               well as scalars — the rendered template output must parse into the
@@ -2099,7 +2102,7 @@ components:
             ```
 
             **3. Hard-Coded Value (literal string)**
-            - Does NOT start with '$.'
+            - Does NOT start with '$'
             - Does NOT contain handlebars '{{' syntax
             - System treats it as a literal string value
             - VERY COMMON for setting static/constant values
@@ -2121,10 +2124,38 @@ components:
             - The system maintains this context even in deeply nested mappings
             - For object mappings without child mappings, extract should return a complete object
             - When both extract and mappings are defined for objects, extract is applied first
+            - The root is the record as it arrives: an object record roots at `$.field`; a
+              grouped record (an array of rows — grouped exports, file key columns, NetSuite
+              grouped saved searches) roots at the array, so its rows are addressed as
+              `$[0].field` (one row) or `$[*].field` (every row). A root that contradicts the
+              record's shape resolves to nothing without an error.
 
             For most simple field-to-field mappings, prefer JSON path syntax for its clarity and performance.
             For hard-coded values, simply use the literal string as the extract value.
           x-celigo-ai-guidance:
+            - |-
+              ## GROUPED (ARRAY) RECORDS
+              Decide the JSONPath root from the record's shape before writing
+              any extract. When the record is an array of rows, `$.field`,
+              `$.properties.field` and `$.rows[*].field` all resolve to
+              nothing — the processor still reports success and the request
+              body ships as `{}`. Address rows as `$[0].field` (that row's
+              value, typed) or `$[*].field` (every row: joined with commas
+              into a `string` destination; rejected with
+              `incompatible_destination_conversion` into a `number`
+              destination). Column labels with spaces work as
+              `$[*][Order Number]`, `$[*].[Order Number]`, or
+              `$[*]['Order Number']`. For one destination element per row
+              the two array kinds take different helper forms: a primitive
+              array (`stringarray` / `numberarray`) uses `buildArrayHelper:
+              [{"extract": "$[*].field"}]`; an `objectarray` uses
+              `buildArrayHelper: [{"extract": "$[*]", "mappings": [...]}]`
+              with the children addressing the row relatively (`$.field`,
+              `{{rows.field}}`). An `extract` placed directly on the
+              array-typed field yields nothing. Handlebars
+              extracts bind the array record as `rows` (`{{rows.0.field}}`),
+              an object record as `record`. The reverse holds too: `$[*]` on
+              an object record iterates the object's values, not rows.
             - |-
               ## SIZE LIMIT
               The platform's import save validator caps this field at **1024
@@ -2382,7 +2413,11 @@ components:
               (`$.items[*]`), `"$"` (the record root), or omission — a
               constructed entry (child `mappings` with the extract omitted or
               `"$"`; the two spellings are equivalent) contributes exactly one
-              element, and entries append in order. Indexed or comma-joined
+              element, and entries append in order. On a grouped (array)
+              record the record itself is the array to iterate: `"$[*]"`
+              yields one `objectarray` element per row (children address the
+              row as `$.field`), and `"$[*].field"` yields one primitive-array
+              value per row. Indexed or comma-joined
               entry extracts (`"$[0]"`, `"$[0],$[0]"`) are not valid: the
               processor renders the entire destination array as null with no
               validation error. To emit a fixed number of static elements, add
@@ -2403,7 +2438,9 @@ components:
 
             **For Simple Arrays (stringarray, numberarray, booleanarray)**
             - Only the 'extract' field is used to pull values
-            - JSON path with wildcards (e.g., $.items[*].name) returns multiple values
+            - JSON path with wildcards (e.g., $.items[*].name) returns multiple values;
+              on a grouped (array) record the record itself is the array, so the
+              path roots at it ($[*].name — one value per row)
             - Each result is converted to the appropriate primitive type
             ```json
             {
@@ -2505,11 +2542,13 @@ components:
             - When both extract and mappings are provided, the system creates special composite objects
               that maintain hierarchical context during processing
             - This enables accessing both the current array element AND its parent context
-            - An ITERATING entry's extract MUST use JSON path syntax starting with '$.'
-              (e.g. '$.items[*]'). A CONSTRUCTED entry (child mappings building one element)
-              instead omits extract or sets it to exactly "$" — never rewrite "$" into a
-              '$.'-prefixed, indexed, or comma-joined form ('$[0]', '$[0],$[0]'): those render
-              the entire destination array as null without raising a validation error
+            - An ITERATING entry's extract MUST be a JSON path that iterates an array:
+              '$.items[*]' when the array is a field of an object record, or '$[*]'
+              (objectarray) / '$[*].field' (primitive arrays) when the record itself is a
+              grouped array of rows. A CONSTRUCTED entry (child mappings building one
+              element) instead omits extract or sets it to exactly "$" — never rewrite "$"
+              into an indexed or comma-joined form ('$[0]', '$[0],$[0]'): those render the
+              entire destination array as null without raising a validation error
             - Each array helper entry acts independently, potentially adding multiple elements
 
             The buildArrayHelper is the most complex part of the mappings system - always analyze the
@@ -2923,9 +2962,11 @@ components:
               This field supports THREE DISTINCT PATTERNS that are easily distinguished:
 
               **1. json Path Syntax**
-              - MUST start with '$.' prefix
+              - MUST start with '$' — the record root. An object record is addressed as
+                '$.field'; a grouped (array) record as '$[0].field' / '$[*].field'
               - Used for precisely targeting data in structured JSON objects
-              - Examples: '$.customer.firstName', '$.items[0].price', '$.addresses[*].street'
+              - Examples: '$.customer.firstName', '$.items[0].price', '$.addresses[*].street',
+                '$[*].Tax' (every row of a grouped record)
               - Wildcards like [*] extract multiple values/objects
 
               ```json
@@ -2936,7 +2977,8 @@ components:
               - Contains '{{' and '}}' pattern
               - Evaluated by the AFE 2.0 handlebars template engine
               - Can include logic, formatting, and computation
-              - Access input record fields with {{record.fieldName}} notation
+              - Access input record fields with {{record.fieldName}} notation; a grouped
+                (array) record binds as `rows` instead — {{rows.0.fieldName}} / {{#each rows}}
               - Examples: "{{record.firstName}} {{record.lastName}}", "{{#if record.isActive}}Active{{else}}Inactive{{/if}}"
               - Valid on `object`, `objectarray`, and primitive-array dataTypes as
                 well as scalars — the rendered template output must parse into the
@@ -2947,7 +2989,7 @@ components:
               ```
 
               **3. Hard-Coded Value (literal string)**
-              - Does NOT start with '$.'
+              - Does NOT start with '$'
               - Does NOT contain handlebars '{{' syntax
               - System treats it as a literal string value
               - VERY COMMON for setting static/constant values
@@ -2969,10 +3011,38 @@ components:
               - The system maintains this context even in deeply nested mappings
               - For object mappings without child mappings, extract should return a complete object
               - When both extract and mappings are defined for objects, extract is applied first
+              - The root is the record as it arrives: an object record roots at `$.field`; a
+                grouped record (an array of rows — grouped exports, file key columns, NetSuite
+                grouped saved searches) roots at the array, so its rows are addressed as
+                `$[0].field` (one row) or `$[*].field` (every row). A root that contradicts the
+                record's shape resolves to nothing without an error.
 
               For most simple field-to-field mappings, prefer JSON path syntax for its clarity and performance.
               For hard-coded values, simply use the literal string as the extract value.
             x-celigo-ai-guidance:
+              - |-
+                ## GROUPED (ARRAY) RECORDS
+                Decide the JSONPath root from the record's shape before writing
+                any extract. When the record is an array of rows, `$.field`,
+                `$.properties.field` and `$.rows[*].field` all resolve to
+                nothing — the processor still reports success and the request
+                body ships as `{}`. Address rows as `$[0].field` (that row's
+                value, typed) or `$[*].field` (every row: joined with commas
+                into a `string` destination; rejected with
+                `incompatible_destination_conversion` into a `number`
+                destination). Column labels with spaces work as
+                `$[*][Order Number]`, `$[*].[Order Number]`, or
+                `$[*]['Order Number']`. For one destination element per row
+                the two array kinds take different helper forms: a primitive
+                array (`stringarray` / `numberarray`) uses `buildArrayHelper:
+                [{"extract": "$[*].field"}]`; an `objectarray` uses
+                `buildArrayHelper: [{"extract": "$[*]", "mappings": [...]}]`
+                with the children addressing the row relatively (`$.field`,
+                `{{rows.field}}`). An `extract` placed directly on the
+                array-typed field yields nothing. Handlebars
+                extracts bind the array record as `rows` (`{{rows.0.field}}`),
+                an object record as `record`. The reverse holds too: `$[*]` on
+                an object record iterates the object's values, not rows.
               - |-
                 ## SIZE LIMIT
                 The platform's import save validator caps this field at **1024
@@ -3230,7 +3300,11 @@ components:
                 (`$.items[*]`), `"$"` (the record root), or omission — a
                 constructed entry (child `mappings` with the extract omitted or
                 `"$"`; the two spellings are equivalent) contributes exactly one
-                element, and entries append in order. Indexed or comma-joined
+                element, and entries append in order. On a grouped (array)
+                record the record itself is the array to iterate: `"$[*]"`
+                yields one `objectarray` element per row (children address the
+                row as `$.field`), and `"$[*].field"` yields one primitive-array
+                value per row. Indexed or comma-joined
                 entry extracts (`"$[0]"`, `"$[0],$[0]"`) are not valid: the
                 processor renders the entire destination array as null with no
                 validation error. To emit a fixed number of static elements, add
@@ -3251,7 +3325,9 @@ components:
 
               **For Simple Arrays (stringarray, numberarray, booleanarray)**
               - Only the 'extract' field is used to pull values
-              - JSON path with wildcards (e.g., $.items[*].name) returns multiple values
+              - JSON path with wildcards (e.g., $.items[*].name) returns multiple values;
+                on a grouped (array) record the record itself is the array, so the
+                path roots at it ($[*].name — one value per row)
               - Each result is converted to the appropriate primitive type
               ```json
               {
@@ -3353,11 +3429,13 @@ components:
               - When both extract and mappings are provided, the system creates special composite objects
                 that maintain hierarchical context during processing
               - This enables accessing both the current array element AND its parent context
-              - An ITERATING entry's extract MUST use JSON path syntax starting with '$.'
-                (e.g. '$.items[*]'). A CONSTRUCTED entry (child mappings building one element)
-                instead omits extract or sets it to exactly "$" — never rewrite "$" into a
-                '$.'-prefixed, indexed, or comma-joined form ('$[0]', '$[0],$[0]'): those render
-                the entire destination array as null without raising a validation error
+              - An ITERATING entry's extract MUST be a JSON path that iterates an array:
+                '$.items[*]' when the array is a field of an object record, or '$[*]'
+                (objectarray) / '$[*].field' (primitive arrays) when the record itself is a
+                grouped array of rows. A CONSTRUCTED entry (child mappings building one
+                element) instead omits extract or sets it to exactly "$" — never rewrite "$"
+                into an indexed or comma-joined form ('$[0]', '$[0],$[0]'): those render the
+                entire destination array as null without raising a validation error
               - Each array helper entry acts independently, potentially adding multiple elements
 
               The buildArrayHelper is the most complex part of the mappings system - always analyze the
@@ -4083,6 +4161,16 @@ components:
                   x-enumDescriptions:
                     create: Builds entirely new output records from inputs, ignoring unmapped fields.
                     modify: Makes targeted edits to existing records, preserving unmapped fields.
+                  x-celigo-ai-guidance:
+                    - |-
+                      On a grouped record (the export groups rows, so the record is an
+                      array) only `create` can author output — build it from the rows with
+                      `$[0].field`, `$[*].field`, or a `buildArrayHelper` over `$[*]`.
+                      `modify` has no object to overlay onto an array: the record passes
+                      through untouched and the processor reports success. Either mode
+                      reshapes the inside of one record; neither changes how many records
+                      the page carries (that is the export's `preSavePage` hook) or whether
+                      the export groups at all (that is its grouping setting).
                   examples:
                     - create
                     - modify
@@ -9948,7 +10036,11 @@ components:
                     suiteAppInstalled:
                       type: boolean
                       readOnly: true
-                      description: When true, the Celigo SuiteApp bundle is installed in the connected NetSuite account. Detected by the server when the connection authenticates to NetSuite.
+                      description: |-
+                        When true, the Celigo integrator.io SuiteApp (SuiteScript 2.x) was detected in
+                        the connected NetSuite account the last time the connection authenticated. It
+                        says nothing about the legacy Celigo bundle; for a live check of both, use
+                        `GET /v1/connections/{_id}/distributedApps`.
             salesforce:
               description: Present when `type` is `salesforce`.
               allOf:
@@ -10687,7 +10779,9 @@ components:
       type: object
       description: |-
         Configuration for HTTP imports.
-        Required whenever the connection referenced by _connectionId has type http.
+        Required whenever the connection referenced by _connectionId has type http, and on
+        `NetSuiteHTTPImport` (NetSuite's REST APIs on a `netsuite` connection, where `nsDomainType`
+        supplies the host).
       x-celigo-ai-guidance:
         - |-
           IMPORTANT:
@@ -10695,6 +10789,11 @@ components:
           this object MUST be populated for the import to function properly.
           This is a required configuration for all HTTP based imports,
           as determined by the connection associated with the import.
+        - |-
+          A `NetSuiteHTTPImport` uses this same object on a netsuite connection: each `relativeURI`
+          entry carries the full path from `/services/rest/record/v1/<type>` (SuiteTalk) or
+          `/app/site/hosting/restlet.nl?script=<id>&deploy=<n>` (custom RESTlet); the host and the
+          token signature come from the connection.
       properties:
         sendPostMappedData:
           type: boolean
@@ -20776,6 +20875,7 @@ components:
           description: |-
             Connection this import uses to reach the destination system. The connection's type must
             be compatible with the import's `adaptorType` (e.g. an `HTTPImport` needs an `http`
+            connection; `NetSuiteDistributedImport` and `NetSuiteHTTPImport` both need a `netsuite`
             connection). Server-required — POST without it fails with 422 "Expected field:
             _connectionId to be present" — except for the connection-less flavors (`ToolImport`,
             `AiAgentImport`, `GuardrailImport`), which the server creates without one.
@@ -20808,9 +20908,15 @@ components:
               Use HTTPImport for all REST/SOAP APIs unless a specialized adaptor exists for the
               target system; always pair the adaptorType with its matching configuration object.
             - |-
-              For NetSuite, always use NetSuiteDistributedImport (with the netsuite_da object).
-              NetSuiteImport is a legacy adaptor for accounts without the Celigo SuiteApp 2.0 — do
-              not use it unless explicitly requested.
+              For NetSuite, use NetSuiteDistributedImport (with the netsuite_da object) when the
+              Celigo SuiteApp or bundle is installed in the account — check with
+              `GET /v1/connections/{_id}/distributedApps` (`suiteapp.success` / `bundle.success`).
+              Use NetSuiteHTTPImport (with `nsDomainType` and the http object) when neither is
+              installed or the user asks for NetSuite's REST APIs; the platform's SuiteTalk connector
+              catalogs `POST /services/rest/record/v1/<type>` for inserts and
+              `PATCH /services/rest/record/v1/<type>/{id}` for updates, and saving links the step to
+              them. NetSuiteImport is a legacy adaptor for accounts without the Celigo SuiteApp 2.0 —
+              do not use it unless explicitly requested.
             - |-
               Use RDBMSImport (with the rdbms object) for built-in database types such as SQL Server,
               MySQL, PostgreSQL, Snowflake, Oracle, and MariaDB. Use JDBCImport (with the jdbc
@@ -20822,6 +20928,7 @@ components:
             - S3Import
             - NetSuiteImport
             - NetSuiteDistributedImport
+            - NetSuiteHTTPImport
             - SalesforceImport
             - JDBCImport
             - RDBMSImport
@@ -20839,7 +20946,8 @@ components:
             AS2Import: File import via AS2 (Applicability Statement 2) protocol.
             S3Import: File import to Amazon S3 storage.
             NetSuiteImport: Legacy NetSuite import for accounts without the Celigo SuiteApp 2.0.
-            NetSuiteDistributedImport: NetSuite import using the distributed SuiteApp 2.0 adaptor (default for NetSuite).
+            NetSuiteDistributedImport: NetSuite import using the distributed SuiteApp 2.0 adaptor (default for NetSuite when the SuiteApp or bundle is installed).
+            NetSuiteHTTPImport: NetSuite import over its REST APIs — SuiteTalk REST record endpoints or a custom RESTlet — on a netsuite connection, without the Celigo SuiteApp or bundle.
             SalesforceImport: Salesforce-specific import using SOAP, REST, Metadata, or Composite APIs.
             JDBCImport: Database import via a generic JDBC connection (not for built-in RDBMS types).
             RDBMSImport: Database import for built-in RDBMS types such as SQL Server, MySQL, PostgreSQL, Snowflake, and Oracle.
@@ -20854,10 +20962,38 @@ components:
           examples:
             - HTTPImport
             - NetSuiteDistributedImport
+            - NetSuiteHTTPImport
             - SalesforceImport
             - FTPImport
             - AiAgentImport
             - GuardrailImport
+        nsDomainType:
+          type: string
+          enum:
+            - suitetalk
+            - restlet
+          x-lowercase: true
+          x-enumDescriptions:
+            suitetalk: NetSuite SuiteTalk REST web services — record endpoints under /services/rest/record/v1
+            restlet: A custom RESTlet script deployed in the NetSuite account, called at /app/site/hosting/restlet.nl?script=<id>&deploy=<n>
+          description: |-
+            Selects which NetSuite REST host a `NetSuiteHTTPImport` calls. The server derives the
+            full base URL from the connection's NetSuite account
+            (`https://<account>.suitetalk.api.netsuite.com` or `https://<account>.restlets.api.netsuite.com`)
+            and signs each request with the connection's token-based credentials, so each
+            `http.relativeURI` entry carries the complete path starting at `/services/rest/...` or
+            `/app/site/hosting/restlet.nl`. Ignored on other adaptor types.
+          x-celigo-ai-guidance:
+            - |-
+              Required on `NetSuiteHTTPImport`: omitting it fails the save with 422 "Path `nsDomainType`
+              is required." The import's `_connectionId` must be a netsuite connection — an http
+              connection fails with 422 invalid_connection_type.
+            - |-
+              With `suitetalk`, saving links `http._httpConnectorVersionId`, `_httpConnectorResourceId`
+              and `_httpConnectorEndpointIds` to the platform's SuiteTalk connector from each
+              `http.method` + `http.relativeURI` pair (for example `POST /services/rest/record/v1/customer`
+              links to that record type's insert endpoint), so the UI's Simple view renders an
+              API-authored step; `restlet` steps are not linked.
         externalId:
           type:
             - string
@@ -21724,10 +21860,15 @@ components:
           iterate ``{{#each rows}}``); hook code sees the array as the
           record element and must not assume object shape.
         - |-
-          Transform 2.0 cannot reshape a grouped record at the array root —
-          ``mode: "modify"`` passes the array through untouched and
-          ``mode: "create"`` yields an empty object. Reshape grouped data in
-          a preSavePage hook (or downstream postResponseMap) instead.
+          A grouped record is ONE record: Mapper 2.0 and Transform 2.0 root
+          JSONPath at the array (``$[0].<field>`` / ``$[*].<field>``;
+          ``$.<field>`` resolves nothing), and a Transform 2.0 in ``mode:
+          "create"`` reshapes it in place — header fields from ``$[0]``, a
+          lines array from a ``buildArrayHelper`` over ``$[*]`` (``mode:
+          "modify"`` has no object to overlay and passes the array through
+          untouched). Changing how many records the page carries — each
+          row becoming its own record for every downstream step — is the
+          ``preSavePage`` hook's job alone.
       items:
         type: string
       examples:
@@ -26309,7 +26450,10 @@ components:
             - \\NAS\Accounting\AP
     Http-2:
       type: object
-      description: Configuration for HTTP exports. Required when the export's `_connectionId` references a connection of type `http`.
+      description: |-
+        Configuration for HTTP exports. Required when the export's `_connectionId` references a
+        connection of type `http`, and on `NetSuiteHTTPExport` (NetSuite's REST APIs on a `netsuite`
+        connection, where `nsDomainType` supplies the host).
       x-celigo-ai-guidance:
         - |-
           IMPORTANT:
@@ -26317,6 +26461,12 @@ components:
           this object MUST be populated for the export to function properly.
           This is a required configuration for all HTTP based exports,
           as determined by the connection associated with the export.
+        - |-
+          A `NetSuiteHTTPExport` uses this same object on a netsuite connection: `relativeURI`
+          carries the full path from `/services/rest/...` (SuiteTalk) or
+          `/app/site/hosting/restlet.nl?script=<id>&deploy=<n>` (custom RESTlet), the host and the
+          token signature come from the connection, and `type` must stay unset (file, blob and
+          csvstream are rejected with 422 unsupported_type).
       properties:
         type:
           type: string
@@ -26466,7 +26616,7 @@ components:
           x-celigo-agent:
             - handlebars
           x-celigo-handlebars-context: pre-mapped
-          description: 'Resource path appended to the connection''s `baseURI` to form the complete request URL. Path segments, query parameters, or the entire value can be built with handlebars expressions for endpoints determined at runtime. For lookup exports (`isLookup: true`) with mappings configured, handlebars always render against the original pre-mapped input record, so fields removed or renamed by mappings remain available for URI construction.'
+          description: 'Resource path appended to the connection''s `baseURI` to form the complete request URL. Path segments, query parameters, or the entire value can be built with handlebars expressions for endpoints determined at runtime. For lookup exports (`isLookup: true`) with mappings configured, handlebars always render against the original pre-mapped input record, so fields removed or renamed by mappings remain available for URI construction. On `NetSuiteHTTPExport` the base URL is derived from the NetSuite connection and `nsDomainType`, so the path starts at `/services/rest/...` or `/app/site/hosting/restlet.nl`.'
           x-celigo-ai-guidance:
             - The resource path portion of the API endpoint used for this export.
             - |-
@@ -33216,7 +33366,8 @@ components:
             - 'null'
           description: |-
             Connection this export uses to reach the source system. The connection's type must be
-            compatible with the export's `adaptorType` (e.g. an `HTTPExport` needs an `http` connection).
+            compatible with the export's `adaptorType` (e.g. an `HTTPExport` needs an `http` connection;
+            `NetSuiteExport` and `NetSuiteHTTPExport` both need a `netsuite` connection).
             Server-required unless `type` is `webhook` or `simple` (those receive data instead of fetching it).
           examples:
             - 60a2c4e6f321d800129a1a3c
@@ -33232,6 +33383,7 @@ components:
             - AS2Export
             - S3Export
             - NetSuiteExport
+            - NetSuiteHTTPExport
             - SalesforceExport
             - JDBCExport
             - RDBMSExport
@@ -33247,7 +33399,8 @@ components:
             FTPExport: Exports files from FTP or SFTP servers.
             AS2Export: Exports data using the AS2 (Applicability Statement 2) secure file transfer protocol.
             S3Export: Exports files from Amazon S3 cloud storage buckets.
-            NetSuiteExport: Exports data from Oracle NetSuite using saved searches, RESTlets, or SuiteApp.
+            NetSuiteExport: Exports data from Oracle NetSuite through the Celigo SuiteApp/bundle RESTlets (saved searches or search criteria), SOAP web services, real-time listeners, or the file cabinet.
+            NetSuiteHTTPExport: Exports records from Oracle NetSuite over its REST APIs — SuiteTalk REST record endpoints and SuiteQL, or a custom RESTlet — on a netsuite connection, with no saved search and no Celigo SuiteApp involved.
             SalesforceExport: Exports data from Salesforce using SOQL queries or real-time events.
             JDBCExport: Exports data from databases using JDBC connections.
             RDBMSExport: Exports data from relational databases using SQL queries.
@@ -33261,7 +33414,71 @@ components:
           examples:
             - HTTPExport
             - NetSuiteExport
+            - NetSuiteHTTPExport
             - SalesforceExport
+          x-celigo-ai-guidance:
+            - |-
+              On a netsuite connection, default to `NetSuiteHTTPExport` (with `nsDomainType` and an
+              `http` object) for exports and lookups: it reads records over NetSuite's REST APIs with
+              nothing to create in NetSuite first — SuiteQL for filtered or multi-table extracts, the
+              record endpoint `GET /services/rest/record/v1/<type>/{id}` for one record. Choose
+              `NetSuiteExport` when the user names an existing saved search or asks for one, for
+              real-time listeners (`type: distributed`), and for file-cabinet exports; never convert an
+              existing `NetSuiteExport` to `NetSuiteHTTPExport` unless asked.
+            - |-
+              When authoring a NetSuite REST export, send `adaptorType: "NetSuiteHTTPExport"` explicitly:
+              on a netsuite connection the server otherwise infers `NetSuiteExport` and rejects the
+              document with 422 "netsuite subschema not defined", even though `nsDomainType` and `http`
+              are present.
+        nsDomainType:
+          type: string
+          enum:
+            - suitetalk
+            - restlet
+          x-lowercase: true
+          x-enumDescriptions:
+            suitetalk: NetSuite SuiteTalk REST web services — record endpoints under /services/rest/record/v1 and SuiteQL under /services/rest/query/v1
+            restlet: A custom RESTlet script deployed in the NetSuite account, called at /app/site/hosting/restlet.nl?script=<id>&deploy=<n>
+          description: |-
+            Selects which NetSuite REST host a `NetSuiteHTTPExport` calls. The server derives the
+            full base URL from the connection's NetSuite account
+            (`https://<account>.suitetalk.api.netsuite.com` or `https://<account>.restlets.api.netsuite.com`)
+            and signs each request with the connection's token-based credentials, so `http.relativeURI`
+            carries the complete path starting at `/services/rest/...` or `/app/site/hosting/restlet.nl`.
+            Ignored on other adaptor types.
+          x-celigo-ai-guidance:
+            - |-
+              Required on `NetSuiteHTTPExport`: omitting it fails the save with 422 "Path `nsDomainType`
+              is required." and any other value fails with 422 "is not a valid enum value for path
+              `nsDomainType`". The export's `_connectionId` must be a netsuite connection — an http
+              connection fails with 422 invalid_connection_type.
+            - |-
+              With `suitetalk`, saving links `http._httpConnectorVersionId`, `_httpConnectorResourceId`
+              and `_httpConnectorEndpointId` to the platform's SuiteTalk connector from `http.method` +
+              `http.relativeURI`, so the UI's Simple view renders an API-authored step; `restlet` steps
+              are not linked.
+            - |-
+              The record list endpoint (`GET /services/rest/record/v1/<type>?limit=<n>&offset={{{export.http.paging.skip}}}`)
+              returns only `{id, links}` per item, so it yields no business fields on its own. For
+              records with fields use SuiteQL: `POST /services/rest/query/v1/suiteql?limit=<n>&offset={{{export.http.paging.skip}}}`,
+              header `Prefer: transient`, `http.body` `{"q": "<SuiteQL>"}`, `http.paging.method: skip`,
+              `http.response.resourcePath: items`; the response envelope carries `hasMore` and
+              `totalResults`. SuiteQL column names are the Records Catalog names (lowercase, e.g.
+              `entityid`, `lastmodifieddate`), not the REST record field names.
+            - |-
+              For incremental runs set `type: delta`, embed `{{lastExportDateTime}}` in the SuiteQL
+              `WHERE` clause (or the record endpoint's `q` parameter) and set `delta.dateFormat` to the
+              format the query compares against, e.g. `to_char(lastmodifieddate,'YYYY-MM-DD HH24:MI:SS') >= '{{lastExportDateTime}}'`
+              with `delta.dateFormat: "YYYY-MM-DD HH:mm:ss"`. In a preview the placeholder renders
+              empty, so preview results do not reflect the delta window.
+            - |-
+              NetSuite must have the REST Web Services feature enabled (Setup > Company > Enable
+              Features > SuiteCloud); otherwise every SuiteTalk call fails with NetSuite 403
+              FEATURE_DISABLED "The 'REST Web Services' feature is not enabled". Custom RESTlets do
+              not need it.
+            - |-
+              `http.type` file, blob, and csvstream are each rejected with 422 unsupported_type
+              ("NetSuiteHTTPExport does not support type: <value>") — REST steps are record-based only.
         type:
           type:
             - string
@@ -33533,8 +33750,8 @@ components:
           description: |-
             Field mappings applied to each incoming record before a lookup HTTP request is made,
             reshaping the upstream record into the structure the lookup target API expects. Only
-            supported when `isLookup` is true and `adaptorType` is `HTTPExport`; do not set it on
-            source exports or non-HTTP lookups.
+            supported when `isLookup` is true and `adaptorType` is `HTTPExport` or
+            `NetSuiteHTTPExport`; do not set it on source exports or other lookup adaptors.
           allOf:
             - $ref: '#/components/schemas/Mappings'
           x-celigo-ai-guidance:
@@ -33547,8 +33764,9 @@ components:
               1. ``isLookup`` is ``true`` (the export is being used as a
                  lookup step, not a source export), AND
               2. ``adaptorType`` is ``"HTTPExport"`` (generic REST/SOAP
-                 HTTP lookup — not NetSuite, Salesforce, RDBMS, file-based,
-                 or any other adaptor).
+                 HTTP lookup) or ``"NetSuiteHTTPExport"`` (NetSuite REST
+                 APIs) — not the saved-search NetSuite adaptor, Salesforce,
+                 RDBMS, file-based, or any other adaptor.
 
               For any other combination (source exports, non-HTTP lookup
               exports), do **not** emit this field.  Explain the constraint

package/package.json

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