@celigo/api-specs 0.2.128 → 0.2.129

package/dist/ai-agent.yml

@@ -3141,7 +3141,7 @@ components:
               no message text) and never cascades or promotes on its own; `Draft`
               descendants are kept as they are, and a `Draft` parent does not gate
               its children. The UI's Set inactive on a parent marks the parent and
-              every child `Inactive` (IO-166197). Re-enabling a child
+              every child `Inactive`. Re-enabling a child
               means re-enabling its ancestors in the same payload. Edits that keep
               existing rows must carry their stored status forward — rewriting a
               `Draft` or `Inactive` row to `Active` turns a row the user parked
@@ -4180,7 +4180,7 @@ components:
                 no message text) and never cascades or promotes on its own; `Draft`
                 descendants are kept as they are, and a `Draft` parent does not gate
                 its children. The UI's Set inactive on a parent marks the parent and
-                every child `Inactive` (IO-166197). Re-enabling a child
+                every child `Inactive`. Re-enabling a child
                 means re-enabling its ancestors in the same payload. Edits that keep
                 existing rows must carry their stored status forward — rewriting a
                 `Draft` or `Inactive` row to `Active` turns a row the user parked
@@ -5485,7 +5485,7 @@ components:
                         ``{record: {...}, settings: ..., job: ...}`` (plus
                         ``fileMeta`` on file-provider steps) — the
                         same runtime-context envelope Handlebars / SQL /
-                        GraphQL specialists consume.  ``mappings[].extract``
+                        GraphQL templates render against.  ``mappings[].extract``
                         JSONPath values MUST include the ``record.`` segment
                         — for example ``"$.record.orderId"`` or
                         ``"$.record.customer.email"``.  PLACEHOLDER extracts
@@ -5513,9 +5513,8 @@ components:
                       ``inputContext: record`` makes the contract
                       self-documenting and prevents the transform from
                       drifting into envelope mode if an upstream change ever
-                      changes the platform default.  The TransformsAgent
-                      reads this value off the transform config and threads
-                      it into the generator's prompt so the JSONPath form
+                      changes the platform default.  Read this value before
+                      writing ``mappings[].extract`` so the JSONPath form
                       matches the runtime root.
                     - |-
                       ## fileMeta on file-provider steps
@@ -6040,9 +6039,9 @@ components:
               format: date-time
               readOnly: true
               description: |-
-                When the draft version of this AI agent expires. Drafts are staged by Celigo
-                Ora (the platform's AI assistant) when it proposes changes for review; this
-                field is present only while an unapproved Ora draft is pending.
+                When the draft version of this AI agent expires. Drafts are staged by Celigo's
+                AI assistant when it proposes changes for review; this field is present only
+                while an unapproved draft is pending.
             debugUntil:
               type: string
               format: date-time

package/dist/alert.yml

@@ -651,7 +651,7 @@ paths:
                           type: string
                           description: User display name.
                           examples:
-                            - Tyler Lamparter
+                            - Jane Doe
                     fieldChanges:
                       type: array
                       description: Fields that were modified.
@@ -686,7 +686,7 @@ paths:
                       byUser:
                         _id: 624cb0346309dc3a543733a2
                         email: user@example.com
-                        name: Tyler Lamparter
+                        name: Jane Doe
                       fieldChanges:
                         - fieldPath: longRuntime.thresholdMinutes
                           oldValue: 30

package/dist/asynchelper.yml

@@ -1352,7 +1352,7 @@ components:
               no message text) and never cascades or promotes on its own; `Draft`
               descendants are kept as they are, and a `Draft` parent does not gate
               its children. The UI's Set inactive on a parent marks the parent and
-              every child `Inactive` (IO-166197). Re-enabling a child
+              every child `Inactive`. Re-enabling a child
               means re-enabling its ancestors in the same payload. Edits that keep
               existing rows must carry their stored status forward — rewriting a
               `Draft` or `Inactive` row to `Active` turns a row the user parked
