@celigo/api-specs 0.2.200 → 0.2.201

package/dist/api.yml

@@ -519,6 +519,7 @@ paths:
         | `/logging/mode` | Logging level for requests handled by this API |
         | `/logging/debugUntil` | End of a temporary full-debug capture window |
         | `/traceKeyTemplate` | Handlebars template that computes each request's trace key |
+        | `/failOnOfflineConnection` | Turn the offline-connection check on or off (boolean) |
 
         All other paths are rejected with `422`. This is the only way to change
         `logging` -- PUT silently ignores that field.
@@ -5748,6 +5749,12 @@ components:
         step's response is discarded after the call.
 
         `fields` and `lists` are plain arrays — exactly the shape GET returns.
+        Entries sent empty (`null`, `{}`, or every value `null`) are dropped on
+        save. Any other `fields` entry left with neither `extract` nor
+        `generate`, or `lists` entry with neither `generate` nor `fields` —
+        what is left of a wrapped or misspelled value such as
+        `"fields": {"type": [...]}` — fails the save with 422
+        `invalid_field_value`.
 
         Extract paths do NOT read the raw application response — the platform
         wraps every response in a canonical per-record envelope first, and
@@ -5804,10 +5811,10 @@ components:
           runs on top of it in a test run).
         - |-
           Send `fields` and `lists` as bare arrays, exactly as GET returns them.
-          Never wrap either in an object (e.g. `"fields": {"type": [...]}`): the
-          API does not reject that shape — it returns 200 and silently persists
-          `fields: [null]` / `lists: [{"fields": []}]`, erasing the step's
-          response mappings.
+          A wrapped value (e.g. `"fields": {"type": [...]}`), an empty object
+          (`"fields": {}`), or an entry holding only unknown keys fails the save
+          with 422 `invalid_field_value`, and the error's `field` names the array
+          (e.g. `pageProcessors[0].responseMapping.fields`).
         - |-
           responseMapping is fully replaced on PUT: omitting it resets the step
           to empty `{"fields": [], "lists": []}`. Always send the complete
@@ -6794,6 +6801,15 @@ components:
           description: When true, the API rejects all incoming requests.
           examples:
             - false
+        failOnOfflineConnection:
+          type: boolean
+          description: |-
+            When true, a call to a builder-mode API is refused before any step runs if a connection
+            the API uses is offline. Set to true on create when omitted. Present on responses only
+            when set: a PUT that omits it removes it, which turns the check off, and
+            `PATCH /v1/apis/{_id}` on `/failOnOfflineConnection` changes it on its own.
+          examples:
+            - true
         timeoutPeriod:
           type: integer
           minimum: 0
@@ -6801,6 +6817,9 @@ components:
           description: |-
             Request-timeout override in seconds (1–120). `0` is a sentinel meaning "use the
             120-second default" — the server rewrites it on write, so a stored value is never 0.
+            A call still running when the timeout passes answers 504 `api_timeout`. With
+            `failOnOfflineConnection` false or absent, a step whose connection is offline holds the
+            call until then.
           examples:
             - 120
             - 30
@@ -7652,7 +7671,14 @@ components:
             - /apis/v1/orders?status=open
         statusCode:
           type: integer
