@celigo/api-specs 0.2.38 → 0.2.40

package/dist/httpconnectorresource.yml

@@ -2,7 +2,7 @@ openapi: 3.2.0
 info:
   version: 1.0.0
   title: HTTP Connector Resources
-  description: API for reading Celigo HTTP Connector Resources — logical API resource groupings within an HTTP Connector.
+  description: API for managing Celigo HTTP Connector Resources — logical API resource groupings within an HTTP Connector.
 servers:
   - url: https://api.integrator.io
     description: Production (US / default region)
@@ -17,36 +17,37 @@ security:
 tags:
   - name: HTTP Connector Resources
     description: |-
-      API for reading HTTP Connector Resource objects in Celigo.
-      HTTP Connector Resources represent logical API resource groupings (e.g. "Account",
-      "Contact", "Order") within an HTTP Connector. Each resource is associated with one
-      or more connector versions and contains HTTP Connector Endpoints that define the
-      available operations.
+      HTTP Connector Resources are the logical API groupings (for example
+      "Account", "Contact", "Order") inside an HTTP Connector. Each resource
+      belongs to one connector, is available in one or more of its versions,
+      and owns the HTTP Connector Endpoints that define the operations users
+      can build exports and imports on.
 
-      These endpoints are **read-only** — creating, updating, and deleting HTTP Connector
-      Resources is only available through the Celigo UI (session authentication).
+      Manage your own resources through `/v1/httpconnectorresources`
+      (list, create) and `/v1/httpconnectorresources/{_id}` (get, update,
+      delete). The nested `/v1/httpconnectors/{_httpConnectorId}/...` routes
+      are read-only views scoped to one connector that also reach resources
+      published by other partners; a resource read through either route is
+      the same object.
 
       ## HTTP connector resource schema
 
       {% openapi-schemas spec="httpconnectorresource" schemas="HTTPConnectorResource" grouped="true" %}
 paths:
-  /v1/httpconnectors/{_httpConnectorId}/httpconnectorresources:
+  /v1/httpconnectorresources:
     get:
       x-internal: false
-      operationId: listHttpConnectorResources
+      operationId: listOwnHttpConnectorResources
       tags:
         - HTTP Connector Resources
-      summary: List HTTP Connector Resources for a connector
+      summary: List your HTTP Connector Resources
       description: |-
-        Returns all resources (logical API groupings) defined under the given
-        HTTP Connector.
-
-        The list response is abridged — it omits `published` and
-        `_httpConnectorId` compared to the detail endpoint. Use
-        `GET /v1/httpconnectors/{_httpConnectorId}/{_id}` for the full object.
-
-        Each resource's `_id` doubles as the `_httpConnectorResourceId` path
-        parameter used by the HTTP Connector Endpoints API.
+        Returns the full HTTP Connector Resources owned by the account, across all
+        of its connectors, sorted by name. This is the canonical CRUD listing; to
+        browse the resources of one connector — including resources published by
+        other partners — use the scoped
+        `GET /v1/httpconnectors/{_httpConnectorId}/httpconnectorresources`, which
+        returns an abridged shape.
       parameters:
         - name: limit
           in: query
@@ -57,6 +58,347 @@ paths:
             examples:
               - 100
         - $ref: '#/components/parameters/After'
