@celigo/api-specs 0.2.118 → 0.2.120

package/dist/api.yml

@@ -5503,7 +5503,7 @@ components:
             OAuth access token for Salesforce API calls (encrypted at rest; returned masked as
             `"******"`). Auto-managed by the system during the OAuth flow; rarely set manually.
           examples:
-            - 00D4P000000zT1P!ARsAQ[fake-access-token]
+            - <org-id>!<session-token>
           x-celigo-ai-guidance:
             - |-
               OAuth access/bearer token (encrypted at rest).
@@ -5642,12 +5642,12 @@ components:
           description: |-
             SSH private key for SFTP key-based authentication (encrypted at rest; returned masked as `"******"`).
             Only used when type is "sftp"; can be used alone or alongside a password. Must be an RSA (SSH-2) key
-            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (first line
-            `-----BEGIN OPENSSH PRIVATE KEY-----`), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
+            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (a first
+            line that names an OPENSSH PRIVATE KEY), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
             are not supported and must be converted to an unencrypted PEM key first.
           x-celigo-ai-guidance:
             - Never take the key through chat; write a placeholder the user replaces in the connection editor. The matching public key must be in the server's authorized_keys for the username — Celigo holds only the private half.
-            - A key whose first line is `-----BEGIN OPENSSH PRIVATE KEY-----`, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
+            - A key whose first line names an OPENSSH PRIVATE KEY, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
           writeOnly: true
         usePassiveMode:
           type: boolean
@@ -5824,7 +5824,7 @@ components:
             AWS access key ID for IAM authentication. From an IAM user or role with S3 permissions
             (s3:GetObject, s3:PutObject, s3:ListBucket, etc.). Used when authType is `accesskey`.
           examples:
-            - AKIAIOSFODNN7EXAMPLE
+            - AKIA_EXAMPLE_KEY_ID
           x-celigo-ui-override: The connection form marks accessKeyId required when Auth type is "Access key & secret" (`accesskey`) and removes it when Auth type is "IAM role" (`awsIam`). The API enforces it for authType `accesskey` (POST without it returns 422 missing_required_field) — encoded via the if/then/else rule below.
         secretAccessKey:
           type: string
@@ -6303,7 +6303,7 @@ components:
             Pre-generated static JWT to use instead of building one from payload (encrypted at rest).
             Use only when the API issues a long-lived JWT that does not need regeneration.
           examples:
-            - eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdmMifQ.EXAMPLEsignature
+            - eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.EXAMPLEpayload.EXAMPLEsignature
           x-celigo-ai-guidance:
             - |-
               Pre-generated JWT token value (encrypted at rest).
@@ -6795,7 +6795,7 @@ components:
                     The API key or bearer token value (encrypted at rest); returned masked as `"******"`.
                     Required unless automatic token refresh is configured.
                   examples:
-                    - sk_live_abc123EXAMPLE456token
+                    - my-api-token-EXAMPLE
                 location:
                   type: string
                   enum:
@@ -7876,7 +7876,7 @@ components:
                   type: string
                   description: AWS access key ID for IAM authentication.
                   examples:
-                    - AKIAIOSFODNN7EXAMPLE
+                    - AKIA_EXAMPLE_KEY_ID
                 secretAccessKey:
                   type: string
                   description: AWS secret access key (encrypted at rest).
@@ -8999,7 +8999,7 @@ components:
             The API key or bearer token value (encrypted at rest); returned masked as `"******"`.
             Required unless automatic token refresh is configured.
           examples:
-            - sk_live_abc123EXAMPLE456token
+            - my-api-token-EXAMPLE
         location:
           type: string
           enum:
@@ -9408,7 +9408,7 @@ components:
               type: string
               description: Access key ID of the IAM user or role whose policy grants the required DynamoDB actions.
               examples:
-                - AKIAIOSFODNN7EXAMPLE
+                - AKIA_EXAMPLE_KEY_ID
             secretAccessKey:
               type: string
               description: Secret access key paired with `accessKeyId`. Encrypted at rest and returned masked as `"******"`.

package/dist/connection.yml

@@ -4614,7 +4614,7 @@ components:
             OAuth access token for Salesforce API calls (encrypted at rest; returned masked as
             `"******"`). Auto-managed by the system during the OAuth flow; rarely set manually.
           examples:
-            - 00D4P000000zT1P!ARsAQ[fake-access-token]
+            - <org-id>!<session-token>
           x-celigo-ai-guidance:
             - |-
               OAuth access/bearer token (encrypted at rest).
