@celigo/api-specs 0.2.99 → 0.2.101

package/dist/tool.yml

@@ -710,14 +710,26 @@ paths:
         - Tools
       summary: Clone a tool
       description: |-
-        Creates a copy of a tool in the target integration and returns a manifest of the
-        resources the clone created. The clone records its lineage in `_sourceId`, which
-        places it in the source tool's clone family.
+        Creates a copy of a tool in the target integration, together with the export and
+        import steps it references, and returns a manifest of the resources the clone
+        created. The clone records its lineage in `_sourceId`, which places it in the source
+        tool's clone family.
 
         The target integration is never inferred from the source tool — pass the source
-        tool's own integration id to clone in place.
+        tool's own integration id to clone in place. When any step of the tool references a
+        connection, `connectionMap` is required as well: every connection the tool uses must
+        appear as a key, mapped to itself to reuse it or to another connection of the account
+        to repoint the cloned steps. A tool with no connection-bearing steps clones without it.
 
-        Use `GET /v1/tools/{_id}/clone/preview` first to see what the clone would create.
+        Use `GET /v1/tools/{_id}/clone/preview` first to see what the clone would create —
+        each `Connection` object in the preview is a key `connectionMap` must carry.
+      x-celigo-ai-guidance:
+        - |-
+          Build `connectionMap` from the clone preview: one key per `Connection` object it lists,
+          each mapped to its own id unless the user asked to repoint the clone. Omitting the map
+          (or sending `{}`) when a step references a connection fails with 400
+          `invalid_connectionMap`; a key the tool does not reference, or a value that is not a
+          connection in the account, fails with 422 `invalid_connectionId` and nothing is created.
       parameters:
         - name: _id
           in: path
@@ -750,15 +762,37 @@ paths:
                   description: Name for the cloned tool. Defaults to `Clone - <source tool name>` when omitted.
                   examples:
                     - Customer enrichment tool (copy)
+                connectionMap:
+                  type: object
+                  description: |-
+                    Connection ids the tool's steps reference, each mapped to the connection the
+                    cloned steps use instead. Required when any step references a connection —
+                    omitted or empty, the clone fails with 400 `invalid_connectionMap`. Map an id
+                    to itself to keep the connection; every key must be a connection the tool
+                    references and every value a connection in the account.
+                  additionalProperties:
+                    type: string
+                    format: objectId
+                  examples:
+                    - 6ac1ef4a38b24d95ffac2545: 6ac1ef4a38b24d95ffac2545
             examples:
               default:
-                summary: Clone into the same integration
+                summary: Clone a tool with no connection-bearing steps into the same integration
                 value:
                   _integrationId: 6a429af50547257e3301246c
                   name: Customer enrichment tool (copy)
+              with_connection_map:
+                summary: Clone a tool whose lookup step uses a connection, reusing that connection
+                value:
+                  _integrationId: 6a429af50547257e3301246c
+                  name: Customer enrichment tool (copy)
+                  connectionMap:
+                    6ac1ef4a38b24d95ffac2545: 6ac1ef4a38b24d95ffac2545
       responses:
         '201':
-          description: The clone was created. Returns a manifest of the resources the clone created.
+          description: |-
+            The clone was created. Returns a manifest of every resource the clone created —
+            the new tool plus the export and import steps it copied.
           content:
             application/json:
               schema:
@@ -769,7 +803,7 @@ paths:
                   properties:
                     model:
                       type: string
-                      description: Model name of the created resource (e.g. `Tool`).
+                      description: Model name of the created resource (e.g. `Tool`, `Export`, `Import`).
                       examples:
                         - Tool
                     _id:
@@ -780,12 +814,22 @@ paths:
                         - 6a869d2f3ae8ccee42a45c44
               examples:
                 default:
-                  summary: Clone created a tool
+                  summary: Clone created a tool with no steps
                   value:
                     - model: Tool
                       _id: 6a869d2f3ae8ccee42a45c44
+                with_steps:
+                  summary: Clone created a tool and the lookup export it references
+                  value:
+                    - model: Export
+                      _id: 6ac1ef8a38b24d95ffac2d64
+                    - model: Tool
+                      _id: 6ac1ef8a38b24d95ffac2d78
         '400':