+      responses:
+        '200':
+          description: Array of the account's HTTP Connector Resources.
+          headers:
+            Link:
+              description: |-
+                RFC-5988 pagination links. When more pages remain, includes a
+                `<...>; rel="next"` entry; absent on the final page.
+              schema:
+                type: string
+          content:
+            application/json:
+              schema:
+                type: array
+                items:
+                  $ref: '#/components/schemas/HTTPConnectorResource'
+              examples:
+                two_resources:
+                  value:
+                    - _id: 6ab1f8b66c46f82ea7b1f20e
+                      name: Account
+                      createdAt: '2026-09-22T03:40:38.704Z'
+                      lastModified: '2026-09-22T03:41:34.542Z'
+                      published: true
+                      _httpConnectorId: 6ab1f8b6d38090b49147cec4
+                      _versionIds:
+                        - 6ab1f8b6d38090b49147cec5
+                    - _id: 6ab1f8c4c2e18361293b46b7
+                      name: Contact
+                      createdAt: '2026-09-22T03:40:52.719Z'
+                      lastModified: '2026-09-22T03:40:52.740Z'
+                      published: false
+                      _httpConnectorId: 6ab1f8b6d38090b49147cec4
+        '204':
+          description: The account owns no HTTP Connector Resources.
+        '401':
+          $ref: '#/components/responses/401-unauthorized'
+        '403':
+          $ref: '#/components/responses/403-forbidden'
+    post:
+      x-internal: false
+      operationId: createHttpConnectorResource
+      tags:
+        - HTTP Connector Resources
+      summary: Create an HTTP Connector Resource
+      description: |-
+        Creates a resource grouping under one of your HTTP Connectors. Create the
+        connector first (`POST /v1/httpconnectors`) and pass its id as
+        `_httpConnectorId`; list the connector's `versions[]._id` values in
+        `_versionIds` to make the resource available in those versions. Endpoints
+        are then attached to the resource through
+        `POST /v1/httpconnectorendpoints`.
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Request'
+            examples:
+              minimal:
+                summary: Resource scoped to one connector version
+                value:
+                  name: Account
+                  _httpConnectorId: 6ab1f8b6d38090b49147cec4
+                  _versionIds:
+                    - 6ab1f8b6d38090b49147cec5
+              configured:
+                summary: Root resource with field catalog and export defaults
+                value:
+                  name: Order
+                  _httpConnectorId: 6ab1f8b6d38090b49147cec4
+                  _versionIds:
+                    - 6ab1f8b6d38090b49147cec5
+                  isRoot: true
+                  resourceFields:
+                    - id: id
+                      label: ID
+                      dataType: string
+                    - id: lines
+                      label: Lines
+                      dataType: objectarray
+                      resourceFields:
+                        - id: sku
+                          dataType: string
+                  supportedBy:
+                    export:
+                      preConfiguredFields:
+                        - path: http.successMediaType
+                          values:
+                            - json
+                      fieldsUserMustSet:
+                        - path: name
+                      fieldsToUnset:
+                        - http.paging
+                    import:
+                      pathParameterToIdentifyExisting: id
+      responses:
+        '201':
+          description: Created resource.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HTTPConnectorResource'
+              examples:
+                created:
+                  value:
+                    _id: 6ab1f8b66c46f82ea7b1f20e
+                    name: Account
+                    createdAt: '2026-09-22T03:40:38.704Z'
+                    lastModified: '2026-09-22T03:40:38.736Z'
+                    published: false
+                    _httpConnectorId: 6ab1f8b6d38090b49147cec4
+                    _versionIds:
+                      - 6ab1f8b6d38090b49147cec5
+        '400':
+          $ref: '#/components/responses/400-bad-request'
+        '401':
+          $ref: '#/components/responses/401-unauthorized'
+        '403':
+          $ref: '#/components/responses/403-forbidden'
+        '422':
+          description: |-
+            A required field is missing, a referenced connector or version is not
+            yours or does not exist, or `isRoot` and `_parentResourceId` were sent
+            together.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+              examples:
+                missing_name:
+                  value:
+                    errors:
+                      - field: name
+                        code: missing_required_field
+                        message: Path `name` is required.
+                invalid_connector:
+                  summary: _httpConnectorId missing or not owned by the account
+                  value:
+                    errors:
+                      - field: _httpConnectorId
+                        code: invalid_ref
+                        message: 63987132784a39b73aae63cd is not a valid _httpConnectorId
+                invalid_version:
+                  value:
+                    errors:
+                      - field: _versionId
+                        code: invalid_ref
+                        message: 6ab1f8b6d38090b491470000 is not a valid _versionId
+                root_with_parent:
+                  value:
+                    errors:
+                      - field: _parentResourceId
+                        code: invalid_field_value
+                        message: 'Invalid value for field "_parentResourceId": isRoot cannot be true when _parentResourceId is set'
+  /v1/httpconnectorresources/{_id}:
+    get:
+      x-internal: false
+      operationId: getOwnHttpConnectorResourceById
+      tags:
+        - HTTP Connector Resources
+      summary: Get one of your HTTP Connector Resources
+      description: |-
+        Returns the full resource. The nested
+        `GET /v1/httpconnectors/{_httpConnectorId}/{_id}` returns the identical
+        object and additionally reaches resources published by other partners;
+        this route is limited to resources the account owns.
+      parameters:
+        - in: path
+          name: _id
+          required: true
+          schema:
+            type: string
+            format: objectId
+            x-celigo-refModel: httpconnectorresources
+            examples:
+              - 6ab1f8b66c46f82ea7b1f20e
+          description: HTTP Connector Resource ID.
+      responses:
+        '200':
+          description: The resource.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HTTPConnectorResource'
+              examples:
+                detail:
+                  value:
+                    _id: 6ab1f8b66c46f82ea7b1f20e
+                    name: Account
+                    createdAt: '2026-09-22T03:40:38.704Z'
+                    lastModified: '2026-09-22T03:41:34.542Z'
+                    published: true
+                    _httpConnectorId: 6ab1f8b6d38090b49147cec4
+                    _versionIds:
+                      - 6ab1f8b6d38090b49147cec5
+        '401':
+          $ref: '#/components/responses/401-unauthorized'
+        '403':
+          $ref: '#/components/responses/403-forbidden'
+        '404':
+          description: No resource with this id is owned by the account.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+              examples:
+                not_found:
+                  value:
+                    errors:
+                      - code: invalid_ref
+                        message: HttpConnectorResource not found.
+    put:
+      x-internal: false
+      operationId: updateHttpConnectorResource
+      tags:
+        - HTTP Connector Resources
+      summary: Update an HTTP Connector Resource
+      description: |-
+        Replaces the resource with the request body. Send the complete document —
+        `_versionIds`, `metadata`, `resourceFields`, `supportedBy`, and the other
+        optional fields are cleared when left out, while `published` and `isRoot`
+        keep their stored values when omitted. `name` and `_httpConnectorId` are
+        required on every PUT. Publish a resource by sending `published: true`.
+      parameters:
+        - in: path
+          name: _id
+          required: true
+          schema:
+            type: string
+            format: objectId
+            x-celigo-refModel: httpconnectorresources
+            examples:
+              - 6ab1f8b66c46f82ea7b1f20e
+          description: HTTP Connector Resource ID.
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Request'
+            examples:
+              publish:
+                summary: Publish the resource
+                value:
+                  name: Account
+                  _httpConnectorId: 6ab1f8b6d38090b49147cec4
+                  _versionIds:
+                    - 6ab1f8b6d38090b49147cec5
+                  published: true
+      responses:
+        '200':
+          description: Updated resource.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HTTPConnectorResource'
+              examples:
+                published:
+                  value:
+                    _id: 6ab1f8b66c46f82ea7b1f20e
+                    name: Account
+                    createdAt: '2026-09-22T03:40:38.704Z'
+                    lastModified: '2026-09-22T03:41:34.542Z'
+                    published: true
+                    _httpConnectorId: 6ab1f8b6d38090b49147cec4
+                    _versionIds:
+                      - 6ab1f8b6d38090b49147cec5
+        '400':
+          $ref: '#/components/responses/400-bad-request'
+        '401':
+          $ref: '#/components/responses/401-unauthorized'
+        '403':
+          $ref: '#/components/responses/403-forbidden'
+        '404':
+          $ref: '#/components/responses/404-not-found'
+        '422':
+          $ref: '#/components/responses/422-unprocessable-entity'
+    delete:
+      x-internal: false
+      operationId: deleteHttpConnectorResource
+      tags:
+        - HTTP Connector Resources
+      summary: Delete an HTTP Connector Resource
+      description: |-
+        Deletes the resource. Refused while any HTTP Connector Endpoint still
+        lists it in `_httpConnectorResourceIds` — delete or re-point those
+        endpoints first. A connector likewise cannot be deleted while it still has
+        resources. Not recoverable through the recycle bin.
+      parameters:
+        - in: path
+          name: _id
+          required: true
+          schema:
+            type: string
+            format: objectId
+            x-celigo-refModel: httpconnectorresources
+            examples:
+              - 6ab1f8b66c46f82ea7b1f20e
+          description: HTTP Connector Resource ID.
+      responses:
+        '204':
+          description: Resource deleted.
+        '401':
+          $ref: '#/components/responses/401-unauthorized'
+        '403':
+          $ref: '#/components/responses/403-forbidden'
+        '404':
+          $ref: '#/components/responses/404-not-found'
+        '422':
+          description: An endpoint still references the resource.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+              examples:
+                referenced:
+                  value:
+                    errors:
+                      - code: delete_not_allowed
+                        message: 'this document is referenced by HttpConnectorEndpoint : 6ab1f999d38090b49147cf00'
+  /v1/httpconnectors/{_httpConnectorId}/httpconnectorresources:
+    get:
+      x-internal: false
+      operationId: listHttpConnectorResources
+      tags:
+        - HTTP Connector Resources
+      summary: List a connector's HTTP Connector Resources
+      description: |-
+        Returns the resources defined under the given HTTP Connector — your own
+        and, for connectors published by other partners, their published
+        resources — sorted by name. The whole list is returned in one response.
+
+        The shape is abridged: it omits `published`, `_httpConnectorId`, and the
+        configuration fields. Use `GET /v1/httpconnectors/{_httpConnectorId}/{_id}`
+        for the full object, or `GET /v1/httpconnectorresources` for the full
+        shape of everything your account owns.
+
+        Each resource's `_id` doubles as the `_httpConnectorResourceId` path
+        parameter used by the HTTP Connector Endpoints API.
+      parameters:
         - in: path
           name: _httpConnectorId
           required: true