@@ -4753,12 +4753,12 @@ components:
           description: |-
             SSH private key for SFTP key-based authentication (encrypted at rest; returned masked as `"******"`).
             Only used when type is "sftp"; can be used alone or alongside a password. Must be an RSA (SSH-2) key
-            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (first line
-            `-----BEGIN OPENSSH PRIVATE KEY-----`), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
+            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (a first
+            line that names an OPENSSH PRIVATE KEY), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
             are not supported and must be converted to an unencrypted PEM key first.
           x-celigo-ai-guidance:
             - Never take the key through chat; write a placeholder the user replaces in the connection editor. The matching public key must be in the server's authorized_keys for the username — Celigo holds only the private half.
-            - A key whose first line is `-----BEGIN OPENSSH PRIVATE KEY-----`, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
+            - A key whose first line names an OPENSSH PRIVATE KEY, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
           writeOnly: true
         usePassiveMode:
           type: boolean
@@ -4935,7 +4935,7 @@ components:
             AWS access key ID for IAM authentication. From an IAM user or role with S3 permissions
             (s3:GetObject, s3:PutObject, s3:ListBucket, etc.). Used when authType is `accesskey`.
           examples:
-            - AKIAIOSFODNN7EXAMPLE
+            - AKIA_EXAMPLE_KEY_ID
           x-celigo-ui-override: The connection form marks accessKeyId required when Auth type is "Access key & secret" (`accesskey`) and removes it when Auth type is "IAM role" (`awsIam`). The API enforces it for authType `accesskey` (POST without it returns 422 missing_required_field) — encoded via the if/then/else rule below.
         secretAccessKey:
           type: string
@@ -5414,7 +5414,7 @@ components:
             Pre-generated static JWT to use instead of building one from payload (encrypted at rest).
             Use only when the API issues a long-lived JWT that does not need regeneration.
           examples:
-            - eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdmMifQ.EXAMPLEsignature
+            - eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.EXAMPLEpayload.EXAMPLEsignature
           x-celigo-ai-guidance:
             - |-
               Pre-generated JWT token value (encrypted at rest).
@@ -5906,7 +5906,7 @@ components:
                     The API key or bearer token value (encrypted at rest); returned masked as `"******"`.
                     Required unless automatic token refresh is configured.
                   examples:
-                    - sk_live_abc123EXAMPLE456token
+                    - my-api-token-EXAMPLE
                 location:
                   type: string
                   enum:
@@ -6987,7 +6987,7 @@ components:
                   type: string
                   description: AWS access key ID for IAM authentication.
                   examples:
-                    - AKIAIOSFODNN7EXAMPLE
+                    - AKIA_EXAMPLE_KEY_ID
                 secretAccessKey:
                   type: string
                   description: AWS secret access key (encrypted at rest).
@@ -8110,7 +8110,7 @@ components:
             The API key or bearer token value (encrypted at rest); returned masked as `"******"`.
             Required unless automatic token refresh is configured.
           examples:
-            - sk_live_abc123EXAMPLE456token
+            - my-api-token-EXAMPLE
         location:
           type: string
           enum:
@@ -8519,7 +8519,7 @@ components:
               type: string
               description: Access key ID of the IAM user or role whose policy grants the required DynamoDB actions.
               examples:
-                - AKIAIOSFODNN7EXAMPLE
+                - AKIA_EXAMPLE_KEY_ID
             secretAccessKey:
               type: string
               description: Secret access key paired with `accessKeyId`. Encrypted at rest and returned masked as `"******"`.

package/dist/enduser.yml

@@ -2715,7 +2715,7 @@ components:
             OAuth access token for Salesforce API calls (encrypted at rest; returned masked as
             `"******"`). Auto-managed by the system during the OAuth flow; rarely set manually.
           examples:
-            - 00D4P000000zT1P!ARsAQ[fake-access-token]
+            - <org-id>!<session-token>
           x-celigo-ai-guidance:
             - |-
               OAuth access/bearer token (encrypted at rest).
@@ -2854,12 +2854,12 @@ components:
           description: |-
             SSH private key for SFTP key-based authentication (encrypted at rest; returned masked as `"******"`).
             Only used when type is "sftp"; can be used alone or alongside a password. Must be an RSA (SSH-2) key
-            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (first line
-            `-----BEGIN OPENSSH PRIVATE KEY-----`), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
+            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (a first
+            line that names an OPENSSH PRIVATE KEY), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
             are not supported and must be converted to an unencrypted PEM key first.
           x-celigo-ai-guidance:
             - Never take the key through chat; write a placeholder the user replaces in the connection editor. The matching public key must be in the server's authorized_keys for the username — Celigo holds only the private half.
