@celigo/api-specs 0.2.171 → 0.2.173

package/dist/ai-agent.yml

@@ -2324,7 +2324,11 @@ components:
 
             **Simple Types (direct value mapping)**
             - `string`: Text values, converts other types to string representation
-            - `number`: Numeric values, attempts conversion from strings
+            - `number`: Numeric values. Converts a numeric string (`"24"` → `24`,
+              `"007"` → `7`) and leaves the field out for an empty string; a value
+              holding letters or a thousands separator (`"1,250.00"`) fails the
+              record with `non_parsable_string` (`<generate>: String contains alpha
+              characters`)
             - `boolean`: True/false values, converts truthy/falsy values
 
             Dates are represented as strings — use `string` for date fields and
@@ -2367,8 +2371,14 @@ components:
             - |-
               Missing `dataType` is rejected at save with validation error
               `[mandatory_destination_datatype] Destination datatype is a
-              required field.` When in doubt, use `"string"` — it accepts
-              any source value and the runtime will coerce it.
+              required field.`
+            - |-
+              Give each row the type the destination field expects; `"string"` is
+              not a safe default. It accepts any source value, but sends a numeric
+              source as text (`"24"`), which a destination that checks JSON types
+              refuses. Map numeric destination fields as `number`, which fails a
+              record (`non_parsable_string`) only when the value holds letters or a
+              thousands separator.
           enum:
             - string
             - number
@@ -2380,7 +2390,7 @@ components:
             - objectarray
           x-enumDescriptions:
             string: Text values; converts other types to their string representation.
-            number: Numeric values; attempts conversion from strings.
+            number: Numeric values; converts numeric strings, and fails the record (`non_parsable_string`) on letters or a thousands separator.
             boolean: True/false values; converts truthy/falsy values.
             object: Nested object built from child `mappings`, or copied whole with `extract` (not both).
             stringarray: Array of string values.
@@ -3408,7 +3418,11 @@ components:
 
               **Simple Types (direct value mapping)**
               - `string`: Text values, converts other types to string representation
-              - `number`: Numeric values, attempts conversion from strings
+              - `number`: Numeric values. Converts a numeric string (`"24"` → `24`,
+                `"007"` → `7`) and leaves the field out for an empty string; a value
+                holding letters or a thousands separator (`"1,250.00"`) fails the
+                record with `non_parsable_string` (`<generate>: String contains alpha
+                characters`)
               - `boolean`: True/false values, converts truthy/falsy values
 
               Dates are represented as strings — use `string` for date fields and
@@ -3451,8 +3465,14 @@ components:
               - |-
                 Missing `dataType` is rejected at save with validation error
                 `[mandatory_destination_datatype] Destination datatype is a
-                required field.` When in doubt, use `"string"` — it accepts
-                any source value and the runtime will coerce it.
+                required field.`
+              - |-
+                Give each row the type the destination field expects; `"string"` is
+                not a safe default. It accepts any source value, but sends a numeric
+                source as text (`"24"`), which a destination that checks JSON types
+                refuses. Map numeric destination fields as `number`, which fails a
+                record (`non_parsable_string`) only when the value holds letters or a
+                thousands separator.
             enum:
               - string
               - number
@@ -3464,7 +3484,7 @@ components:
               - objectarray
             x-enumDescriptions:
               string: Text values; converts other types to their string representation.
-              number: Numeric values; attempts conversion from strings.
+              number: Numeric values; converts numeric strings, and fails the record (`non_parsable_string`) on letters or a thousands separator.
               boolean: True/false values; converts truthy/falsy values.
               object: Nested object built from child `mappings`, or copied whole with `extract` (not both).
               stringarray: Array of string values.
@@ -4527,15 +4547,30 @@ components:
                 - `"lessthan"`: Value is less than specified value (is less than)
                 - `"lessthanequals"`: Value is less than or equal to specified value (is less than or equals)
                 - `"startswith"`: String starts with specified prefix (starts with)