@@ -66,17 +408,29 @@ paths:
             x-celigo-refModel: httpconnectors
             examples:
               - 63987132784a39b73aae63cd
-          description: HTTP Connector ID
+          description: HTTP Connector ID.
+        - in: query
+          name: version
+          required: false
+          schema:
+            type: string
+            format: objectId
+            examples:
+              - 63987132784a39b73aae63ce
+          description: Return only resources available in this connector version (`versions[]._id`).
+        - in: query
+          name: publishedOnly
+          required: false
+          schema:
+            type: boolean
+            default: false
+          description: |-
+            When true, returns only published resources that belong to a published
+            version of the connector. The connector itself must be published,
+            otherwise the request fails with 404.
       responses:
         '200':
-          description: Successfully retrieved list of HTTP Connector Resources
-          headers:
-            Link:
-              description: |-
-                RFC-5988 pagination links. When more pages remain, includes a `<...>; rel="next"` entry;
-                absent on the final page.
-              schema:
-                type: string
+          description: Abridged resources of the connector.
           content:
             application/json:
               schema:
@@ -99,11 +453,21 @@ paths:
                       _versionIds:
                         - 63987132784a39b73aae63ce
         '204':
-          description: No resources exist for this connector
+          description: The connector has no resources visible to the caller.
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '404':
-          $ref: '#/components/responses/404-not-found'
+          description: The connector does not exist, is not yours, and is not published.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+              examples:
+                not_found:
+                  value:
+                    errors:
+                      - code: invalid_ref
+                        message: httpConnector not found or not published.
   /v1/httpconnectors/{_httpConnectorId}/{_id}:
     get:
       x-internal: false
@@ -112,15 +476,17 @@ paths:
         - HTTP Connector Resources
       summary: Get an HTTP connector resource
       description: |-