-            - A key whose first line is `-----BEGIN OPENSSH PRIVATE KEY-----`, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
+            - A key whose first line names an OPENSSH PRIVATE KEY, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
           writeOnly: true
         usePassiveMode:
           type: boolean
@@ -3036,7 +3036,7 @@ components:
             AWS access key ID for IAM authentication. From an IAM user or role with S3 permissions
             (s3:GetObject, s3:PutObject, s3:ListBucket, etc.). Used when authType is `accesskey`.
           examples:
-            - AKIAIOSFODNN7EXAMPLE
+            - AKIA_EXAMPLE_KEY_ID
           x-celigo-ui-override: The connection form marks accessKeyId required when Auth type is "Access key & secret" (`accesskey`) and removes it when Auth type is "IAM role" (`awsIam`). The API enforces it for authType `accesskey` (POST without it returns 422 missing_required_field) — encoded via the if/then/else rule below.
         secretAccessKey:
           type: string
@@ -3515,7 +3515,7 @@ components:
             Pre-generated static JWT to use instead of building one from payload (encrypted at rest).
             Use only when the API issues a long-lived JWT that does not need regeneration.
           examples:
-            - eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdmMifQ.EXAMPLEsignature
+            - eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.EXAMPLEpayload.EXAMPLEsignature
           x-celigo-ai-guidance:
             - |-
               Pre-generated JWT token value (encrypted at rest).
@@ -4007,7 +4007,7 @@ components:
                     The API key or bearer token value (encrypted at rest); returned masked as `"******"`.
                     Required unless automatic token refresh is configured.
                   examples:
-                    - sk_live_abc123EXAMPLE456token
+                    - my-api-token-EXAMPLE
                 location:
                   type: string
                   enum:
@@ -5088,7 +5088,7 @@ components:
                   type: string
                   description: AWS access key ID for IAM authentication.
                   examples:
-                    - AKIAIOSFODNN7EXAMPLE
+                    - AKIA_EXAMPLE_KEY_ID
                 secretAccessKey:
                   type: string
                   description: AWS secret access key (encrypted at rest).
@@ -6211,7 +6211,7 @@ components:
             The API key or bearer token value (encrypted at rest); returned masked as `"******"`.
             Required unless automatic token refresh is configured.
           examples:
-            - sk_live_abc123EXAMPLE456token
+            - my-api-token-EXAMPLE
         location:
           type: string
           enum:
@@ -6620,7 +6620,7 @@ components:
               type: string
               description: Access key ID of the IAM user or role whose policy grants the required DynamoDB actions.
               examples:
-                - AKIAIOSFODNN7EXAMPLE
+                - AKIA_EXAMPLE_KEY_ID
             secretAccessKey:
               type: string
               description: Secret access key paired with `accessKeyId`. Encrypted at rest and returned masked as `"******"`.

package/dist/export.yml

@@ -1714,11 +1714,11 @@ components:
               ### Common implementations
 
               ```
-              "token": "3a7c4f8b2e9d1a5c6b3e7d9fEXAMPLE"
+              "token": "<32+ random characters>"
               ```
 
               ```
-              "token": "whsec_8fb2e91a5c6b3e7dEXAMPLE"
+              "token": "whsec_<signing secret from the sending system>"
               ```
 
               IMPORTANT: Never share this token in public repositories or documentation.
@@ -1975,11 +1975,11 @@ components:
               For tokens embedded in JSON payloads:
 
               ```
-              "path": "meta.token"        // For { "meta": { "token": "xyz123" } }
+              "path": "meta.token"        // For { "meta": { "token": "<token>" } }
               ```
 
               ```
-              "path": "verification.key"  // For { "verification": { "key": "xyz123" } }
+              "path": "verification.key"  // For { "verification": { "key": "<token>" } }
               ```
 
               ### Token at root level
@@ -1987,7 +1987,7 @@ components:
               For tokens in the top level of the request:
 
               ```
-              "path": "token"             // For { "token": "xyz123", "data": {...} }
+              "path": "token"             // For { "token": "<token>", "data": {...} }
               ```
 
               ### Token in query parameters
@@ -1995,7 +1995,7 @@ components:
               For tokens sent as URL query parameters, use the parameter name:
 
               ```
-              "path": "verify_token"      // For /webhook?verify_token=xyz123
+              "path": "verify_token"      // For /webhook?verify_token=<token>
               ```
             - |-
               ## VERIFICATION PROCESS