@@ -2391,7 +2391,7 @@ components:
                 no message text) and never cascades or promotes on its own; `Draft`
                 descendants are kept as they are, and a `Draft` parent does not gate
                 its children. The UI's Set inactive on a parent marks the parent and
-                every child `Inactive` (IO-166197). Re-enabling a child
+                every child `Inactive`. Re-enabling a child
                 means re-enabling its ancestors in the same payload. Edits that keep
                 existing rows must carry their stored status forward — rewriting a
                 `Draft` or `Inactive` row to `Active` turns a row the user parked
@@ -3099,7 +3099,7 @@ components:
                         ``{record: {...}, settings: ..., job: ...}`` (plus
                         ``fileMeta`` on file-provider steps) — the
                         same runtime-context envelope Handlebars / SQL /
-                        GraphQL specialists consume.  ``mappings[].extract``
+                        GraphQL templates render against.  ``mappings[].extract``
                         JSONPath values MUST include the ``record.`` segment
                         — for example ``"$.record.orderId"`` or
                         ``"$.record.customer.email"``.  PLACEHOLDER extracts
@@ -3127,9 +3127,8 @@ components:
                       ``inputContext: record`` makes the contract
                       self-documenting and prevents the transform from
                       drifting into envelope mode if an upstream change ever
-                      changes the platform default.  The TransformsAgent
-                      reads this value off the transform config and threads
-                      it into the generator's prompt so the JSONPath form
+                      changes the platform default.  Read this value before
+                      writing ``mappings[].extract`` so the JSONPath form
                       matches the runtime root.
                     - |-
                       ## fileMeta on file-provider steps

package/dist/audit.yml

@@ -199,7 +199,7 @@ paths:
               sso: Change triggered by an SSO authentication event.
               cli: Change made via the Celigo CLI.
               mcp: Change made through the Celigo Platform MCP server.
-              ora: Change made by the Ora AI assistant.
+              ora: Change made by Celigo's AI assistant.
           description: |-
             Filter by source. Unsupported values are rejected with 422
             `invalid_audit_field`.
@@ -671,7 +671,7 @@ paths:
               sso: Change triggered by an SSO authentication event.
               cli: Change made via the Celigo CLI.
               mcp: Change made through the Celigo Platform MCP server.
-              ora: Change made by the Ora AI assistant.
+              ora: Change made by Celigo's AI assistant.
           description: Source filter.
       responses:
         '200':
@@ -951,7 +951,7 @@ paths:
               sso: Change triggered by an SSO authentication event.
               cli: Change made via the Celigo CLI.
               mcp: Change made through the Celigo Platform MCP server.
-              ora: Change made by the Ora AI assistant.
+              ora: Change made by Celigo's AI assistant.
           description: Filter by source.
         - name: _byUserId
           in: query
@@ -1550,7 +1550,7 @@ components:
             sso: Change triggered by an SSO authentication event.
             cli: Change made via the Celigo CLI.
             mcp: Change made through the Celigo Platform MCP server.
-            ora: Change made by the Ora AI assistant.
+            ora: Change made by Celigo's AI assistant.
         support:
           type: boolean
           readOnly: true
@@ -1754,7 +1754,7 @@ components:
               sso: Change triggered by an SSO authentication event.
               cli: Change made via the Celigo CLI.
               mcp: Change made through the Celigo Platform MCP server.
-              ora: Change made by the Ora AI assistant.
+              ora: Change made by Celigo's AI assistant.
           examples:
             - - api
               - system
@@ -1969,7 +1969,7 @@ components:
             sso: Change triggered by an SSO authentication event.
             cli: Change made via the Celigo CLI.
             mcp: Change made through the Celigo Platform MCP server.
-            ora: Change made by the Ora AI assistant.
+            ora: Change made by Celigo's AI assistant.
           description: Source filter.
         _byUserId:
           type: string

package/dist/editransaction.yml

