@celigo/api-specs 0.2.96 → 0.2.98

package/dist/flow.yml

@@ -418,7 +418,7 @@ paths:
       summary: Patch a flow
       description: |-
         Partially updates a flow using a JSON Patch document (RFC 6902).
-        Only the `replace` operation is supported, and only on the following
+        `replace`, `add`, and `remove` operations are accepted only on the following
         whitelisted paths:
 
         | Path | Description |
@@ -430,13 +430,12 @@ paths:
         | `/logging/mode` | Logging mode |
         | `/runPageGeneratorsInParallel` | Run page generators in parallel |
         | `/aiDescription` | AI-generated description object |
-        | `/schedule/frequency` | Schedule frequency |
-        | `/schedule/startDate` | Schedule start date |
-        | `/schedule/endDate` | Schedule end date |
-        | `/schedule/days` | Schedule days |
-        | `/schedule/cron` | Cron expression |
+        | `/schedule` | Celigo 6-field cron string (same as PUT `schedule`) |
+        | `/timezone` | IANA timezone string |
 
-        All other paths are rejected with 422.
+        All other paths are rejected with 422, except pointers nested under `/schedule`
+        (such as `/schedule/cron`): `schedule` is a string, so those return 204 and change
+        nothing. Send the whole cron string to `/schedule` instead.
 
         PATCH is safer than PUT for toggling `disabled` or arming debug logging because it won't
         accidentally reset other fields. To arm debug logging, `replace` `/logging/debugUntil` with
@@ -476,11 +475,11 @@ paths:
                     path: /logging/debugUntil
                     value: '2026-05-02T16:00:00.000Z'
               update_schedule:
-                summary: Change schedule frequency
+                summary: Change Celigo 6-field schedule cron
                 value:
                   - op: replace
-                    path: /schedule/frequency
-                    value: 0 */6 * * *
+                    path: /schedule
+                    value: '? 5 0,6,12,18 ? * *'
       responses:
         '204':
           description: Flow patched successfully.

package/dist/iclient.yml

@@ -1160,27 +1160,16 @@ components:
             clientSecret:
               type: string
               description: |-
-                OAuth 2.0 client secret. Returned masked as `"******"`.
-                Re-send that value on update to keep it; it is not preserved if omitted.
+                OAuth 2.0 client secret. Returned masked as `"******"`; re-send that mask
+                on update to keep the stored secret. Required whenever `oauth2` is sent, on
+                create and update: omitting it or sending an empty string fails with 422
+                `missing_required_field` rather than clearing the secret.
               x-celigo-ai-guidance:
                 - |-
-                  ## IMPLEMENTATION GUIDANCE:
-                  - Provide the plain client secret value here to set/update it.
-                  - To keep the existing secret unchanged during an update, omit this field (or, if the API/UI returns a masked value, keep `"******"` as-is).
-                - |-
-                  This is the value you provide to configure or update the iClient.
-                  Internally,
-                  integrator.io stores this secret encrypted at rest (for example as
-                  `clientSecret_crypt` and `clientSecret_salt` fields in the underlying model),
-                  and API responses typically return a masked value (e.g.,
-                  `"******"`) when a secret is already set.
-                - |-
-                  This is the value you provide to configure or update the iClient.
-                  Internally,
-                  integrator.io stores this secret encrypted at rest (for example as
-                  `clientSecret_crypt` and `clientSecret_salt` fields in the underlying model),
-                  and API responses typically return a masked value (e.g.,
-                  `"******"`) when a secret is already set.
+                  Send the plain secret to set or replace it. To keep the stored secret on a
+                  PUT, send "******" (the masked value GET returns). Never omit clientSecret
+                  while sending other oauth2 fields: create and update both fail with 422
+                  missing_required_field on oauth2.clientSecret.
                 - |-
                   This is the value you provide to configure or update the iClient.
                   Internally,

package/dist/lookupcache.yml

@@ -410,9 +410,11 @@ paths:
       summary: Upsert entries into a lookup cache
       description: |-
         Writes key-value entries to a lookup cache. Keys that already exist are
-        overwritten; new keys are created. Keys are strings; values may be strings or
-        objects — arrays at the top level are rejected (wrap them in an object). One
-        invalid value fails the entire batch with `400 invalid_value`.
+        overwritten; new keys are created. Values may be null, numbers, booleans,
+        strings, or objects — arrays at the top level are rejected (wrap them in an
+        object). One invalid entry fails the entire batch and nothing in it is written:
+        a bad value returns `400 invalid_value`, and an empty, missing, or over-length
+        key returns `400 cache_dynamodb_invalid_key`.
 
         The service rejects batches larger than ~1000 entries or ~5 MB of JSON.
         Callers uploading more than that should split their payload; the Celigo CLI
@@ -979,15 +981,17 @@ components:
     LookupCacheDataEntry:
       type: object
       description: |-
-        A single key-value pair stored in a lookup cache. Keys are strings; values are
-        either strings or objects — the cache preserves whichever JSON shape was
-        upserted. Top-level arrays are **rejected** at upsert with
-        `400 invalid_value "The value provided corresponding to the key: <k> is invalid"`;
-        callers that need to store an array should wrap it in an object
-        (e.g. `{ "items": [...] }`).
+        A single key-value pair stored in a lookup cache. Values may be JSON null, number,
+        boolean, string, or object, and each is read back with the type it was upserted
+        with. Top-level arrays are **rejected** at upsert with
+        `400 invalid_value "The value provided corresponding to the key: <k> is invalid"`,
+        as are objects that carry their own top-level `key` property; callers that need to
+        store an array should wrap it in an object (e.g. `{ "items": [...] }`).
       properties:
         key:
           type: string
+          minLength: 1
+          maxLength: 255
           description: |-
             Lookup key. Treated as an opaque string by the cache — case-sensitive, no
             normalization. The same cache can hold multiple entries that differ only in
@@ -997,19 +1001,31 @@ components:
             - ext-customer-12345
         value:
           description: |-
-            Value associated with the key. May be a string or an object; nested arrays
-            inside an object are fine. Top-level arrays are rejected — wrap them.
-            Consumers should check the runtime type before use.
+            Value associated with the key. Nested arrays inside an object are fine; a
+            top-level array is rejected — wrap it. Consumers should check the runtime type
+            before use.
           oneOf:
+            - title: Null value
+              type: 'null'
+            - title: Number value
+              type: number
+            - title: Boolean value
+              type: boolean
             - title: String value
               type: string
             - title: Object value
               type: object
               additionalProperties: true
           examples:
+            - null
+            - 42
+            - true
             - California
             - customerId: 0015g00000abc
             - ts: '2026-04-22T00:00:00Z'
+      required:
+        - key
+        - value
     LookupCacheDataUpsertRequest:
       type: object
       description: |-

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.96",
+  "version": "0.2.98",
   "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": "545ed6c7",
+		"iasCommit": "4fcf1e98",
 		"generatedAt": "2026-10-12"
 	},
 	"roots": {