@@ -5806,7 +5806,7 @@ components:
             - eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
             - sk-1234567890abcdef
       examples:
-        - bearerToken: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
+        - bearerToken: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.EXAMPLEpayload.EXAMPLEsignature
     Cdc:
       type: object
       description: |-
@@ -6888,7 +6888,7 @@ components:
                     "method": "token",
                     "path": "meta.nextToken",
                     "pathLocation": "body",
-                    "token": "eyJwYWdlIjozfQ=="
+                    "token": "<next-page-token>"
                   }
 
                   // For APIs requiring an initial token:
@@ -6931,7 +6931,7 @@ components:
 
                       Example header:
                       ```
-                      X-Pagination-Token: abc123
+                      X-Pagination-Token: <next-page-token>
                       ```
                       Correct path: "X-Pagination-Token"
 

package/dist/iclient.yml

@@ -98,7 +98,7 @@ paths:
                       enableIClientReferences: false
                       formType: assistant
                       oauth2:
-                        clientId: 1096775564568-cucr5sv44tgfec4kkqsufi5k975d8orv.apps.googleusercontent.com
+                        clientId: 123456789012-EXAMPLE.apps.googleusercontent.com
                         clientSecret: '******'
                         scope: []
                         scopeDelimiter: ' '
@@ -299,7 +299,7 @@ paths:
                     enableIClientReferences: false
                     formType: assistant
                     oauth2:
-                      clientId: 1096775564568-cucr5sv44tgfec4kkqsufi5k975d8orv.apps.googleusercontent.com
+                      clientId: 123456789012-EXAMPLE.apps.googleusercontent.com
                       clientSecret: '******'
                       scope: []
                       scopeDelimiter: ' '
@@ -1156,7 +1156,7 @@ components:
                   It is a public value that is included in authorization requests and token
                   exchanges to associate the requests with the registered client.
               examples:
-                - 1096775564568-cucr5sv44tgfec4kkqsufi5k975d8orv.apps.googleusercontent.com
+                - 123456789012-EXAMPLE.apps.googleusercontent.com
                 - abc123xyz
                 - myapp-client-001
                 - 1234567890abcdef
@@ -2326,8 +2326,7 @@ components:
                 - |-
                   ## EXAMPLES:
                   - "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
-                  - "2YotnFZFEjr1zCsicMWpAA"
-                  - "mF_9.B5f-4.1JqM"
+                  - An opaque string, such as the sample access token in RFC 6749
                 - |-
                   ## IMPLEMENTATION GUIDANCE:
                   - Ensure the token is included in the Authorization header as "Bearer {token}".
@@ -2699,8 +2698,8 @@ components:
                       commonly application/x-www-form-urlencoded.
                     - |-
                       ## EXAMPLES:
-                      - grant_type=refresh_token&refresh_token=xyz123&client_id=abc&client_secret=secret
-                      - grant_type=refresh_token&refresh_token=def456
+                      - grant_type=refresh_token&refresh_token=REFRESH_TOKEN&client_id=CLIENT_ID&client_secret=CLIENT_SECRET
+                      - grant_type=refresh_token&refresh_token={{{iClient.oauth2.refreshToken}}}
                     - |-
                       ## FIELD BEHAVIOR:
                       - Contains all necessary parameters to request a new access token using a refresh token.
@@ -2749,8 +2748,7 @@ components:
                       commonly application/x-www-form-urlencoded.
                   examples:
                     - grant_type=refresh_token&refresh_token={{{iClient.oauth2.refreshToken}}}
-                    - grant_type=refresh_token&refresh_token=xyz123&client_id=abc&client_secret=secret
-                    - grant_type=refresh_token&refresh_token=def456
+                    - grant_type=refresh_token&refresh_token=REFRESH_TOKEN&client_id=CLIENT_ID&client_secret=CLIENT_SECRET
                 headers:
                   description: |-
                     Custom HTTP headers for the refresh token request.
@@ -2927,9 +2925,9 @@ components:
                       - Conforms to RFC 7009 (OAuth 2.0 Token Revocation)
                     - |-
                       ## EXAMPLES:
-                      - token=SlAV32hkKG
-                      - token=34xkj23j4k23&token_type_hint=refresh_token
-                      - token=abcdef123456&token_type_hint=access_token
+                      - token={{{iClient.oauth2.accessToken}}}
+                      - token={{{iClient.oauth2.refreshToken}}}&token_type_hint=refresh_token
+                      - token=ACCESS_TOKEN&token_type_hint=access_token
                     - |-
                       ## FIELD BEHAVIOR:
                       - Contains key-value pairs representing the token and optional token type hint.