-          description: HTTP status code the API responded with.
+          description: |-
+            HTTP status code the API responded with. A call refused because
+            `failOnOfflineConnection` is true and a connection the API uses is offline is logged
+            with 500 and one `apiCall` step in `error` status; the caller got
+            `api_connection_offline` ("One or more connections used by this API are offline.
+            Contact the API publisher and try again later."). Neither that response nor the
+            step's log data names the connection: `GET /v1/apis/{_id}/connections` shows which
+            ones read `offline: true`. A call that ran past `timeoutPeriod` is logged with 504.
           examples:
             - 200
         traceKey:
@@ -10915,6 +10941,22 @@ components:
               an `auth.type` `oauth` connection: 422 invalid_field_update "Removing _iClientId is
               not allowed for oauth connections due to security reasons." — switch it to another
               iClient instead.
+        _tokenStoreId:
+          type: string
+          format: objectId
+          readOnly: true
+          description: |-
+            Token store holding the expiring Shopify access token that this connection shares with
+            the other connections of the same app and shop. Set only by the platform, and present
+            only when set; no API route reads the store itself. Sending the field on POST, even as
+            `null`, fails with 422 `token_store_id_not_writable`. On PUT or PATCH only a value
+            different from the stored one fails the same way (any id, on a connection that has
+            none), so sending it back unchanged or omitting it is accepted.
+          x-celigo-ai-guidance:
+            - |-
+              When creating a connection from another connection's GET response, drop
+              `http._tokenStoreId` from the body: a POST that carries it with any value, `null`
+              included, fails with 422 `token_store_id_not_writable`.
         _httpConnectorId:
           type: string
           format: objectId

package/dist/connection.yml

@@ -6763,6 +6763,22 @@ components:
               an `auth.type` `oauth` connection: 422 invalid_field_update "Removing _iClientId is
               not allowed for oauth connections due to security reasons." — switch it to another
               iClient instead.
+        _tokenStoreId:
+          type: string
+          format: objectId
+          readOnly: true
+          description: |-
+            Token store holding the expiring Shopify access token that this connection shares with
+            the other connections of the same app and shop. Set only by the platform, and present
+            only when set; no API route reads the store itself. Sending the field on POST, even as
+            `null`, fails with 422 `token_store_id_not_writable`. On PUT or PATCH only a value
+            different from the stored one fails the same way (any id, on a connection that has
+            none), so sending it back unchanged or omitting it is accepted.
+          x-celigo-ai-guidance:
+            - |-
+              When creating a connection from another connection's GET response, drop
+              `http._tokenStoreId` from the body: a POST that carries it with any value, `null`
+              included, fails with 422 `token_store_id_not_writable`.
         _httpConnectorId:
           type: string
           format: objectId

package/dist/enduser.yml

@@ -4799,6 +4799,22 @@ components:
               an `auth.type` `oauth` connection: 422 invalid_field_update "Removing _iClientId is
               not allowed for oauth connections due to security reasons." — switch it to another
               iClient instead.
+        _tokenStoreId:
+          type: string
+          format: objectId
+          readOnly: true
+          description: |-
+            Token store holding the expiring Shopify access token that this connection shares with
+            the other connections of the same app and shop. Set only by the platform, and present
+            only when set; no API route reads the store itself. Sending the field on POST, even as
+            `null`, fails with 422 `token_store_id_not_writable`. On PUT or PATCH only a value
+            different from the stored one fails the same way (any id, on a connection that has
+            none), so sending it back unchanged or omitting it is accepted.
+          x-celigo-ai-guidance:
+            - |-
+              When creating a connection from another connection's GET response, drop
+              `http._tokenStoreId` from the body: a POST that carries it with any value, `null`
+              included, fails with 422 `token_store_id_not_writable`.
         _httpConnectorId:
           type: string
           format: objectId

package/dist/flow.yml

@@ -4369,6 +4369,12 @@ components:
         step's response is discarded after the call.
 
         `fields` and `lists` are plain arrays — exactly the shape GET returns.
+        Entries sent empty (`null`, `{}`, or every value `null`) are dropped on
+        save. Any other `fields` entry left with neither `extract` nor
+        `generate`, or `lists` entry with neither `generate` nor `fields` —
+        what is left of a wrapped or misspelled value such as
+        `"fields": {"type": [...]}` — fails the save with 422
+        `invalid_field_value`.
 
         Extract paths do NOT read the raw application response — the platform
         wraps every response in a canonical per-record envelope first, and
@@ -4425,10 +4431,10 @@ components:
           runs on top of it in a test run).
         - |-
           Send `fields` and `lists` as bare arrays, exactly as GET returns them.
-          Never wrap either in an object (e.g. `"fields": {"type": [...]}`): the
-          API does not reject that shape — it returns 200 and silently persists
-          `fields: [null]` / `lists: [{"fields": []}]`, erasing the step's
-          response mappings.
+          A wrapped value (e.g. `"fields": {"type": [...]}`), an empty object
+          (`"fields": {}`), or an entry holding only unknown keys fails the save
+          with 422 `invalid_field_value`, and the error's `field` names the array
+          (e.g. `pageProcessors[0].responseMapping.fields`).
         - |-
           responseMapping is fully replaced on PUT: omitting it resets the step
           to empty `{"fields": [], "lists": []}`. Always send the complete

package/dist/marketplace.yml