@@ -958,7 +958,7 @@ components:
             Present only when the flow resolved the partner; drives the partner
             filter of the B2B Manager dashboard.
           examples:
-            - Best Buy
+            - Globex Retail
         partnerPairKey:
           type: string
           description: |-
@@ -968,7 +968,7 @@ components:
             `referenceDocumentNumber`. Present only when the flow resolved the
             partner.
           examples:
-            - ACME:BESTBUY
+            - ACME:GLOBEX
         direction:
           type: string
           enum:

package/dist/eventreport.yml

@@ -509,13 +509,13 @@ components:
                   type: string
                   description: Display name of the requesting user.
                   examples:
-                    - Tyler Lamparter
+                    - Jane Doe
                 email:
                   type: string
                   format: email
                   description: Email address of the requesting user.
                   examples:
-                    - tyler.lamparter@celigo.com
+                    - jane@example.com
     EventReportCreateRequest:
       type: object
       description: |

package/dist/export.yml

@@ -475,7 +475,7 @@ paths:
         Body is a complete export document (the shape you would POST to
         `/v1/exports`), typically without `_id`. The CLI uses it for two
         scenarios:
-        - `ora exports invoke` with a doc on stdin → ad-hoc preview of a
+        - `celigo exports invoke` with a doc on stdin → ad-hoc preview of a
           not-yet-saved export.
         - Agent-driven "preview + refine" loops where an LLM iterates on the
           export config and calls this endpoint to sample output each time.
@@ -1097,9 +1097,9 @@ components:
               Substitute ``<modifiedTimestampField>`` with the actual
               timestamp field the target entity exposes in its response.  Do
               NOT invent or copy field names from an example authored for a
-              different endpoint -- an unknown field name causes a runtime
-              "unknown property" / "invalid column" error the build cannot
-              catch.  See the engine's filter-field grounding principle.
+              different endpoint -- an unknown field name causes an
+              "unknown property" / "invalid column" error that surfaces only
+              at run time.
 
               For Salesforce, this field is required and has the following default values:
               - LastModifiedDate
@@ -10896,7 +10896,7 @@ components:
                         `[application · stage=apiCall] search.createColumn:
                         Missing a required argument: name`.  The platform
                         validation runs before any column data is read, so
-                        the build fails fast.
+                        the export fails fast.
                       - |-
                         ## NAME MUST BE A SEARCH COLUMN, NOT A BODY FIELD
                         NetSuite distinguishes between body fields (the
@@ -10904,9 +10904,8 @@ components:
                         search columns (the fields exposed for filtering /
                         sorting in saved searches, like `shipaddress1`).
                         `columns[].name` MUST be a search column ID, not
-                        a body field ID.  See the SEARCH COLUMNS section of
-                        the metadata fetcher output for the valid search
-                        column names for the chosen `recordType`.
+                        a body field ID: take it from the chosen
+                        `recordType`'s SEARCH COLUMNS list.
                       - |-
                         ## EXAMPLES
                         - `"internalid"` -- the record's internal id
@@ -11648,7 +11647,7 @@ components:
                   If the folder internal ID is required to be dynamic based on the data you are integrating,
                   you can specify the JSON path to the field in your data containing the folder
                   internal ID values instead — with DOUBLE braces (e.g. {{record.folderId}}).
-                  Production usage is dominantly a static numeric ID; dynamic substitution is rare.
+                  Default to a static numeric ID; dynamic substitution is the exception.
                 - |-
                   ## FIELD BEHAVIOR:
                   - Identifies the specific folder in NetSuite's file cabinet to export files from
@@ -11673,7 +11672,7 @@ components:
                   - May be linked to folder creation or folder search operations to retrieve valid IDs.
                 - |-
                   ## EXAMPLES:
-                  - "12345" - Static folder internal ID (the dominant production form)
+                  - "12345" - Static folder internal ID (the usual form)
                   - "67890" - Another valid folder internal ID
                   - "{{record.folderId}}" - Dynamic folder ID from integration data (double braces)
                 - |-
@@ -13196,7 +13195,7 @@ components:
               no message text) and never cascades or promotes on its own; `Draft`
               descendants are kept as they are, and a `Draft` parent does not gate
               its children. The UI's Set inactive on a parent marks the parent and