@@ -2957,9 +2955,8 @@ components:
                       MIME type as per the OAuth 2.0 Token Revocation specification (RFC 7009).
                   examples:
                     - token={{{iClient.oauth2.accessToken}}}
-                    - token=SlAV32hkKG
-                    - token=34xkj23j4k23&token_type_hint=refresh_token
-                    - token=abcdef123456&token_type_hint=access_token
+                    - token={{{iClient.oauth2.refreshToken}}}&token_type_hint=refresh_token
+                    - token=ACCESS_TOKEN&token_type_hint=access_token
                 headers:
                   description: |-
                     Custom HTTP headers for the revocation request.
@@ -3072,8 +3069,8 @@ components:
               x-celigo-ai-guidance:
                 - |-
                   ## EXAMPLES:
-                  - `{"password":"my-password-EXAMPLE"}`
-                  - `{"token":"x7if4nkovhgr63ghp"}`
+                  - `{"password":"<password>"}`
+                  - `{"token":"<api-token>"}`
                 - |-
                   ## IMPORTANT NOTES:
                   - Use this for secrets (passwords, tokens, keys).
@@ -3297,8 +3294,7 @@ components:
                   of the client application.
                 - |-
                   ## EXAMPLES:
-                  - "3MVG9d6T2QxX9z5l7Y8P0qR1sT2uVwXyZAbCdEfGhIjKlMnOpQrStUvWxYz123456"
-                  - "1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"
+                  - "3MVG9-EXAMPLE-consumer-key"
                 - |-
                   ## IMPORTANT NOTES:
                   - The clientId alone does not grant access; it must be paired with appropriate credentials and tokens.
@@ -3330,9 +3326,7 @@ components:
                   It is essential for enabling authorized access to Salesforce resources on behalf
                   of the client application.
               examples:
-                - 3MVG9pRzvMkjMb6kkUMc3nVfDlF1H9V8sV0kZ8wQ7nC2x
-                - 3MVG9d6T2QxX9z5l7Y8P0qR1sT2uVwXyZAbCdEfGhIjKlMnOpQrStUvWxYz123456
-                - 1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
+                - 3MVG9-EXAMPLE-consumer-key
             clientSecret:
               type: string
               description: |-
@@ -3380,7 +3374,7 @@ components:
                   - Different Salesforce environments (sandbox vs production) may require different tokens.
                 - |-
                   ## EXAMPLES:
-                  - A long alphanumeric string like "00Dxx0000001gPFEAY!AQ0AQJ..."
+                  - A long string that starts with the org ID, an exclamation mark, and then the session token
                   - OAuth access tokens obtained via Salesforce OAuth 2.0 flows.
                   - Tokens generated from Salesforce connected apps for API access.
                 - |-
@@ -3789,10 +3783,10 @@ components:
               authorization, and interaction with various Amazon MWS endpoints.
             - |-
               ## EXAMPLES:
-              - Access Key ID: "AKIAIOSFODNN7EXAMPLE"
-              - Secret Access Key: "1234567890abcdef1234567890abcdef12345678"
-              - Seller ID: "A1XEXAMPLE123"
-              - MWS Auth Token: "amzn.mws.4ea38b7b-f563-7709-4bae-87aeaEXAMPLE"
+              - Access Key ID: 20 characters, starting with AKIA
+              - Secret Access Key: 40 characters, shown once when the key is created
+              - Seller ID: the merchant ID from Seller Central, such as A1XEXAMPLE123
+              - MWS Auth Token: a UUID with the amzn.mws. prefix, issued when the seller authorizes the developer
             - |-
               ## FIELD BEHAVIOR:
               - Contains all necessary authentication credentials such as Access Key ID, Secret Access Key, Seller ID, and MWS Auth Token.
@@ -3847,9 +3841,7 @@ components:
                   - Used alongside other credentials such as Seller ID and MWS Auth Token for full API access.
                 - |-
                   ## EXAMPLES:
-                  - "AKIAIOSFODNN7EXAMPLE"
-                  - "ABCD1234EFGH5678IJKL"
-                  - "A1B2C3D4E5F6G7H8I9J0"
+                  - "AKIA_EXAMPLE_KEY_ID"
                 - |-
                   ## IMPORTANT NOTES:
                   - The Access Key ID alone is insufficient for authentication; it must be paired with the Secret Access Key.