@@ -435,6 +435,7 @@ paths:
                       name: Error automation via integrator.io APIs
                       docType: Template
                       type: integration
+                      celigoAgentSupported: false
                       description: Template that automates flow error handling via integrator.io APIs.
                       applications:
                         - integrator.io
@@ -544,6 +545,15 @@ components:
             on Connector entries, which install through their own route.
           examples:
             - integration
+        celigoAgentSupported:
+          type: boolean
+          description: |-
+            When true, the template is flagged for installation through the Celigo Agent (Ora)
+            guided install. Present on every `docType: Template` entry of
+            `POST /v1/published/combined`; absent on Connector entries and from
+            `GET /v1/templates/published`.
+          examples:
+            - false
         imageURL:
           type: string
           description: |-

package/dist/mcp-server.yml

@@ -7241,6 +7241,22 @@ components:
               an `auth.type` `oauth` connection: 422 invalid_field_update "Removing _iClientId is
               not allowed for oauth connections due to security reasons." — switch it to another
               iClient instead.
+        _tokenStoreId:
+          type: string
+          format: objectId
+          readOnly: true
+          description: |-
+            Token store holding the expiring Shopify access token that this connection shares with
+            the other connections of the same app and shop. Set only by the platform, and present
+            only when set; no API route reads the store itself. Sending the field on POST, even as
+            `null`, fails with 422 `token_store_id_not_writable`. On PUT or PATCH only a value
+            different from the stored one fails the same way (any id, on a connection that has
+            none), so sending it back unchanged or omitting it is accepted.
+          x-celigo-ai-guidance:
+            - |-
+              When creating a connection from another connection's GET response, drop
+              `http._tokenStoreId` from the body: a POST that carries it with any value, `null`
+              included, fails with 422 `token_store_id_not_writable`.
         _httpConnectorId:
           type: string
           format: objectId

package/dist/tool.yml

@@ -7027,7 +7027,12 @@ components:
                         the same envelope (`{{data.0.name}}`,
                         `{{#if data.length}}found{{/if}}`; dot indexes only; a
                         string result); there is no `record` object in this
-                        context, so `{{record.…}}` renders nothing.
+                        context, so `{{record.…}}` renders nothing. Entries sent
+                        empty (`null`, `{}`) are dropped on save; a `fields` entry
+                        left with neither `extract` nor `generate`, or a `lists`
+                        entry with neither `generate` nor `fields` (a wrapped or
+                        misspelled value), fails the save with 422
+                        `invalid_field_value`.
                       properties:
                         fields:
                           type: array
@@ -10229,6 +10234,22 @@ components:
               an `auth.type` `oauth` connection: 422 invalid_field_update "Removing _iClientId is
               not allowed for oauth connections due to security reasons." — switch it to another
               iClient instead.
+        _tokenStoreId:
+          type: string
+          format: objectId
+          readOnly: true
+          description: |-
+            Token store holding the expiring Shopify access token that this connection shares with
+            the other connections of the same app and shop. Set only by the platform, and present
+            only when set; no API route reads the store itself. Sending the field on POST, even as
+            `null`, fails with 422 `token_store_id_not_writable`. On PUT or PATCH only a value
+            different from the stored one fails the same way (any id, on a connection that has
+            none), so sending it back unchanged or omitting it is accepted.
+          x-celigo-ai-guidance:
+            - |-
+              When creating a connection from another connection's GET response, drop
+              `http._tokenStoreId` from the body: a POST that carries it with any value, `null`
+              included, fails with 422 `token_store_id_not_writable`.
         _httpConnectorId:
           type: string
           format: objectId

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.200",
+  "version": "0.2.201",
   "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": "72f30fe4",
+		"iasCommit": "2a2728aa",
 		"generatedAt": "2026-10-28"
 	},
 	"roots": {
@@ -2243,6 +2243,7 @@
 				"disabled": 8,
 				"draft": 8,
 				"draftExpiresAt": 0,
+				"failOnOfflineConnection": 8,
 				"function": 0,
 				"lastModified": 0,
 				"logging": 152,
@@ -3218,6 +3219,7 @@
 				"_httpConnectorId": 0,
 				"_httpConnectorVersionId": 0,
 				"_iClientId": 0,
+				"_tokenStoreId": 0,
 				"auth": 280,
 				"baseURI": 179,
 				"clientCertificates": 251,