@celigo/api-specs 0.2.17 → 0.2.19

package/dist/iclient.yml

@@ -1744,73 +1744,36 @@ components:
               items:
                 type: string
               description: |-
-                Domain names used to validate OAuth URLs. Provide each
-                unique domain once (no scheme, no path).
+                Registrable domains (`domain.com`, `domain.co.uk` — the host with its
+                subdomains removed) of the OAuth URLs this client's credentials are
+                sent to: the access token, authorization, and revoke URLs. Before an
+                OAuth request leaves integrator.io, the target URL's registrable
+                domain must appear here; a full hostname never matches.
               examples:
                 - - domain.com
                 - - domain.com
                   - domain1.com
                   - domain2.com
+                - - microsoftonline.com
+                  - microsoft.com
               x-celigo-ai-guidance:
                 - |-
-                  Set this to the list of unique domain names used to validate the OAuth URLs (Authorization,
-                  Access Token, Revoke Token).
-                  In the UI, enter each unique domain name as comma-separated values;
-                  if the same domain is used for each URL, provide it only once.
-                  For multiple domains, set this to `["domain.com", "domain1.com",
-                  "domain2.com"]`; if all URLs share the same domain (e.g.
-                  `domain.com`), set this to `["domain.com"]`.
-                - |-
-                  Example: if your URLs are:
-                  - `https://<AccessTokenURL>.domain.com`
-                  - `https://<RevokeTokenURL>.domain1.com`
-                  - `https://<AuthorizationURL>.domain2.com`
-
-                  then set `validDomainNames` to: `["domain.com", "domain1.com", "domain2.com"]`.
-                - |-
-                  ## TECHNICAL DETAILS:
-                  - Stored as an array of strings.
-                - |-
-                  ## FIELD BEHAVIOR:
-                  - Array of domain names (no scheme, no path).
-                  - Used to validate the OAuth URL domains (authorization/token/revoke).
-                  - Provide each unique domain once.
-                - |-
-                  ## DEPENDENCY CHAIN:
-                  - Used alongside `oauth2.auth.uri`, `oauth2.token.uri`, and `oauth2.revoke.uri`.
-                - |-
-                  ## IMPLEMENTATION GUIDANCE:
-                  - Extract the domain portion from each OAuth URL and include it here.
-                  - Do not include `https://` or any URL path/query—only the domain.
-                  - Keep this list in sync if any OAuth URLs change.
-                - |-
-                  ## EXAMPLES:
-                  - ["domain.com"]
-                  - ["domain.com", "domain1.com", "domain2.com"]
-                - |-
-                  ## IMPORTANT NOTES:
-                  - This is about **domains** for OAuth URLs, not full URLs.
-                - |-
-                  Example: if your URLs are:
-                  - `https://<AccessTokenURL>.domain.com`
-                  - `https://<RevokeTokenURL>.domain1.com`
-                  - `https://<AuthorizationURL>.domain2.com`
-                - |-
-                  Set this to the list of unique domain names used to validate the OAuth URLs (Authorization,
-                  Access Token, Revoke Token).
-                  In the UI, enter each unique domain name as comma-separated values;
-                  if the same domain is used for each URL, provide it only once.
-                  For multiple domains, set this to `["domain.com", "domain1.com",
-                  "domain2.com"]`; if all URLs share the same domain (e.g.
-                  `domain.com`), set this to `["domain.com"]`.
-                - |-
-                  Set this to the list of unique domain names used to validate the OAuth URLs (Authorization,
-                  Access Token, Revoke Token).
-                  In the UI, enter each unique domain name as comma-separated values;
-                  if the same domain is used for each URL, provide it only once.
-                  For multiple domains, set this to `["domain.com", "domain1.com",
-                  "domain2.com"]`; if all URLs share the same domain (e.g.
-                  `domain.com`), set this to `["domain.com"]`.
+                  Store the registrable domain, never the hostname. For the token URL
+                  `https://login.microsoftonline.com/<tenant>/oauth2/v2.0/token` the entry is
+                  `microsoftonline.com`; `login.microsoftonline.com` fails the connection test with
+                  `[invalid_domain] The domain of request url should be present in
+                  iClient.oauth2.validDomainNames` and no request is sent. Public suffixes are
+                  honoured: `auth.example.co.uk` → `example.co.uk`, not `co.uk`.
+                - |-
+                  List the registrable domain of every OAuth URL on the client (token, authorization,
+                  revoke) once each — a missing token-URL domain is what blocks the connection.
+                  Celigo's connector setup guides also list the API host's registrable domain next to
+                  them (Microsoft: `microsoftonline.com`, `microsoft.com`); include it to match the
+                  guides — an extra entry is harmless.
+                - |-
+                  When a connection using this client reports `[invalid_domain]`, the fix is this
+                  field — replace hostnames with registrable domains. The connection's base URI and
+                  ping path are where the request goes, not where the allow-list lives.
             failPath:
               type: string
               description: |-

package/dist/subscription.yml

@@ -830,12 +830,13 @@ components:
                   example: 4000
         logging:
           type: object
-          description: Execution logging plan entitlements.
+          description: |-
+            Execution logging plan entitlements. A plan that does not entitle execution
+            logging carries only `enabled: false`; the cap fields appear when the plan
+            defines them. Trial accounts carry the trial's entitlement until `trialEndDate`;
+            an account that does not convert then reads `enabled: false` (or no block).
           required:
             - enabled
-            - maxLogMode
-            - maxDebugDuration
-            - maxRetentionPeriod
           properties:
             enabled:
               type: boolean
@@ -843,21 +844,29 @@ components:
               example: true
             maxLogMode:
               type: string
-              description: Maximum logging detail level the plan allows.
+              description: |-
+                Maximum persistent execution-log mode (`flow.logging.mode`) the plan allows;
+                present when the plan defines this cap. A flow mode above this level is
+                outside the entitlement regardless of the account's Store payloads consent.
+                Time-boxed debug windows (`flow.logging.debugUntil`) are not governed by
+                this cap: they are governed by `enabled`, `maxDebugDuration`, and the
+                account's Store payloads consent.
               example: detailed
               enum:
-                - brief
+                - basic
                 - detailed
               x-enumDescriptions:
-                brief: Summary-level execution logs only.
-                detailed: Full execution logs with request/response data.
+                basic: Summary-level persistent execution logs only (no request/response payloads); debug windows remain available within maxDebugDuration
+                detailed: Full persistent execution logs with request/response payloads
+              x-celigo-ai-guidance:
+                - On a basic-capped plan, a persistent Detailed log mode is outside the entitlement — steer that request to a license upgrade. A time-boxed debug window is within the plan; check `maxDebugDuration` and the account's Store payloads consent for it instead of inferring from this cap.
             maxDebugDuration:
               type: integer
-              description: Maximum time (in minutes) the plan allows a user to enable debug logging for.
+              description: Maximum time (in minutes) the plan allows a user to enable debug logging for. Present when the plan defines this cap.
               example: 4320
             maxRetentionPeriod:
               type: integer
-              description: Maximum execution log retention period (in days) the plan allows.
+              description: Maximum execution log retention period (in days) the plan allows. Present when the plan defines this cap.
               example: 180
         storage:
           type: object

package/package.json

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

package/schemas.json

@@ -1,8 +1,8 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "c3e34bb",
-		"generatedAt": "2026-09-13"
+		"iasCommit": "abe461c",
+		"generatedAt": "2026-09-15"
 	},
 	"roots": {
 		"aiagent": 121,