@@ -3896,9 +3888,7 @@ components:
                   enabling operations such as order retrieval, inventory management,
                   and report generation.
               examples:
-                - AKIAIOSFODNN7EXAMPLE
-                - ABCD1234EFGH5678IJKL
-                - A1B2C3D4E5F6G7H8I9J0
+                - AKIA_EXAMPLE_KEY_ID
             secretKey:
               type: string
               description: |-
@@ -3997,9 +3987,9 @@ components:
                   if it is unencrypted, sending certificatePassword is rejected.
                 - |-
                   The save does not check that the PEM is a usable credential — a placeholder PEM
-                  carrying the BEGIN CERTIFICATE and BEGIN PRIVATE KEY blocks saves (live-verified
-                  201). Enter the real PEM in the iClient editor before testing a connection that
-                  uses the iClient.
+                  carrying a certificate block and a private-key block saves (live-verified 201).
+                  Enter the real PEM in the iClient editor before testing a connection that uses
+                  the iClient.
             certificatePassword:
               type: string
               description: |-
@@ -4026,11 +4016,10 @@ components:
               description: |-
                 Google service-account key file, sent as a JSON string. The save
                 reads `project_id`, `client_email`, and a `private_key` that
-                includes its PEM armor (`-----BEGIN PRIVATE KEY-----` through
-                `-----END PRIVATE KEY-----`). Missing, empty, or incomplete JSON
-                fails with 422 `invalid_json_key`. Send the full key on every
-                create and every update — omitting it or sending `"******"`
-                fails the same way.
+                includes its PEM armor (its BEGIN and END PRIVATE KEY lines).
+                Missing, empty, or incomplete JSON fails with 422
+                `invalid_json_key`. Send the full key on every create and every
+                update — omitting it or sending `"******"` fails the same way.
               x-celigo-ai-guidance:
                 - |-
                   A placeholder body inside the PEM armor is accepted on create.
@@ -4135,8 +4124,8 @@ components:
               - Be aware of token expiration and implement proper handling for expired tokens.
             - |-
               ## EXAMPLES:
-              - eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
-              - eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJpc3MiOiJleGFtcGxlLmNvbSIsInN1YiI6IjEyMzQ1Njc4OTAiLCJleHAiOjE2MjQ2MjQwMDB9.EXAMPLEsignature
+              - eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.EXAMPLEpayload.EXAMPLEsignature
+              - eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.EXAMPLEpayload.EXAMPLEsignature
             - |-
               ## DEPENDENCY CHAIN:
               - Depends on the authentication mechanism generating the JWT.

package/dist/mcp-server.yml

@@ -4540,7 +4540,7 @@ components:
             OAuth access token for Salesforce API calls (encrypted at rest; returned masked as
             `"******"`). Auto-managed by the system during the OAuth flow; rarely set manually.
           examples:
-            - 00D4P000000zT1P!ARsAQ[fake-access-token]
+            - <org-id>!<session-token>
           x-celigo-ai-guidance:
             - |-
               OAuth access/bearer token (encrypted at rest).
@@ -4679,12 +4679,12 @@ components:
           description: |-
             SSH private key for SFTP key-based authentication (encrypted at rest; returned masked as `"******"`).
             Only used when type is "sftp"; can be used alone or alongside a password. Must be an RSA (SSH-2) key
-            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (first line
-            `-----BEGIN OPENSSH PRIVATE KEY-----`), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
+            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (a first
+            line that names an OPENSSH PRIVATE KEY), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
             are not supported and must be converted to an unencrypted PEM key first.
           x-celigo-ai-guidance:
             - Never take the key through chat; write a placeholder the user replaces in the connection editor. The matching public key must be in the server's authorized_keys for the username — Celigo holds only the private half.
-            - A key whose first line is `-----BEGIN OPENSSH PRIVATE KEY-----`, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
+            - A key whose first line names an OPENSSH PRIVATE KEY, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
           writeOnly: true
         usePassiveMode:
           type: boolean
@@ -4861,7 +4861,7 @@ components:
             AWS access key ID for IAM authentication. From an IAM user or role with S3 permissions
             (s3:GetObject, s3:PutObject, s3:ListBucket, etc.). Used when authType is `accesskey`.
           examples:
-            - AKIAIOSFODNN7EXAMPLE
+            - AKIA_EXAMPLE_KEY_ID
           x-celigo-ui-override: The connection form marks accessKeyId required when Auth type is "Access key & secret" (`accesskey`) and removes it when Auth type is "IAM role" (`awsIam`). The API enforces it for authType `accesskey` (POST without it returns 422 missing_required_field) — encoded via the if/then/else rule below.
         secretAccessKey:
           type: string