-          description: The body omits `_integrationId` (`required_field_missing`).
+          description: |-
+            The body omits `_integrationId` (`required_field_missing`), or the tool's steps
+            reference a connection and `connectionMap` is missing or empty
+            (`invalid_connectionMap`).
           content:
             application/json:
               schema:
@@ -797,10 +841,40 @@ paths:
                     errors:
                       - code: required_field_missing
                         message: 'required field: _integrationId is missing'
+                missingConnectionMap:
+                  summary: A step references a connection but no connectionMap was sent
+                  value:
+                    errors:
+                      - code: invalid_connectionMap
+                        message: The resource which you are trying to create requires a connectionMap.
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '404':
           $ref: '#/components/responses/404-not-found'
+        '422':
+          description: |-
+            `connectionMap` does not match the tool: a value is not a connection in the account,
+            or a key is not a connection the tool's steps reference (the unmapped connection is
+            reported alongside). Nothing is created.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+              examples:
+                unknownTargetConnection:
+                  summary: A mapped value is not a connection in the account
+                  value:
+                    errors:
+                      - code: invalid_connectionId
+                        message: 'The _connectionId provided for the key ''6ac1ef4a38b24d95ffac2545'': ''000000000000000000000001'' is invalid.'
+                keyNotReferenced:
+                  summary: A key is not one of the tool's connections, so the real one is unmapped
+                  value:
+                    errors:
+                      - code: invalid_connectionId
+                        message: The key '000000000000000000000001' in connectionMap doesn't match with any of the _id's of the connection documents.
+                      - code: invalid_connectionId
+                        message: 'The _connectionId provided for the key ''6ac1ef4a38b24d95ffac2545'': '''' is invalid.'
   /v1/tools/{_id}/clone/preview:
     get:
       x-internal: false
@@ -1199,6 +1273,10 @@ paths:
         broader history. Use an entry's `executionId` with
         `GET /v1/tools/{_id}/invocations/{executionId}` to drill into its steps.
 
+        Entries are written asynchronously: a run appears here a few seconds after
+        `POST /v1/tools/{_id}/invoke` returns, so re-read before concluding that a run
+        was not logged.
+
         Sandbox Tools return `403`. Custom roles only see invocations whose
         `_invokerIntegrationId` is in their accessible integrations.
       parameters:
@@ -1214,7 +1292,9 @@ paths:
               - 65a98d1ef2b40000098c3a4d
         - name: pageSize
           in: query
-          description: Number of entries per page. Larger values are clamped to 100.
+          description: |-
+            Number of entries per page. Larger values are clamped to 100; `0` or a non-numeric
+            value returns `400` `invalid_url`.
           schema:
             type: integer
             minimum: 1
@@ -1380,7 +1460,11 @@ paths:
                       nextPageUrl: null
                       prevPageUrl: null
         '400':
-          description: Invalid query parameter, for example a `status` token outside the enum.
+          description: |-
+            Invalid query parameter: a `status` token outside the enum (`invalid_status`), a
+            `sortOrder` other than `asc`/`desc` (`invalid_sort_order`), a `time_gte`/`time_lte`
+            that is not a timestamp (`invalid_field`), or a `pageSize` below 1 or non-numeric
+            (`invalid_url`).
           content:
             application/json:
               schema:
@@ -1391,6 +1475,23 @@ paths:
                     errors:
                       - code: invalid_status
                         message: Status should be either success, error or ignore.
+                invalid_sort_order:
+                  value:
+                    errors:
+                      - code: invalid_sort_order
+                        message: Sort order should be either asc or desc.
+                invalid_time:
+                  summary: '`time_gte` is not a timestamp'
+                  value:
+                    errors:
+                      - code: invalid_field
+                        message: 'The value provided for the field: ''time_gte'' is invalid.'
+                invalid_page_size:
+                  summary: '`pageSize` is 0 or not a number'
+                  value:
+                    errors:
+                      - code: invalid_url
+                        message: pageSize is not valid.
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '403':
@@ -1432,14 +1533,16 @@ paths:
         - name: time_gte
           in: query
           required: true
-          description: Start of the deletion window. Omitting it returns `400` `invalid_query_params`.
+          description: |-
+            Start of the deletion window. Must be earlier than `time_lte`; omitting either bound
+            returns `400` `invalid_query_params`.
           schema:
             type: string
             format: date-time
         - name: time_lte
           in: query
           required: true
-          description: End of the deletion window. Must not be in the future.
+          description: End of the deletion window. Neither bound may be in the future.
           schema:
             type: string
             format: date-time
@@ -1447,7 +1550,9 @@ paths:
         '202':
           description: Deletion request accepted for asynchronous processing. No body.
         '400':
-          description: Missing or invalid window parameters.
+          description: |-
+            Missing or invalid window parameters — a bound is omitted, a bound is in the future,
+            or `time_gte` is not before `time_lte`. Nothing is deleted.
           content:
             application/json:
               schema:
@@ -1458,6 +1563,21 @@ paths:
                     errors:
                       - code: invalid_query_params
                         message: time_gte query parameter is required for deleting logs.
+                missing_time_lte:
+                  value:
+                    errors:
+                      - code: invalid_query_params
+                        message: time_lte query parameter is required for deleting logs.
+                future_window:
+                  value:
+                    errors:
+                      - code: invalid_query_params
+                        message: time_gte and time_lte cannot be in the future.
+                inverted_window:
+                  value:
+                    errors:
+                      - code: invalid_query_params
+                        message: time_gte must be before time_lte.
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '403':
@@ -1479,8 +1599,12 @@ paths:
         `recordId` with the log-data endpoint to read the payload it processed.
 
         When the invocation is missing or not visible under the caller's integration ACL,
-        the endpoint returns `204 No Content`. `404` applies only to an unknown or inaccessible
-        Tool `_id`. A malformed `executionId` returns `422`. Sandbox Tools return `403`.
+        the endpoint returns `204 No Content`. The trace is written asynchronously: for a few
+        seconds after `POST /v1/tools/{_id}/invoke` returns, a valid `invocationId` also answers
+        `204`, and the header can then appear before its step records, with an empty `steps`
+        array. Re-read before treating a run as unknown or as failed before its first step.
+        `404` applies only to an unknown or inaccessible Tool `_id`. A malformed `executionId`
+        returns `422`. Sandbox Tools return `403`.
       parameters:
         - name: _id
           in: path
@@ -1556,7 +1680,9 @@ paths:
                     logMode: debug
                     steps: []
         '204':
-          description: Invocation not found or not visible under the caller's integration ACL.
+          description: |-
+            Invocation not found, not visible under the caller's integration ACL, or not yet
+            written — a run answers `204` for a few seconds after the invoke returns.
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '403':
@@ -1727,9 +1853,17 @@ paths:
         came out — selected by `_expOrImpId`, `stage`, `groupId`, and `recordId` from the
         trace-metadata response. The input and output bubbles store their payload under the
         `schemaValidation` stage; a lookup step stores the response it merged under
-        `responseMapping`. A selector that matches nothing returns `200` with an empty `logs`
-        array. Large payloads are not inlined — the entry carries an `externalReference` whose
-        `s3Key` you pass to the signed-URL endpoint.
+        `responseMapping`; a step that makes an outbound API call, such as an HTTP lookup,
+        stores each request it sent under `apiCall`, one entry per attempt, so a retried
+        request shows each failed attempt before the one that succeeded. Large payloads are
+        not inlined — the entry carries an `externalReference` whose `s3Key` you pass to the
+        signed-URL endpoint.
+
+        A selector that matches nothing returns `200` with an empty `logs` array — a stage
+        the step never ran for that record, a `groupId` from another step, and a step that
+        recorded no request all look the same. Payloads are written after the trace's step
+        records, so for a run that just finished an empty array can also mean the payload has
+        not landed yet; re-query before concluding nothing was stored.
 
         For nested Tools, set `stage` to `tool` with the nested ToolImport id to fetch the
         composed input/output payload.
@@ -1812,6 +1946,43 @@ paths:
                               orderId: SO-1043
                           errors: []
                     errors: []
+                apiCall:
+                  summary: HTTP lookup requests — a failed attempt, then the retry that succeeded
+                  value:
+                    logs:
+                      - log:
+                          apiCallTraceKeyId: M3bsB9KB
+                          stage: apiCall
+                          apiCallType: lookupexport
+                          status: failed
+                          request:
+                            method: GET
+                            uri: https://api.example.com/v1/orders
+                            headers:
+                              accept: application/json
+                              Authorization: Bearer ********
+                          response:
+                            statusCode: 503
+                            headers:
+                              content-type: text/html
+                            body: <html><head><title>503 Service Temporarily Unavailable</title></head></html>
+                      - log:
+                          apiCallTraceKeyId: cI09faBo
+                          stage: apiCall
+                          apiCallType: lookupexport
+                          status: success
+                          request:
+                            method: GET
+                            uri: https://api.example.com/v1/orders
+                            headers:
+                              accept: application/json
+                              Authorization: Bearer ********
+                          response:
+                            statusCode: 200
+                            headers:
+                              content-type: application/json; charset=utf-8
+                            body: '[{"_id":"6a50f177a8d85436a4a890db","name":"SO-1043"}]'
+                    errors: []
                 noMatch:
                   summary: Selector matched no stored payload
                   value:
@@ -3320,7 +3491,11 @@ components:
             - For regular fields: Set to the exact property name (e.g., "firstName", "price", "isActive")
             - For object fields: Set to the object property name, then add child mappings in the 'mappings' array
             - For array fields: Set to the array property name, then configure 'buildArrayHelper'
-            - For arrays within arrays: Leave EMPTY for the inner array mappings, as they don't have field names
+            - Two structural blanks: the inner array item of an array of arrays (it has no field name),
+              and the single top-level `objectarray` item of a `rows [ ]` mapping (the array output
+              structure — see the array's description). A child-bearing wrapper and a source-only row that
+              already exist in a saved document also stay unnamed when the tree is re-sent — filling in a
+              name changes the output; it does not complete the row
 
             IMPORTANT: Do NOT use dot notation (e.g., "customer.firstName") in this field. Instead, create proper
             hierarchical structure with nested mappings:
@@ -3335,8 +3510,9 @@ components:
             }
             ```
 
-            When parsing existing mappings, empty 'generate' fields almost always indicate inner array structures
-            within a parent array.
+            When parsing existing mappings, an empty `generate` inside a parent array is an inner array; an
+            empty `generate` on the ONLY top-level item, with `dataType: objectarray`, is the `rows [ ]` JSON
+            structure — array output, bound as `rows` in templates — and is intentional, not a missing name.
           examples:
             - name
             - address
@@ -4317,6 +4493,12 @@ components:
         object-array row left with no source, no destination and no remaining child `mappings` or
         `buildArrayHelper` entries; a row with only one of the two, and a source-less, destination-less
         wrapper that still has children, are kept.
+
+        The shape of the array is the mapper's **JSON structure**. Named top-level items produce an object
+        record (`record { }`). Exactly one top-level item with `dataType: objectarray` and no `generate` is
+        the `rows [ ]` structure: the mapped record is an array — usually one element per element of the
+        source array that root's `buildArrayHelper` iterates — Handlebars templates such as `http.body`
+        bind it as `rows` instead of `record`, and the mapping editor shows that row's destination disabled.
       x-celigo-ai-guidance:
         - |-
           Rows that exist in the saved document — including `Draft` and `Inactive` rows and
@@ -4325,6 +4507,14 @@ components:
           them. Only a row with neither source nor destination — and, for an object or
           object-array row, no remaining children — can be left out; the save would drop it
           anyway. A wrapper with children but no `generate` is kept by the save, so keep it.
+        - |-
+          A single unnamed top-level `objectarray` item is the `rows [ ]` JSON structure, not a
+          missing destination: keep it unnamed when editing (naming it turns the output into an
+          object, and a template that iterates `rows` then renders nothing), and author that
+          shape only when the request body must be an array or a template iterates `rows`.
+          The editor's save check accepts the unnamed root only in the `rows [ ]` structure;
+          any other row with a source and no `generate` fails with "One or more destination
+          field values not entered".
       items:
         type: object
         properties:
@@ -4340,7 +4530,11 @@ components:
               - For regular fields: Set to the exact property name (e.g., "firstName", "price", "isActive")
               - For object fields: Set to the object property name, then add child mappings in the 'mappings' array
               - For array fields: Set to the array property name, then configure 'buildArrayHelper'
-              - For arrays within arrays: Leave EMPTY for the inner array mappings, as they don't have field names
+              - Two structural blanks: the inner array item of an array of arrays (it has no field name),
+                and the single top-level `objectarray` item of a `rows [ ]` mapping (the array output
+                structure — see the array's description). A child-bearing wrapper and a source-only row that
+                already exist in a saved document also stay unnamed when the tree is re-sent — filling in a
+                name changes the output; it does not complete the row
 
               IMPORTANT: Do NOT use dot notation (e.g., "customer.firstName") in this field. Instead, create proper
               hierarchical structure with nested mappings:
@@ -4355,8 +4549,9 @@ components:
               }
               ```
 
-              When parsing existing mappings, empty 'generate' fields almost always indicate inner array structures
-              within a parent array.
+              When parsing existing mappings, an empty `generate` inside a parent array is an inner array; an
+              empty `generate` on the ONLY top-level item, with `dataType: objectarray`, is the `rows [ ]` JSON
+              structure — array output, bound as `rows` in templates — and is intentional, not a missing name.
             examples:
               - name
               - address
@@ -24907,6 +25102,23 @@ components:
               per-mode contract.  Handlebars expressions in ``extract`` always
               reference ``{{record.field}}`` regardless — only JSONPath
               behavior flips with ``inputContext``.
+            - |-
+              ## JSON structure — record { } or rows [ ]
+
+              The shape of this array is the mapper's JSON structure. Named
+              top-level items produce an object record; ``http.body`` and the
+              other templates bind it as ``record``. Exactly one top-level item
+              with ``dataType: objectarray`` and no ``generate`` is the
+              ``rows [ ]`` structure: the mapped record is an array — one
+              element per element the item's ``buildArrayHelper`` iterates —
+              and templates bind it as ``rows`` (``{{#each rows}}``), with
+              ``record.*`` undefined. The mapping editor shows that row's
+              destination disabled; its save check accepts the unnamed root
+              only in the ``rows [ ]`` structure and fails any other row that
+              has a source and no ``generate`` with "One or more destination
+              field values not entered". Keep the root unnamed when editing a
+              ``rows [ ]`` mapping — naming it turns the output into an object
+              and a ``{{#each rows}}`` body renders nothing.
             - |-
               ## IMPORT-SPECIFIC BEHAVIOR
 
@@ -30365,7 +30577,10 @@ components:
                 - '{"records": [{"id": "{{record.id}}", "exported": true}]}'
         paging:
           type: object
-          description: Controls how the export requests subsequent pages when the API returns multi-page responses. The `method` field determines which companion fields are required and how each next page is requested. For the page, skip, and token methods, reference the matching pagination variable (`{{export.http.paging.page}}`, `{{export.http.paging.skip}}`, or `{{export.http.paging.token}}`) in the relative URI or request body — misconfigured pagination is a common cause of incomplete data retrieval.
+          description: |-
+            Controls how the export requests subsequent pages when the API returns multi-page responses. The `method` field determines which companion fields are required and how each next page is requested. For the page, skip, and token methods, reference the matching pagination variable (`{{export.http.paging.page}}`, `{{export.http.paging.skip}}`, or `{{export.http.paging.token}}`) in the relative URI or request body — misconfigured pagination is a common cause of incomplete data retrieval.
+
+            When this export is the first lookup of a builder-mode API with `pagination.enabled` set, it is that API's volume driver: saving the export (even unchanged) invalidates the API's issued cursors, so a caller mid-walk gets an empty final page, and removing `paging` is accepted on save but makes every call to the API fail with `400 api_pagination_source_not_paged` until paging is restored or the API's flag is turned off.
           x-celigo-ai-guidance:
             - Configuration object for navigating through multi-page API responses.
             - |-
@@ -37196,7 +37411,10 @@ components:
             - '2026-09-22T03:27:29.411000Z'
         timeTaken:
           type: integer
-          description: Total processing time in milliseconds.
+          description: |-
+            Wall-clock duration of the invocation in milliseconds, from request to response.
+            It also counts time spent outside the steps, so it exceeds the sum of the step
+            `timeTaken` values on the trace.
           examples:
             - 1025
         logMode:
@@ -37369,7 +37587,10 @@ components:
             - '2026-09-22T03:27:29.411000Z'
         timeTaken:
           type: integer
-          description: Total processing time in milliseconds.
+          description: |-
+            Wall-clock duration of the invocation in milliseconds, from request to response.
+            It also counts time spent outside the steps, so it exceeds the sum of the step
+            `timeTaken` values — use the step sum when apportioning time across steps.
           examples:
             - 1025
         traceKey:
@@ -37415,7 +37636,8 @@ components:
           type: array
           description: |-
             Step records in execution order — input bubble, branch steps, output bubble.
-            Empty when the run failed before its first step.
+            Empty when the run failed before its first step. Step records are written after
+            the header, so a run read seconds after it finished can also return an empty array.
           items:
             $ref: '#/components/schemas/ToolInvocationStep'
     ToolChildrenResponse:
@@ -37467,10 +37689,14 @@ components:
           description: |-
             Processing stage whose payload to fetch. The input and output bubbles store their
             payload under `schemaValidation`; a lookup step stores the merged response under
-            `responseMapping`; use `tool` for a nested ToolImport's composed payload.
+            `responseMapping`; a step that makes an outbound API call, such as an HTTP lookup,
+            stores each request it sent under `apiCall`; use `tool` for a nested ToolImport's
+            composed payload. A stage the step never ran for this record returns an empty
+            `logs` array, the same as a record that stored nothing.
           examples:
             - schemaValidation
             - responseMapping
+            - apiCall
             - tool
         groupId:
           type: string
@@ -37496,12 +37722,19 @@ components:
             Small payloads are inlined under `log`; a large payload is replaced by an
             `externalReference[]` whose `source.s3Key` you pass to
             `GET /v1/tools/{_id}/invocations/{executionId}/logs/signedURL` to download it.
+            A bubble or mapping stage returns one entry per record; the `apiCall` stage
+            returns one entry per request the step sent, in order, so a retried request shows
+            each failed attempt before the one that succeeded.
           items:
             type: object
             properties:
               log:
                 type: object
-                description: Inlined payload for the selected record and stage.
+                description: |-
+                  Inlined payload for the selected record and stage. Record-level stages such
+                  as `schemaValidation` and `responseMapping` carry the timestamp, selector echo
+                  and `input` / `output` / `errors`; the `apiCall` stage carries the request sent
+                  and the response received instead.
                 properties:
                   timestamp:
                     type: string
@@ -37551,6 +37784,71 @@ components:
                     items:
                       type: object
                       additionalProperties: true
+                  apiCallTraceKeyId:
+                    type: string
+                    description: Identifier of one request attempt. Present when `stage` is `apiCall`.
+                    examples:
+                      - M3bsB9KB
+                  apiCallType:
+                    type: string
+                    description: Kind of step that sent the request, such as a lookup export. Present when `stage` is `apiCall`.
+                    examples:
+                      - lookupexport
+                  status:
+                    type: string
+                    enum:
+                      - success
+                      - failed
+                    x-enumDescriptions:
+                      success: The attempt received a response the step accepted
+                      failed: The attempt was rejected or errored; a later entry may carry the retry
+                    description: Outcome of this request attempt. Present when `stage` is `apiCall`.
+                  request:
+                    type: object
+                    description: |-
+                      The request the step sent on this attempt — `method`, `uri` and `headers`.
+                      Credential headers are masked. Present when `stage` is `apiCall`.
+                    properties:
+                      method:
+                        type: string
+                        description: HTTP method of the attempt.
+                      uri:
+                        type: string
+                        description: Full URL the attempt called.
+                      headers:
+                        type: object
+                        additionalProperties: true
+                        description: Request headers as sent, with credential values masked.
+                    additionalProperties: true
+                  response:
+                    type: object
+                    description: |-
+                      The response this attempt received — `statusCode`, `headers`, and the raw
+                      `body` as a string when the endpoint sent one. Present when `stage` is
+                      `apiCall`.
+                    properties:
+                      statusCode:
+                        type: integer
+                        description: HTTP status the endpoint returned.
+                      headers:
+                        type: object
+                        additionalProperties: true
+                        description: Response headers as received.
+                      body:
+                        type: string
+                        description: Raw response body; JSON arrives as a serialized string.
+                    additionalProperties: true
+                if:
+                  properties:
+                    stage:
+                      const: apiCall
+                  required:
+                    - stage
+                then:
+                  required:
+                    - status
+                    - request
+                    - response
                 additionalProperties: true
               externalReference:
                 type: array

package/package.json

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

package/schemas.json

@@ -1,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "6feafe65",
+		"iasCommit": "33fb4992",
 		"generatedAt": "2026-10-12"
 	},
 	"roots": {