-        Retrieves a specific HTTP Connector Resource by its unique identifier.
+        Retrieves a specific HTTP Connector Resource by its unique identifier —
+        the same object `GET /v1/httpconnectorresources/{_id}` returns, but this
+        route also reaches resources published by other partners.
 
         The path uses a shortcut form: `/v1/httpconnectors/{_httpConnectorId}/{_id}`
         where `{_id}` is the resource ID directly under the connector. The longer
         form `/v1/httpconnectors/{_httpConnectorId}/httpconnectorresources/{_id}`
         is not supported and fails with an `invalid_ref` error.
 
-        The detail response includes `published` and `_httpConnectorId` fields
-        that are omitted from the list endpoint.
+        The detail response includes `published`, `_httpConnectorId`, and the
+        configuration fields that are omitted from the list endpoint.
       parameters:
         - in: path
           name: _httpConnectorId
@@ -204,47 +570,715 @@ components:
       schema:
         type: string
   schemas:
-    ListItem:
+    ResourceField:
       type: object
-      description: |-
-        Abridged HTTP Connector Resource as returned in list responses. Omits
-        `published` and `_httpConnectorId` compared to the detail response.
+      description: One field of the resource's records, optionally with nested child fields.
+      required:
+        - id
       properties:
-        _id:
+        id:
           type: string
-          format: objectId
-          description: Unique identifier
-          readOnly: true
-          x-celigo-refModel: httpconnectorresources
+          description: Field identifier as it appears in the record.
           examples:
-            - 63987132784a39b73aae63e7
+            - id
+        label:
+          type: string
+          description: Display label for the field.
+          examples:
+            - ID
+        description:
+          type: string
+          description: Help text describing the field.
+          examples:
+            - Record identifier
+        dataType:
+          type: string
+          description: Data type label for the field, stored as given.
+          examples:
+            - string
+        metadata:
+          type: object
+          additionalProperties: true
+          description: Free-form metadata for the field.
+        resourceFields:
+          type: array
+          description: Child fields of an object or array field. Absent when the field is scalar.
+          items:
+            type: object
+            additionalProperties: true
+            description: Nested field with the same shape as its parent.
+    Filter:
+      type: object
+      description: |
+        Configuration for selectively processing records based on specified criteria. This object enables
+        precise control over which items are included or excluded from processing operations.
+
+        **Filter behavior**
+
+        When configured, the filter is applied before processing begins:
+        - Items that match the filter criteria are processed
+        - Items that don't match are completely skipped
+        - No partial processing is performed
+
+        **Implementation approaches**
+
+        There are two distinct filtering mechanisms available:
+
+        **Rule-Based Filtering (`type: "expression"`)**
+        - **Best For**: Common filtering patterns based on standard attributes
+        - **Capabilities**: Filter by names, values, dates, numerical ranges, text patterns
+        - **Advantages**: Declarative, no coding required, consistent performance
+        - **Configuration**: Define rules in the `expression` object
+        - **Use When**: You have clear, static criteria for selection
+
+        **Script-Based Filtering (`type: "script"`)**
+        - **Best For**: Complex logic, dynamic criteria, or business rules
+        - **Capabilities**: Full programmatic control, access to complete metadata
+        - **Advantages**: Maximum flexibility, can implement any filtering logic
+        - **Configuration**: Reference a script in the `script` object
+        - **Use When**: Simple rules aren't sufficient or logic needs to be dynamic
+      properties:
+        type:
+          type: string
+          description: |
+            Determines which filtering mechanism to use. This choice affects which properties
+            must be configured and how filtering logic is implemented.
+
+            **Available types**
+
+            **Rule-Based Filtering (`"expression"`)**
+            - **Required Config**: The `expression` object with rule definitions
+            - **Behavior**: Evaluates declarative rules against item attributes
+            - **Best For**: Common patterns like name matching, date ranges, value limits
+            - **Advantages**: Simpler to configure, no custom code required
+
+            **Script-Based Filtering (`"script"`)**
+            - **Required Config**: The `script` object with _scriptId and function
+            - **Behavior**: Executes custom JavaScript to determine which items to process
+            - **Best For**: Complex conditions, business logic, dynamic criteria
+            - **Advantages**: Maximum flexibility, can implement any logic
+
+            **Implementation guidance**
+
+            1. For standard filtering needs (name, size, date), use `"expression"`
+            2. For complex logic or conditions not covered by expressions, use `"script"`
+            3. When selecting a type, you must configure the corresponding object:
+                - `type: "expression"` requires the `expression` object
+                - `type: "script"` requires the `script` object
+          enum:
+            - expression
+            - script
+          x-enumDescriptions:
+            expression: Rule-based filtering using declarative conditions.
+            script: Script-based filtering using custom JavaScript logic.
+          examples:
+            - expression
+            - script
+        expression:
+          type: object
+          description: |
+            Configuration for declarative rule-based filtering. This object enables filtering
+            items based on common attributes without requiring custom code.
+
+            **Usage context**
+
+            This object is REQUIRED when `filter.type` is set to "expression" and should not be
+            configured otherwise. It provides a standardized way to define filtering rules that
+            can match against item attributes like name, type, value, date, and other properties.
+
+            **Implementation guidance**
+
+            The expression system uses a rule-based approach where:
+            - Rules can be combined with AND/OR logic
+            - Each rule can check a specific attribute
+            - Multiple conditions can be applied (ranges, pattern matching, exact matches)
+
+            **Common filter patterns**
+
+            1. **Pattern matching**: Using wildcards like `*` and `?`
+            2. **Value range filtering**: Numbers between min and max values
+            3. **Date range filtering**: Items created/modified within specific time ranges
+            4. **Status checking**: Items with specific status values or properties
+
+            For AI agents: Rule-based filtering should be your first choice when the filtering criteria
+            can be expressed in terms of standard attributes. Only use script-based filtering when
+            more complex logic is required.
+          properties:
+            version:
+              type: string
+              description: |
+                Version identifier for the expression format. Currently only version "1" is supported.
+
+                This field ensures future compatibility if the expression format evolves. Always set to "1"
+                for current implementations.
+              enum:
+                - '1'
+              x-enumDescriptions:
+                '1': Current and only supported filter expression version.
+              examples:
+                - '1'
+            rules:
+              type: array
+              description: |
+                Expression array defining filter conditions using prefix notation. The first element is the operator,
+                followed by its operands which may themselves be nested expression arrays.
+
+                The rule expression follows this pattern:
+                - First element: Operator name (string)
+                - Remaining elements: Operands for that operator (values or nested expressions)
+
+                **Expression structure**
+
+                Filter expressions use a prefix notation where operators appear before their operands:
+                ```
+                [operator, operand1, operand2, ...]
+                ```
+
+                **Comparison Operators**
+                - `"equals"`: Exact match (equals)
+                - `"notequals"`: Not equal to value (not equals)
+                - `"greaterthan"`: Value is greater than specified value (is greater than)
+                - `"greaterthanequals"`: Value is greater than or equal to specified value (is greater than or equals)
+                - `"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)
+                - `"endswith"`: String ends with specified suffix (ends with)
+                - `"contains"`: String contains specified substring (contains)
+                - `"doesnotcontain"`: String does not contain specified substring (does not contain)
+                - `"isempty"`: Field is empty or null (is empty)
+                - `"isnotempty"`: Field contains a value (is not empty)
+                - `"matches"`: Matches specified pattern (matches)
+
+                **Logical Operators**
+                - `"and"`: All conditions must be true
+                - `"or"`: At least one condition must be true
+                - `"not"`: Negates the condition
+
+                **Field Access and Type Conversion**
+                - `"extract"`: Access a field from the item by name
+                - `"settings"`: Access a custom setting from the flow, flow step, or integration configuration
+                - `"boolean"`: Convert value to Boolean type
+                - `"epochtime"`: Convert value to Epoch Time (Unix timestamp)
+                - `"number"`: Convert value to Number type
+                - `"string"`: Convert value to String type
+
+                **Field Access Details**
+
+                **Using `extract` to access record fields:**
+                - Retrieves values from the current record being processed
+                - Can access nested properties using dot notation (e.g., `"customer.email"`)
+                - Returns the raw field value which may need type conversion
+
+                **Using `settings` to access configuration values:**
+                - Retrieves values from the integration's configuration settings
+                - Supports different scopes with prefix notation:
+                  - `flow.settingName`: Access flow-level settings
+                  - `export.settingName`: Access export-level settings
+                  - `import.settingName`: Access import-level settings
+                  - `integration.settingName`: Access integration-level settings
+                - Useful for dynamic filtering based on configuration
+
+                **Field Transformations**
+                - `"lowercase"`: Convert string to lowercase
+                - `"uppercase"`: Convert string to uppercase
+                - `"ceiling"`: Round number up to the nearest integer
+                - `"floor"`: Round number down to the nearest integer
+                - `"abs"`: Get absolute value of a number
+
+                Type conversion operators are often necessary when comparing extracted field values against literals or when the field type doesn't match the comparison operator's expected type. For example:
+
+                ```json
+                [
+                  "equals",
+                  [
+                    "number",  // Convert to number before comparison
+                    [
+                      "extract",
+                      "quantity"
+                    ]
+                  ],
+                  100
+                ]
+                ```
+
+                Example with datetime conversion:
+                ```json
+                [
+                  "greaterthan",
+                  [
+                    "epochtime",  // Convert to Unix timestamp before comparison
+                    [
+                      "extract",
+                      "createdDate"
+                    ]
+                  ],
+                  1609459200000  // January 1, 2021 as Unix timestamp in milliseconds
+                ]
+                ```
+
+                Example with transformations:
+                ```json
+                [
+                  "and",
+                  [
+                    "matches",
+                    [
+                      "lowercase",  // Convert to lowercase before matching
+                      [
+                        "string",
+                        [
+                          "extract",
+                          "categories"
+                        ]
+                      ]
+                    ],
+                    "netsuite"
+                  ],
+                  [
+                    "notequals",
+                    [
+                      "string",
+                      [
+                        "extract",
+                        "recurrence.pattern.type"
+                      ]
+                    ],
+                    ""
+                  ]
+                ]
+                ```
+
+                Example comparing a record field with a flow setting:
+                ```json
+                [
+                  "equals",
+                  [
+                    "string",
+                    [
+                      "extract",
+                      "trantype"
+                    ]
+                  ],
+                  [
+                    "string",
+                    [
+                      "settings",
+                      "flow.trantype"
+                    ]
+                  ]
+                ]
+                ```
+
+                **Examples**
+
+                Example 1: Status field is not equal to "cancelled"
+                ```json
+                [
+                  "notequals",
+                  [
+                    "extract",
+                    "status"
+                  ],
+                  "cancelled"
+                ]
+                ```
+
+                Example 2: Filename starts with "HC"
+                ```json
+                [
+                  "startswith",
+                  [
+                    "extract",
+                    "filename"
+                  ],
+                  "HC"
+                ]
+                ```
+
+                Example 3: Amount is greater than 100
+                ```json
+                [
+                  "greaterthan",
+                  [
+                    "number",
+                    [
+                      "extract",
+                      "amount"
+                    ]
+                  ],
+                  100
+                ]
+                ```
+
+                Example 4: Order date is after January 1, 2023
+                ```json
+                [
+                  "greaterthan",
+                  [
+                    "extract",
+                    "orderDate"
+                  ],
+                  "2023-01-01T00:00:00Z"
+                ]
+                ```
+
+                Example 5: Category contains any of ["Urgent", "High Priority"]
+                ```json
+                [
+                  "anyof",
+                  [
+                    "extract",
+                    "category"
+                  ],
+                  ["Urgent", "High Priority"]
+                ]
+                ```
+              items:
+                oneOf:
+                  - title: String
+                    type: string
+                  - title: Number
+                    type: number
+                  - title: Boolean
+                    type: boolean
+                  - title: Object
+                    type: object
+                  - title: Array
+                    type: array
+                  - title: 'Null'
+                    type: 'null'
+        script:
+          type: object
+          description: |
+            Configuration for programmable script-based filtering. This object enables complex, custom
+            filtering logic beyond what expression-based filtering can provide.
+
+            **Usage context**
+
+            This object is REQUIRED when `filter.type` is set to "script" and should not be configured
+            otherwise. It provides a way to execute custom JavaScript code to determine which items
+            should be processed.
+
+            **Implementation approach**
+
+            Script-based filtering works by:
+            1. Executing the specified function from the referenced script
+            2. Passing item data to the function
+            3. Using the function's return value (true/false) to determine inclusion
+
+            **Common use cases**
+
+            Script filtering is ideal for:
+            - Complex business logic that can't be expressed as simple rules
+            - Dynamic filtering criteria that change based on external factors
+            - Content-based filtering that requires deep inspection
+            - Advanced pattern matching beyond simple wildcards
+            - Multi-stage filtering with intermediate logic
+
+            For AI agents: Only use script-based filtering when expression-based filtering is insufficient.
+            Script filtering requires maintaining custom code, which adds complexity to the integration.
+          properties:
+            _scriptId:
+              type: string
+              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.
+
+                The referenced script must contain the function specified in the `function` field
+                and must be written to handle filtering specifically. The script receives
+                item data as its input and must return a boolean value indicating whether
+                to process the item (true) or skip it (false).
+
+                Format: 24-character hexadecimal string (MongoDB ObjectId)
+              examples:
+                - 60a2c4e6f321d800129a1a3c
+                - 5f8d43a1b9e5a80011a35f2c
+            function:
+              type: string
+              description: |
+                Name of the function within the script to execute for filtering decisions. This function
+                must exist in the script referenced by _scriptId.
+
+                **Function requirements**
+
+                The specified function must:
+                - Accept item data as its first parameter
+                - Return a boolean value (true to process the item, false to skip it)
+                - Handle errors gracefully
+                - Execute efficiently (as it may run for many items)
+
+                **Function signature**
+
+                ```javascript
+                function filterItems(itemData) {
+                  // itemData contains properties of the item being evaluated
+                  // Custom logic here
+                  return true; // or false to skip the item
+                }
+                ```
+
+                For AI agents: Ensure the function name exactly matches a function defined in the
+                referenced script, as mismatches will cause the filter to fail.
+              examples:
+                - filterItems
+                - shouldProcess
+                - evaluateMatch
+    ResourceSupportedBySection:
+      type: object
+      description: |-
+        Conditions, pre-configured field values, required user inputs, and
+        fields to clear for one resource type (export or import) created from
+        this resource.
+      properties:
+        conditions:
+          type: array
+          description: |-
+            Expression-based filters referenced by `_conditionIds` in
+            `preConfiguredFields` and `fieldsUserMustSet` to apply those entries
+            conditionally.
+          items:
+            type: object
+            properties:
+              _id:
+                type: string
+                format: objectId
+                readOnly: true
+                description: Identifier of this condition, referenced by `_conditionIds` in field entries.
+                examples:
+                  - 5f8d43a1b9e5a80011a35f2c
+              condition:
+                $ref: '#/components/schemas/Filter'
+        preConfiguredFields:
+          type: array
+          description: Fields set automatically on the generated export or import. Not editable by the user.
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+                description: Dot-notation path of the field on the generated export or import.
+                examples:
+                  - http.successMediaType
+              values:
+                type: array
+                description: Value(s) to assign. Typically a single-element array; entries may be any JSON type.
+                examples:
+                  - - json
+              _conditionIds:
+                type: array
+                description: Condition IDs that must be satisfied for this entry to apply. Always applies when absent.
+                items:
+                  type: string
+                  format: objectId
+                  examples:
+                    - 5f8d43a1b9e5a80011a35f2c
+        fieldsUserMustSet:
+          type: array
+          description: Fields the user must provide values for on the generated export or import.
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+                description: Dot-notation path of the field on the generated export or import.
+                examples:
+                  - name
+              values:
+                type: array
+                description: Optional suggested or constrained values. Entries may be any JSON type.
+                examples:
+                  - - delta
+                    - test
+              _conditionIds:
+                type: array
+                description: Condition IDs that must be satisfied for this entry to apply.
+                items:
+                  type: string
+                  format: objectId
+                  examples:
+                    - 5f8d43a1b9e5a80011a35f2c
+              helpURL:
+                type: string
+                description: URL to documentation for this field.
+                examples:
+                  - https://docs.celigo.com/hc/en-us
+              labelOverride:
+                type: string
+                description: Custom label shown in the UI instead of the default.
+                examples:
+                  - Record name
+        fieldsToUnset:
+          type: array
+          description: Dot-notation paths to clear on the generated export or import.
+          items:
+            type: string
+            examples:
+              - http.paging
+    ResourceSupportedBy:
+      type: object
+      description: |-
+        Defaults the connector framework applies when a user builds an export or
+        an import on one of this resource's endpoints. Each section
+        pre-configures fields, lists the fields the user must still fill in, and
+        clears fields that do not apply.
+      properties:
+        export:
+          $ref: '#/components/schemas/ResourceSupportedBySection'
+        import:
+          allOf:
+            - $ref: '#/components/schemas/ResourceSupportedBySection'
+            - type: object
+              properties:
+                pathParameterToIdentifyExisting:
+                  type: string
+                  description: |-
+                    Path parameter whose value identifies the existing record on
+                    an update or upsert import. Needed only when the endpoint has
+                    more than one path parameter.
+                  examples:
+                    - id
+                lookupToIdentifyExisting:
+                  type: object
+                  description: |-
+                    Lookup the import runs to find out whether a record already
+                    exists before deciding between create and update. Both
+                    fields go together — sending one without the other is
+                    rejected.
+                  properties:
+                    _httpConnectorEndpointId:
+                      type: string
+                      format: objectId
+                      x-celigo-refModel: httpconnectorendpoints
+                      description: |-
+                        HTTP Connector Endpoint that performs the lookup. Must be
+                        an existing endpoint.
+                      examples:
+                        - 63987132784a39b73aae63ea
+                    extract:
+                      type: string
+                      description: Path in the lookup response to read the existing record's identifier from.
+                      examples:
+                        - data.0.id
+    HTTPConnectorResourceBase:
+      type: object
+      description: Writable fields shared by the request and response schemas.
+      properties:
         name:
           type: string
-          description: Resource name
+          description: Human-readable name of the API resource this grouping represents (for example "Account", "Contact", "Order").
           examples:
             - Account
+        published:
+          type: boolean
+          default: false
+          description: |-
+            When true, the resource is visible to users of the connector's
+            published catalog. Only resources whose owner may publish HTTP
+            connectors appear to other accounts.
+        _httpConnectorId:
+          type: string
+          format: objectId
+          x-celigo-refModel: httpconnectors
+          description: |-
+            HTTP Connector this resource belongs to. Must be a connector owned by
+            the caller's account.
+          examples:
+            - 63987132784a39b73aae63cd
+        _httpConnectorApiId:
+          type: string
+          format: objectId
+          description: |-
+            API group (an entry of the connector's `apis[]`) this resource belongs
+            to. Set only for grouped connectors; flat connectors scope resources by
+            `_versionIds` instead.
+          examples:
+            - 63987132784a39b73aae63d0
         _versionIds:
           type: array
-          description: Connector version IDs this resource belongs to
+          description: |-
+            Connector (or API group) versions this resource is available in. Each
+            id must be one of the connector's `versions[]._id` values.
           items:
             type: string
             format: objectId
-            examples:
-              - 63987132784a39b73aae63ce
-        createdAt:
-          type: string
-          format: date-time
-          readOnly: true
-          description: Timestamp when created
           examples:
-            - '2023-01-17T09:51:53.665Z'
-        lastModified:
+            - - 63987132784a39b73aae63ce
+        _parentResourceId:
           type: string
-          format: date-time
-          readOnly: true
-          description: Timestamp when last modified
+          format: objectId
+          x-celigo-refModel: httpconnectorresources
+          description: |-
+            Parent resource when this resource is nested under another one (for
+            example "Order line" under "Order"). Omit for top-level resources;
+            cannot be combined with `isRoot: true`.
           examples:
-            - '2024-05-23T07:00:29.858Z'
+            - 63987132784a39b73aae63e7
+        isRoot:
+          type: boolean
+          default: false
+          description: |-
+            When true, marks the resource as the root of a resource hierarchy.
+            Rejected together with `_parentResourceId`.
+        metadata:
+          type: object
+          additionalProperties: true
+          description: Free-form metadata stored with the resource, for example Data Intelligence attributes.
+          examples:
+            - note: Primary sales object
+        resourceFields:
+          type: array
+          description: |-
+            Field catalog of the records this resource returns, used by tooling to
+            describe the API's payloads. Fields nest through their own
+            `resourceFields`.
+          items:
+            $ref: '#/components/schemas/ResourceField'
+        supportedBy:
+          $ref: '#/components/schemas/ResourceSupportedBy'
+    HTTPConnectorResource:
+      type: object
+      required:
+        - _id
+        - _httpConnectorId
+        - name
+        - published
+        - createdAt
+        - lastModified
+      description: |-
+        HTTP Connector Resource as returned by `GET /v1/httpconnectorresources`,
+        `GET /v1/httpconnectorresources/{_id}`, and the nested
+        `GET /v1/httpconnectors/{_httpConnectorId}/{_id}` — all three return the
+        same object. Optional fields that were never set are absent.
+      allOf:
+        - $ref: '#/components/schemas/HTTPConnectorResourceBase'
+        - type: object
+          properties:
+            _id:
+              type: string
+              format: objectId
+              readOnly: true
+              x-celigo-refModel: httpconnectorresources
+              description: |-
+                Unique identifier for the resource. Doubles as the
+                `_httpConnectorResourceId` path parameter of the HTTP Connector
+                Endpoints API.
+              examples:
+                - 63987132784a39b73aae63e7
+            createdAt:
+              type: string
+              format: date-time
+              readOnly: true
+              description: Timestamp when the resource was created.
+              examples:
+                - '2023-01-17T09:51:53.665Z'
+            lastModified:
+              type: string
+              format: date-time
+              readOnly: true
+              description: Timestamp when the resource was last updated. Changes on every PUT.
+              examples:
+                - '2024-05-23T07:00:31.350Z'
     Error:
       type: object
       description: Standard error response envelope returned by integrator.io APIs.
@@ -285,65 +1319,68 @@ components:
               - message
       required:
         - errors
-    HTTPConnectorResource:
+    Request:
       type: object
+      description: |-
+        Fields for creating or updating an HTTP Connector Resource through
+        `POST /v1/httpconnectorresources` and `PUT /v1/httpconnectorresources/{_id}`.
+        PUT replaces the whole document — omitted optional fields are cleared,
+        except `published` and `isRoot`, which keep their stored values.
       required:
-        - _id
+        - name
         - _httpConnectorId
+      x-celigo-ai-guidance:
+        - Omitting _httpConnectorId fails with 422 invalid_ref " is not a valid _httpConnectorId"; omitting name fails with 422 missing_required_field. _versionIds is optional but each id must be one of the connector's versions[]._id values or the create fails with 422 invalid_ref "<id> is not a valid _versionId".
+      allOf:
+        - $ref: '#/components/schemas/HTTPConnectorResourceBase'
+    ListItem:
+      type: object
+      description: |-
+        Abridged HTTP Connector Resource returned by the nested
+        `GET /v1/httpconnectors/{_httpConnectorId}/httpconnectorresources`
+        catalog listing. Omits `published`, `_httpConnectorId`, and the
+        configuration fields; fetch the full object by id.
+      required:
+        - _id
         - name
-        - published
         - createdAt
         - lastModified
-      description: HTTP Connector Resource object as returned by the API
       properties:
         _id:
           type: string
           format: objectId
-          description: Unique identifier for the HTTP Connector Resource
           readOnly: true
           x-celigo-refModel: httpconnectorresources
+          description: Unique identifier for the resource.
           examples:
             - 63987132784a39b73aae63e7
         name:
           type: string
-          description: Human-readable name for this resource (e.g. "Account", "Contact", "Order")
+          description: Human-readable name of the API resource.
           examples:
             - Account
-        published:
-          type: boolean
-          description: When true, this resource is published and visible to users.
-        _httpConnectorId:
-          type: string
-          format: objectId
-          description: |-
-            Parent HTTP Connector ID. Only present in the detail (by-ID) response,
-            omitted from list responses.
-          readOnly: true
-          x-celigo-refModel: httpconnectors
-          examples:
-            - 63987132784a39b73aae63cd
         _versionIds:
           type: array
-          description: Connector version IDs this resource belongs to
+          description: Connector version IDs this resource is available in. Absent when the resource is not tied to a version.
           items:
             type: string
             format: objectId
-            examples:
-              - 63987132784a39b73aae63ce
+          examples:
+            - - 63987132784a39b73aae63ce
         createdAt:
           type: string
           format: date-time
-          description: Timestamp when created
           readOnly: true
+          description: Timestamp when the resource was created.
           examples:
             - '2023-01-17T09:51:53.665Z'
         lastModified:
           type: string
           format: date-time
-          description: Timestamp when last modified
           readOnly: true
+          description: Timestamp when the resource was last updated.
           examples:
-            - '2024-05-23T07:00:31.350Z'
+            - '2024-05-23T07:00:29.858Z'
   responses:
     401-unauthorized:
       description: |-
@@ -379,6 +1416,32 @@ components:
               summary: Bearer token invalid or revoked
               value:
                 message: Bearer Authentication Failed
+    403-forbidden:
+      description: |
+        Forbidden. The authenticated caller does not have permission to perform this operation.
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/Error'
+          examples:
+            default:
+              value:
+                errors:
+                  - code: forbidden
+                    message: You do not have permission to access this resource.
+    400-bad-request:
+      description: |
+        Bad request. The server could not understand the request because of malformed syntax or invalid parameters.
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/Error'
+          examples:
+            default:
+              value:
+                errors:
+                  - code: invalid_request
+                    message: The request body failed validation.
     404-not-found:
       description: |
         Not found. The requested resource does not exist or is not visible to the caller.
@@ -392,5 +1455,18 @@ components:
                 errors:
                   - code: not_found
                     message: The requested resource was not found.
+    422-unprocessable-entity:
+      description: |
+        Unprocessable entity. The request was well-formed but was unable to be followed due to semantic errors.
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/Error'
+          examples:
+            default:
+              value:
+                errors:
+                  - code: unprocessable_entity
+                    message: The request could not be processed due to a semantic error.
 x-enable-proxy: true
 x-internal: false