@@ -5340,7 +5340,7 @@ components:
             Pre-generated static JWT to use instead of building one from payload (encrypted at rest).
             Use only when the API issues a long-lived JWT that does not need regeneration.
           examples:
-            - eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdmMifQ.EXAMPLEsignature
+            - eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.EXAMPLEpayload.EXAMPLEsignature
           x-celigo-ai-guidance:
             - |-
               Pre-generated JWT token value (encrypted at rest).
@@ -5832,7 +5832,7 @@ components:
                     The API key or bearer token value (encrypted at rest); returned masked as `"******"`.
                     Required unless automatic token refresh is configured.
                   examples:
-                    - sk_live_abc123EXAMPLE456token
+                    - my-api-token-EXAMPLE
                 location:
                   type: string
                   enum:
@@ -6913,7 +6913,7 @@ components:
                   type: string
                   description: AWS access key ID for IAM authentication.
                   examples:
-                    - AKIAIOSFODNN7EXAMPLE
+                    - AKIA_EXAMPLE_KEY_ID
                 secretAccessKey:
                   type: string
                   description: AWS secret access key (encrypted at rest).
@@ -8036,7 +8036,7 @@ components:
             The API key or bearer token value (encrypted at rest); returned masked as `"******"`.
             Required unless automatic token refresh is configured.
           examples:
-            - sk_live_abc123EXAMPLE456token
+            - my-api-token-EXAMPLE
         location:
           type: string
           enum:
@@ -8445,7 +8445,7 @@ components:
               type: string
               description: Access key ID of the IAM user or role whose policy grants the required DynamoDB actions.
               examples:
-                - AKIAIOSFODNN7EXAMPLE
+                - AKIA_EXAMPLE_KEY_ID
             secretAccessKey:
               type: string
               description: Secret access key paired with `accessKeyId`. Encrypted at rest and returned masked as `"******"`.

package/dist/tool.yml

@@ -7869,7 +7869,7 @@ components:
             OAuth access token for Salesforce API calls (encrypted at rest; returned masked as
             `"******"`). Auto-managed by the system during the OAuth flow; rarely set manually.
           examples:
-            - 00D4P000000zT1P!ARsAQ[fake-access-token]
+            - <org-id>!<session-token>
           x-celigo-ai-guidance:
             - |-
               OAuth access/bearer token (encrypted at rest).
@@ -8008,12 +8008,12 @@ components:
           description: |-
             SSH private key for SFTP key-based authentication (encrypted at rest; returned masked as `"******"`).
             Only used when type is "sftp"; can be used alone or alongside a password. Must be an RSA (SSH-2) key
-            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (first line
-            `-----BEGIN OPENSSH PRIVATE KEY-----`), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
+            in PEM format, supplied whole from its BEGIN line to its END line — OpenSSH-format keys (a first
+            line that names an OPENSSH PRIVATE KEY), passphrase-protected keys, SSH-1 keys and PuTTY `.ppk` files
             are not supported and must be converted to an unencrypted PEM key first.
           x-celigo-ai-guidance:
             - Never take the key through chat; write a placeholder the user replaces in the connection editor. The matching public key must be in the server's authorized_keys for the username — Celigo holds only the private half.
-            - A key whose first line is `-----BEGIN OPENSSH PRIVATE KEY-----`, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
+            - A key whose first line names an OPENSSH PRIVATE KEY, or one that asks for a passphrase, is outside the supported format per the Help Center; `ssh-keygen -p -m PEM -f <key>` rewrites it as PEM (`-N ""` also removes the passphrase).
           writeOnly: true
         usePassiveMode:
           type: boolean
@@ -8190,7 +8190,7 @@ components:
             AWS access key ID for IAM authentication. From an IAM user or role with S3 permissions
             (s3:GetObject, s3:PutObject, s3:ListBucket, etc.). Used when authType is `accesskey`.
           examples:
-            - AKIAIOSFODNN7EXAMPLE
+            - AKIA_EXAMPLE_KEY_ID
           x-celigo-ui-override: The connection form marks accessKeyId required when Auth type is "Access key & secret" (`accesskey`) and removes it when Auth type is "IAM role" (`awsIam`). The API enforces it for authType `accesskey` (POST without it returns 422 missing_required_field) — encoded via the if/then/else rule below.
         secretAccessKey:
           type: string