+                - `"notstartswith"`: String does not start with specified prefix (does not start with)
                 - `"endswith"`: String ends with specified suffix (ends with)
+                - `"notendswith"`: String does not end with specified suffix (does not end with)
                 - `"contains"`: String contains specified substring (contains)
                 - `"doesnotcontain"`: String does not contain specified substring (does not contain)
                 - `"empty"`: Field is missing or empty (is empty)
                 - `"notempty"`: Field contains a value (is not empty)
-                - `"matches"`: Matches a regular expression (matches)
-
-                `isempty`, `isnotempty` and `anyof` are not operators: they are refused with 422
-                "Invalid operation: <name>".
+                - `"matches"`: Matches a regular expression, ignoring case (matches)
+
+                Operator names are case-insensitive: `NOTEMPTY` and `endsWith` work and are stored
+                as sent. `isempty`, `isnotempty`, `anyof`, `notcontains`, `doesnotstartwith`,
+                `doesnotendwith`, `notmatches`, `doesnotmatch` and `notequal` are not operators:
+                they are refused with 422 "Invalid operation: <name>", with the name in lowercase,
+                both when the filter is saved and by `POST /v1/processors/filter`. To negate a
+                condition, wrap it in `not`.
+
+                The string comparisons (`equals`, `contains`, `startswith`, `endswith` and their
+                negations) are case-sensitive; wrap the field in `lowercase` to compare without case.
+                `matches` is not: every pattern is compiled with the flags `gi`, so `^paid$` also
+                matches `PAID` and `[a-z]` matches capital letters. An inline flag such as `(?i)`
+                makes the pattern invalid. The filter still saves, but in a run every record fails
+                with `FILTER_EVALUATION_FAILED` ("Invalid regular expression: /(?i)…/gi: Invalid
+                group"), and `POST /v1/processors/filter` refuses the call with 422 (live-verified
+                2026-10-22).
 
                 **Logical Operators**
                 - `"and"`: All conditions must be true
@@ -4825,7 +4860,9 @@ components:
               x-celigo-refModel: scripts
               description: |
                 Reference to the Script resource that contains the filtering logic. This must be a valid