-              every child `Inactive` (IO-166197). Re-enabling a child
+              every child `Inactive`. Re-enabling a child
               means re-enabling its ancestors in the same payload. Edits that keep
               existing rows must carry their stored status forward — rewriting a
               `Draft` or `Inactive` row to `Active` turns a row the user parked
@@ -14235,7 +14234,7 @@ components:
                 no message text) and never cascades or promotes on its own; `Draft`
                 descendants are kept as they are, and a `Draft` parent does not gate
                 its children. The UI's Set inactive on a parent marks the parent and
-                every child `Inactive` (IO-166197). Re-enabling a child
+                every child `Inactive`. Re-enabling a child
                 means re-enabling its ancestors in the same payload. Edits that keep
                 existing rows must carry their stored status forward — rewriting a
                 `Draft` or `Inactive` row to `Active` turns a row the user parked
@@ -14943,7 +14942,7 @@ components:
                         ``{record: {...}, settings: ..., job: ...}`` (plus
                         ``fileMeta`` on file-provider steps) — the
                         same runtime-context envelope Handlebars / SQL /
-                        GraphQL specialists consume.  ``mappings[].extract``
+                        GraphQL templates render against.  ``mappings[].extract``
                         JSONPath values MUST include the ``record.`` segment
                         — for example ``"$.record.orderId"`` or
                         ``"$.record.customer.email"``.  PLACEHOLDER extracts
@@ -14971,9 +14970,8 @@ components:
                       ``inputContext: record`` makes the contract
                       self-documenting and prevents the transform from
                       drifting into envelope mode if an upstream change ever
-                      changes the platform default.  The TransformsAgent
-                      reads this value off the transform config and threads
-                      it into the generator's prompt so the JSONPath form
+                      changes the platform default.  Read this value before
+                      writing ``mappings[].extract`` so the JSONPath form
                       matches the runtime root.
                     - |-
                       ## fileMeta on file-provider steps

package/dist/filedefinitionrules.yml

@@ -26,7 +26,7 @@ tags:
       Job records expire 24 hours after submission. Submissions are
       rate-limited per caller (10 per hour, with an administrator bypass);
       the document-types catalog allows 100 per hour and 10 per 60 seconds.
-      The API only produces rules — it persists nothing. The Ora agent in
+      The API only produces rules — it persists nothing. Celigo's AI assistant in
       integrator.io drives these endpoints for interactive onboarding; call
       them directly to script partner onboarding in bulk.
 

package/dist/flow.yml

@@ -1592,7 +1592,7 @@ paths:
             Only return errors closed by the listed resolvers. Repeat the parameter once per value;
             each value is a Mongo user id (matching the `resolvedBy` field on user-resolved errors).
             The literal value `auto` matches platform-auto-resolved errors and can be mixed with
-            user ids (`?resolvedBy=681a1c92c99fc39fabe2d7b9&resolvedBy=auto`). Unknown values are
+            user ids (`?resolvedBy=<userId>&resolvedBy=auto`). Unknown values are
             not rejected — they simply match nothing.
           schema:
             type: array
@@ -6632,11 +6632,11 @@ components:
           type: string
           description: |-
             Display name of the user currently assigned to this error for triage when the email resolves
-            to a known account user (e.g. `"Tyler Lamparter"`). When the email does not match a known
+            to a known account user (e.g. `"Jane Doe"`). When the email does not match a known
             user, the literal email string is stored instead. Set via
             `PUT /v1/flows/{_id}/{_stepId}/errors/assign`. Absent when no assignment has been made.
           examples:
-            - Tyler Lamparter
+            - Jane Doe
         assignedBy:
           type: string
           description: Mongo user id of the user who made the assignment. Absent when no assignment has been made.