@@ -8669,7 +8669,7 @@ components:
             Pre-generated static JWT to use instead of building one from payload (encrypted at rest).
             Use only when the API issues a long-lived JWT that does not need regeneration.
           examples:
-            - eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdmMifQ.EXAMPLEsignature
+            - eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.EXAMPLEpayload.EXAMPLEsignature
           x-celigo-ai-guidance:
             - |-
               Pre-generated JWT token value (encrypted at rest).
@@ -9161,7 +9161,7 @@ components:
                     The API key or bearer token value (encrypted at rest); returned masked as `"******"`.
                     Required unless automatic token refresh is configured.
                   examples:
-                    - sk_live_abc123EXAMPLE456token
+                    - my-api-token-EXAMPLE
                 location:
                   type: string
                   enum:
@@ -10242,7 +10242,7 @@ components:
                   type: string
                   description: AWS access key ID for IAM authentication.
                   examples:
-                    - AKIAIOSFODNN7EXAMPLE
+                    - AKIA_EXAMPLE_KEY_ID
                 secretAccessKey:
                   type: string
                   description: AWS secret access key (encrypted at rest).
@@ -11365,7 +11365,7 @@ components:
             The API key or bearer token value (encrypted at rest); returned masked as `"******"`.
             Required unless automatic token refresh is configured.
           examples:
-            - sk_live_abc123EXAMPLE456token
+            - my-api-token-EXAMPLE
         location:
           type: string
           enum:
@@ -11774,7 +11774,7 @@ components:
               type: string
               description: Access key ID of the IAM user or role whose policy grants the required DynamoDB actions.
               examples:
-                - AKIAIOSFODNN7EXAMPLE
+                - AKIA_EXAMPLE_KEY_ID
             secretAccessKey:
               type: string
               description: Secret access key paired with `accessKeyId`. Encrypted at rest and returned masked as `"******"`.
@@ -26365,11 +26365,11 @@ components:
               ### Common implementations
 
               ```
-              "token": "3a7c4f8b2e9d1a5c6b3e7d9fEXAMPLE"
+              "token": "<32+ random characters>"
               ```
 
               ```
-              "token": "whsec_8fb2e91a5c6b3e7dEXAMPLE"
+              "token": "whsec_<signing secret from the sending system>"
               ```
 
               IMPORTANT: Never share this token in public repositories or documentation.
@@ -26626,11 +26626,11 @@ components:
               For tokens embedded in JSON payloads:
 
               ```
-              "path": "meta.token"        // For { "meta": { "token": "xyz123" } }
+              "path": "meta.token"        // For { "meta": { "token": "<token>" } }
               ```
 
               ```
-              "path": "verification.key"  // For { "verification": { "key": "xyz123" } }
+              "path": "verification.key"  // For { "verification": { "key": "<token>" } }
               ```
 
               ### Token at root level
@@ -26638,7 +26638,7 @@ components:
               For tokens in the top level of the request:
 
               ```
-              "path": "token"             // For { "token": "xyz123", "data": {...} }
+              "path": "token"             // For { "token": "<token>", "data": {...} }
               ```
 
               ### Token in query parameters
@@ -26646,7 +26646,7 @@ components:
               For tokens sent as URL query parameters, use the parameter name:
 
               ```
-              "path": "verify_token"      // For /webhook?verify_token=xyz123
+              "path": "verify_token"      // For /webhook?verify_token=<token>
               ```
             - |-
               ## VERIFICATION PROCESS
@@ -30040,7 +30040,7 @@ components:
             - eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
             - sk-1234567890abcdef
       examples:
-        - bearerToken: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
+        - bearerToken: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.EXAMPLEpayload.EXAMPLEsignature
     Cdc:
       type: object
       description: |-
@@ -31122,7 +31122,7 @@ components:
                     "method": "token",
                     "path": "meta.nextToken",
                     "pathLocation": "body",
-                    "token": "eyJwYWdlIjozfQ=="
+                    "token": "<next-page-token>"
                   }
 
                   // For APIs requiring an initial token:
@@ -31165,7 +31165,7 @@ components:
 
                       Example header:
                       ```
-                      X-Pagination-Token: abc123
+                      X-Pagination-Token: <next-page-token>
                       ```
                       Correct path: "X-Pagination-Token"
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.118",
+  "version": "0.2.120",
   "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": "289007c3",
-		"generatedAt": "2026-10-16"
+		"iasCommit": "a82ea4f6",
+		"generatedAt": "2026-10-17"
 	},
 	"roots": {
 		"aiagent": 133,