-                ObjectId of a Script resource that exists in the system.
+                ObjectId of a Script resource in this account: any other id fails the save with 422
+                ("Only a script owned by the user or a script shared by the Integration App can be used
+                at filter.script._scriptId.").
 
                 The referenced script must contain the function specified in the `function` field
                 and must be written to handle filtering specifically. The script receives
@@ -5084,7 +5121,7 @@ components:
 
               This value is used as a fallback when:
               1. The source value doesn't match any key in the map
-              2. allowFailures is set to true
+              2. allowFailures is true or omitted
 
               Setting an appropriate default helps prevent flow failures due to unexpected
               values and provides predictable behavior for edge cases.
@@ -5094,8 +5131,10 @@ components:
               - Original value indicators: "{Original Value}", "No mapping found"
               - Neutral values: "Other", "N/A", "Miscellaneous"
 
-              If allowFailures is false, a record whose value is unmapped fails and the default
-              is ignored.
+              A save refuses a default together with an explicit `allowFailures: false`
+              (422 `Lookups with default set can not have allowFailures explicitly set to
+              false.`): a lookup either fails a miss (`allowFailures: false`, no default) or
+              falls back to its default.
             examples:
               - Unknown
               - Other
@@ -5103,7 +5142,8 @@ components:
               - Unmapped Value
               - '{Original Value}'
             x-celigo-ai-guidance:
-              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and with `allowFailures: false` a miss fails the record whatever the default. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
+              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
+              - A default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
           allowFailures:
             type:
               - boolean
@@ -5559,7 +5599,9 @@ components:
                 Reference to a predefined script resource containing the transformation logic.
 
                 The referenced script should contain the function specified in the
-                'function' property.
+                'function' property. It must be a script in this account: any other id fails the save
+                with 422 ("Only a script owned by the user or a script shared by the Integration App can
+                be used at transform.script._scriptId.").
               format: objectid
               x-celigo-refModel: scripts
               examples:
@@ -5592,7 +5634,11 @@ components:
           type: string
           format: objectId
           x-celigo-refModel: scripts
-          description: Script containing the hook function named in `function`. Send this or `_stackId`, not both.
+          description: |-
+            Script containing the hook function named in `function`. Send this or `_stackId`, not both.
+            Must be a script in this account: any other id fails the save with 422, naming the hook,
+            such as "Only a script owned by the user or a script shared by the Integration App can
+            be used at hooks.preMap._scriptId." on an import's `preMap`.
         _stackId:
           type: string
           format: objectId

package/dist/api.yml

@@ -2560,8 +2560,12 @@ components:
     Script:
       type: object
       description: |-
-        Script-mode configuration. The referenced function receives the request object
-        and must return a response with `statusCode`, `headers`, and `body`.
+        Script-mode configuration. Callers reach the API at `/v1/apis/{_id}/request`, and the
+        referenced function is called with one `options` object: `method`, `headers` (the
+        request's headers, without `Authorization`), `queryString` (the parsed query string),
+        `body`, and `rawBody` (the body as received, a string). On a GET, `body` is absent and
+        `rawBody` is empty. It returns `{statusCode, headers, body}`: `headers` is optional,
+        and `body` may be any JSON value, an array included.
       properties:
         _scriptId:
           type: string
@@ -2581,8 +2585,15 @@ components:
         - function
       x-celigo-ai-guidance:
         - |-
-          In script mode, you provide a custom JavaScript function that receives the request
-          object and returns the response. This gives you complete control over the API behavior.
+          In script mode, you provide a custom JavaScript function that receives the `options`
+          object (`method`, `headers` without `Authorization`, `queryString`, `body`, `rawBody`)
+          and returns the response. This gives you complete control over the API behavior.
+        - |-
+          The function gets no `pathParams` or `queryParams`: read the query from `queryString`.
+          A return without `statusCode`, or with a `null` or missing `body`, answers the caller
+          501 ("'StatusCode' returned by the script cannot be undefined." or "'body' returned by
+          the script cannot be undefined or null."), and an error the function throws answers
+          422 with its message. Any other `statusCode` is sent as returned.
     items:
       type: object
       required:

package/dist/asynchelper.yml

@@ -543,7 +543,11 @@ components:
 
             **Simple Types (direct value mapping)**
             - `string`: Text values, converts other types to string representation
-            - `number`: Numeric values, attempts conversion from strings
+            - `number`: Numeric values. Converts a numeric string (`"24"` → `24`,
+              `"007"` → `7`) and leaves the field out for an empty string; a value
+              holding letters or a thousands separator (`"1,250.00"`) fails the
+              record with `non_parsable_string` (`<generate>: String contains alpha
+              characters`)
             - `boolean`: True/false values, converts truthy/falsy values
 
             Dates are represented as strings — use `string` for date fields and
@@ -586,8 +590,14 @@ components:
             - |-
               Missing `dataType` is rejected at save with validation error
               `[mandatory_destination_datatype] Destination datatype is a
-              required field.` When in doubt, use `"string"` — it accepts
-              any source value and the runtime will coerce it.
+              required field.`
+            - |-
+              Give each row the type the destination field expects; `"string"` is
+              not a safe default. It accepts any source value, but sends a numeric
+              source as text (`"24"`), which a destination that checks JSON types
+              refuses. Map numeric destination fields as `number`, which fails a
+              record (`non_parsable_string`) only when the value holds letters or a
+              thousands separator.
           enum:
             - string
             - number
@@ -599,7 +609,7 @@ components:
             - objectarray
           x-enumDescriptions:
             string: Text values; converts other types to their string representation.
-            number: Numeric values; attempts conversion from strings.
+            number: Numeric values; converts numeric strings, and fails the record (`non_parsable_string`) on letters or a thousands separator.
             boolean: True/false values; converts truthy/falsy values.
             object: Nested object built from child `mappings`, or copied whole with `extract` (not both).
             stringarray: Array of string values.
@@ -1627,7 +1637,11 @@ components:
 
               **Simple Types (direct value mapping)**
               - `string`: Text values, converts other types to string representation
-              - `number`: Numeric values, attempts conversion from strings
+              - `number`: Numeric values. Converts a numeric string (`"24"` → `24`,
+                `"007"` → `7`) and leaves the field out for an empty string; a value
+                holding letters or a thousands separator (`"1,250.00"`) fails the
+                record with `non_parsable_string` (`<generate>: String contains alpha
+                characters`)
               - `boolean`: True/false values, converts truthy/falsy values
 
               Dates are represented as strings — use `string` for date fields and
@@ -1670,8 +1684,14 @@ components:
               - |-
                 Missing `dataType` is rejected at save with validation error
                 `[mandatory_destination_datatype] Destination datatype is a
-                required field.` When in doubt, use `"string"` — it accepts
-                any source value and the runtime will coerce it.
+                required field.`
+              - |-
+                Give each row the type the destination field expects; `"string"` is
+                not a safe default. It accepts any source value, but sends a numeric
+                source as text (`"24"`), which a destination that checks JSON types
+                refuses. Map numeric destination fields as `number`, which fails a
+                record (`non_parsable_string`) only when the value holds letters or a
+                thousands separator.
             enum:
               - string
               - number
@@ -1683,7 +1703,7 @@ components:
               - objectarray
             x-enumDescriptions:
               string: Text values; converts other types to their string representation.
-              number: Numeric values; attempts conversion from strings.
+              number: Numeric values; converts numeric strings, and fails the record (`non_parsable_string`) on letters or a thousands separator.
               boolean: True/false values; converts truthy/falsy values.
               object: Nested object built from child `mappings`, or copied whole with `extract` (not both).
               stringarray: Array of string values.
@@ -2825,7 +2845,7 @@ components:
 
               This value is used as a fallback when:
               1. The source value doesn't match any key in the map
-              2. allowFailures is set to true
+              2. allowFailures is true or omitted
 
               Setting an appropriate default helps prevent flow failures due to unexpected
               values and provides predictable behavior for edge cases.
@@ -2835,8 +2855,10 @@ components:
               - Original value indicators: "{Original Value}", "No mapping found"
               - Neutral values: "Other", "N/A", "Miscellaneous"
 
-              If allowFailures is false, a record whose value is unmapped fails and the default
-              is ignored.
+              A save refuses a default together with an explicit `allowFailures: false`
+              (422 `Lookups with default set can not have allowFailures explicitly set to
+              false.`): a lookup either fails a miss (`allowFailures: false`, no default) or
+              falls back to its default.
             examples:
               - Unknown
               - Other
@@ -2844,7 +2866,8 @@ components:
               - Unmapped Value
               - '{Original Value}'
             x-celigo-ai-guidance:
-              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and with `allowFailures: false` a miss fails the record whatever the default. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
+              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
+              - A default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
           allowFailures:
             type:
               - boolean
@@ -3300,7 +3323,9 @@ components:
                 Reference to a predefined script resource containing the transformation logic.
 
                 The referenced script should contain the function specified in the
-                'function' property.
+                'function' property. It must be a script in this account: any other id fails the save
+                with 422 ("Only a script owned by the user or a script shared by the Integration App can
+                be used at transform.script._scriptId.").
               format: objectid
               x-celigo-refModel: scripts
               examples:

package/dist/enduser.yml

@@ -29,7 +29,11 @@ tags:
       routes shared with workspace users. The account owner is never an end
       user: owners already have MCP access without an end-user record, the
       invite refuses the owner's address (`owner_self_invite_not_allowed`),
-      and the owner never appears in these lists.
+      and the owner never appears in these lists. Workspace administrators
+      need no record either: under Celigo OAuth they reach every MCP server in
+      the environment, and everything on it. Other workspace users need an
+      end-user record with grants. Anyone who also holds an end-user record,
+      an administrator included, is judged by that record's grants.
 
       ## End user schema