npm - @celigo/api-specs - Versions diffs - 0.2.179 → 0.2.181 - Mend

@celigo/api-specs 0.2.179 → 0.2.181

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (9) hide show

package/dist/api.yml CHANGED Viewed

@@ -6899,10 +6899,34 @@ components:
             - Amazon-Hybrid
             - vendor_central
           x-enumDescriptions:
-            Amazon-SP-API: Amazon Selling Partner API connection.
-            Amazon-Hybrid: Hybrid Amazon connection supporting both MWS and SP-API.
-            vendor_central: Amazon Vendor Central API connection.
-          description: Specific API type for Amazon integrations. Only set this for Amazon connections.
+            Amazon-SP-API: Amazon Seller Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
+            Amazon-Hybrid: Amazon Seller Central over both the legacy MWS and the Selling Partner API, for integrations not yet fully on SP-API
+            vendor_central: Amazon Vendor Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
+          description: |-
+            Selects which Amazon selling program and API family a prebuilt Amazon connection talks to.
+            Set by the Amazon Seller Central and Amazon Vendor Central connection forms; a custom
+            Selling Partner API integration built on the customer's own developer application is a
+            plain HTTP connection and does not carry this field.
+          x-celigo-ai-guidance:
+            - |-
+              The prebuilt Amazon connection forms collect the API type, selling region and marketplace
+              and save an OAuth 2.0 authorization-code connection (`http.auth.type` `oauth`,
+              `http.auth.oauth.grantType` `authorizecode`, `useIClientFields` false) whose authorization
+              URI is the Seller Central or Vendor Central `/apps/authorize/consent` page — Amazon's
+              public-application consent, granted by the selling partner to Celigo's registered
+              Selling Partner API application. Celigo's Seller Central documentation states the customer
+              need not register as an Amazon developer (article 360060827012); the Vendor Central form
+              carries no developer credentials either.
+            - |-
+              The prebuilt forms collect no Amazon developer application id, client secret, AWS
+              credentials or iClient — the Vendor Central form has no iClient field, and the Seller
+              Central form sets `http._iClientId` only for its legacy `Amazon-MWS` choice — so creating
+              one of these connections asks the customer for a Seller Central or Vendor Central account
+              for the chosen region and marketplace and a user who can complete Amazon's consent screen,
+              nothing more. A customer who must run on their OWN developer registration builds a
+              token-based or OAuth 2.0 universal HTTP connection to the Selling Partner API base URI
+              instead (articles 6204088366363 and the OAuth 2.0 universal connector) and takes on
+              Amazon's developer agreements themselves.
           examples:
             - Amazon-SP-API
         clientCertificates:

package/dist/connection.yml CHANGED Viewed

@@ -5756,10 +5756,34 @@ components:
             - Amazon-Hybrid
             - vendor_central
           x-enumDescriptions:
-            Amazon-SP-API: Amazon Selling Partner API connection.
-            Amazon-Hybrid: Hybrid Amazon connection supporting both MWS and SP-API.
-            vendor_central: Amazon Vendor Central API connection.
-          description: Specific API type for Amazon integrations. Only set this for Amazon connections.
+            Amazon-SP-API: Amazon Seller Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
+            Amazon-Hybrid: Amazon Seller Central over both the legacy MWS and the Selling Partner API, for integrations not yet fully on SP-API
+            vendor_central: Amazon Vendor Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
+          description: |-
+            Selects which Amazon selling program and API family a prebuilt Amazon connection talks to.
+            Set by the Amazon Seller Central and Amazon Vendor Central connection forms; a custom
+            Selling Partner API integration built on the customer's own developer application is a
+            plain HTTP connection and does not carry this field.
+          x-celigo-ai-guidance:
+            - |-
+              The prebuilt Amazon connection forms collect the API type, selling region and marketplace
+              and save an OAuth 2.0 authorization-code connection (`http.auth.type` `oauth`,
+              `http.auth.oauth.grantType` `authorizecode`, `useIClientFields` false) whose authorization
+              URI is the Seller Central or Vendor Central `/apps/authorize/consent` page — Amazon's
+              public-application consent, granted by the selling partner to Celigo's registered
+              Selling Partner API application. Celigo's Seller Central documentation states the customer
+              need not register as an Amazon developer (article 360060827012); the Vendor Central form
+              carries no developer credentials either.
+            - |-
+              The prebuilt forms collect no Amazon developer application id, client secret, AWS
+              credentials or iClient — the Vendor Central form has no iClient field, and the Seller
+              Central form sets `http._iClientId` only for its legacy `Amazon-MWS` choice — so creating
+              one of these connections asks the customer for a Seller Central or Vendor Central account
+              for the chosen region and marketplace and a user who can complete Amazon's consent screen,
+              nothing more. A customer who must run on their OWN developer registration builds a
+              token-based or OAuth 2.0 universal HTTP connection to the Selling Partner API base URI
+              instead (articles 6204088366363 and the OAuth 2.0 universal connector) and takes on
+              Amazon's developer agreements themselves.
           examples:
             - Amazon-SP-API
         clientCertificates:

package/dist/enduser.yml CHANGED Viewed

@@ -3807,10 +3807,34 @@ components:
             - Amazon-Hybrid
             - vendor_central
           x-enumDescriptions:
-            Amazon-SP-API: Amazon Selling Partner API connection.
-            Amazon-Hybrid: Hybrid Amazon connection supporting both MWS and SP-API.
-            vendor_central: Amazon Vendor Central API connection.
-          description: Specific API type for Amazon integrations. Only set this for Amazon connections.
+            Amazon-SP-API: Amazon Seller Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
+            Amazon-Hybrid: Amazon Seller Central over both the legacy MWS and the Selling Partner API, for integrations not yet fully on SP-API
+            vendor_central: Amazon Vendor Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
+          description: |-
+            Selects which Amazon selling program and API family a prebuilt Amazon connection talks to.
+            Set by the Amazon Seller Central and Amazon Vendor Central connection forms; a custom
+            Selling Partner API integration built on the customer's own developer application is a
+            plain HTTP connection and does not carry this field.
+          x-celigo-ai-guidance:
+            - |-
+              The prebuilt Amazon connection forms collect the API type, selling region and marketplace
+              and save an OAuth 2.0 authorization-code connection (`http.auth.type` `oauth`,
+              `http.auth.oauth.grantType` `authorizecode`, `useIClientFields` false) whose authorization
+              URI is the Seller Central or Vendor Central `/apps/authorize/consent` page — Amazon's
+              public-application consent, granted by the selling partner to Celigo's registered
+              Selling Partner API application. Celigo's Seller Central documentation states the customer
+              need not register as an Amazon developer (article 360060827012); the Vendor Central form
+              carries no developer credentials either.
+            - |-
+              The prebuilt forms collect no Amazon developer application id, client secret, AWS
+              credentials or iClient — the Vendor Central form has no iClient field, and the Seller
+              Central form sets `http._iClientId` only for its legacy `Amazon-MWS` choice — so creating
+              one of these connections asks the customer for a Seller Central or Vendor Central account
+              for the chosen region and marketplace and a user who can complete Amazon's consent screen,
+              nothing more. A customer who must run on their OWN developer registration builds a
+              token-based or OAuth 2.0 universal HTTP connection to the Selling Partner API base URI
+              instead (articles 6204088366363 and the OAuth 2.0 universal connector) and takes on
+              Amazon's developer agreements themselves.
           examples:
             - Amazon-SP-API
         clientCertificates:

package/dist/export.yml CHANGED Viewed

@@ -9657,7 +9657,7 @@ components:
             Directory on the server to retrieve files from, either absolute or relative to the login
             directory; the FTP user must have read permission on it. Use forward slashes regardless
             of server OS — paths are case-sensitive on UNIX/Linux servers. Supports handlebars
-            templates, e.g. archive/{{date 'YYYY-MM-DD'}}.
+            templates, e.g. archive/{{timestamp 'YYYY-MM-DD'}}.
           examples:
             - users/dave
             - incoming/orders
@@ -9679,12 +9679,12 @@ components:
               - Can use static text or handlebars templates
               - Examples:
                 - `"ORDER_"` - matches ORDER_123.csv but not order_123.csv
-                - `"INV_{{date 'YYYYMMDD'}}"` - matches current date's invoices
+                - `"INV_{{timestamp 'YYYYMMDD'}}"` - matches current date's invoices
           examples:
             - ORDER_
             - INV_
             - EXPORT_
-            - PO_{{date 'YYYYMMDD'}}
+            - PO_{{timestamp 'YYYYMMDD'}}
         fileNameEndsWith:
           type: string
           x-celigo-agent:
@@ -9738,7 +9738,7 @@ components:
           examples:
             - processed
             - archive
-            - backup/{{date 'YYYY-MM'}}
+            - backup/{{timestamp 'YYYY-MM'}}
             - /var/ftp/archive
           x-celigo-agent:
             - handlebars
@@ -12267,12 +12267,12 @@ components:
               - Can contain static text or handlebars templates
               - Examples:
                 - `"processed/"` - places files under a processed folder
-                - `"archive/{{date 'YYYY-MM-DD'}}/"` - organizes by date
+                - `"archive/{{timestamp 'YYYY-MM-DD'}}/"` - organizes by date
           examples:
             - processed/
-            - archive/{{date 'YYYY-MM'}}/
+            - archive/{{timestamp 'YYYY-MM'}}/
             - history/
-            - completed/{{date 'YYYY/MM/DD'}}/
+            - completed/{{timestamp 'YYYY/MM/DD'}}/
           x-celigo-agent:
             - handlebars
     Wrapper:

package/dist/import.yml CHANGED Viewed

@@ -3091,7 +3091,10 @@ components:
           description: |-
             Name of the file written to the server, including its extension; do not include directory
             separators — the location comes from directoryPath. Supports handlebars placeholders such
-            as items-{{timestamp}}.csv to generate a unique name per run. The template is rendered
+            as items-{{timestamp}}.csv to generate a unique name per run; `{{timestamp}}` alone renders
+            the full ISO-8601 time, colons included (`2026-10-23T08:25:21.743Z`), and a format gives
+            a date stamp instead: `orders-{{timestamp 'YYYYMMDD'}}.csv`. There is no `date` helper. The
+            template is rendered
             against the incoming record: a file-transfer import from an FTP source kept the source
             file's name with `{{record.fileMeta.fileName}}` set on `file.fileName` and this field left
             unset — other source providers expose the name under their own `fileMeta` field.
@@ -3163,7 +3166,7 @@ components:
               - May be influenced by file transfer mode (binary or ASCII) based on the file type.
           examples:
             - items-{{timestamp}}.csv
-            - orders-{{date 'YYYYMMDD'}}.xml
+            - orders-{{timestamp 'YYYYMMDD'}}.xml
             - export.json
         inProgressFileName:
           type: string
@@ -3274,7 +3277,7 @@ components:
           examples:
             - processed
             - archive
-            - backup/{{date 'YYYY-MM'}}
+            - backup/{{timestamp 'YYYY-MM'}}
     Jdbc:
       type: object
       description: |-
@@ -8743,13 +8746,13 @@ components:
             **Common patterns**
             - `"data-{{timestamp}}.json"` - Timestamped JSON file (DEFAULT — use this pattern when not specified)
-            - `"export-{{date}}.csv"` - Date-stamped CSV file
+            - `"export-{{timestamp 'YYYY-MM-DD'}}.csv"` - Date-stamped CSV file
             - `"{{recordType}}-backup.xml"` - Dynamic record type naming
             **Examples**
             - `"customers-{{timestamp}}.json"`
             - `"orders-export.csv"`
-            - `"inventory-{{date}}.xlsx"`
+            - `"inventory-{{timestamp 'YYYY-MM-DD'}}.xlsx"`
             **Important**
             - For S3 imports, this should typically match the `s3.fileKey` value

package/dist/mcp-server.yml CHANGED Viewed

@@ -5643,10 +5643,34 @@ components:
             - Amazon-Hybrid
             - vendor_central
           x-enumDescriptions:
-            Amazon-SP-API: Amazon Selling Partner API connection.
-            Amazon-Hybrid: Hybrid Amazon connection supporting both MWS and SP-API.
-            vendor_central: Amazon Vendor Central API connection.
-          description: Specific API type for Amazon integrations. Only set this for Amazon connections.
+            Amazon-SP-API: Amazon Seller Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
+            Amazon-Hybrid: Amazon Seller Central over both the legacy MWS and the Selling Partner API, for integrations not yet fully on SP-API
+            vendor_central: Amazon Vendor Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
+          description: |-
+            Selects which Amazon selling program and API family a prebuilt Amazon connection talks to.
+            Set by the Amazon Seller Central and Amazon Vendor Central connection forms; a custom
+            Selling Partner API integration built on the customer's own developer application is a
+            plain HTTP connection and does not carry this field.
+          x-celigo-ai-guidance:
+            - |-
+              The prebuilt Amazon connection forms collect the API type, selling region and marketplace
+              and save an OAuth 2.0 authorization-code connection (`http.auth.type` `oauth`,
+              `http.auth.oauth.grantType` `authorizecode`, `useIClientFields` false) whose authorization
+              URI is the Seller Central or Vendor Central `/apps/authorize/consent` page — Amazon's
+              public-application consent, granted by the selling partner to Celigo's registered
+              Selling Partner API application. Celigo's Seller Central documentation states the customer
+              need not register as an Amazon developer (article 360060827012); the Vendor Central form
+              carries no developer credentials either.
+            - |-
+              The prebuilt forms collect no Amazon developer application id, client secret, AWS
+              credentials or iClient — the Vendor Central form has no iClient field, and the Seller
+              Central form sets `http._iClientId` only for its legacy `Amazon-MWS` choice — so creating
+              one of these connections asks the customer for a Seller Central or Vendor Central account
+              for the chosen region and marketplace and a user who can complete Amazon's consent screen,
+              nothing more. A customer who must run on their OWN developer registration builds a
+              token-based or OAuth 2.0 universal HTTP connection to the Selling Partner API base URI
+              instead (articles 6204088366363 and the OAuth 2.0 universal connector) and takes on
+              Amazon's developer agreements themselves.
           examples:
             - Amazon-SP-API
         clientCertificates:

package/dist/tool.yml CHANGED Viewed

@@ -9177,10 +9177,34 @@ components:
             - Amazon-Hybrid
             - vendor_central
           x-enumDescriptions:
-            Amazon-SP-API: Amazon Selling Partner API connection.
-            Amazon-Hybrid: Hybrid Amazon connection supporting both MWS and SP-API.
-            vendor_central: Amazon Vendor Central API connection.
-          description: Specific API type for Amazon integrations. Only set this for Amazon connections.
+            Amazon-SP-API: Amazon Seller Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
+            Amazon-Hybrid: Amazon Seller Central over both the legacy MWS and the Selling Partner API, for integrations not yet fully on SP-API
+            vendor_central: Amazon Vendor Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
+          description: |-
+            Selects which Amazon selling program and API family a prebuilt Amazon connection talks to.
+            Set by the Amazon Seller Central and Amazon Vendor Central connection forms; a custom
+            Selling Partner API integration built on the customer's own developer application is a
+            plain HTTP connection and does not carry this field.
+          x-celigo-ai-guidance:
+            - |-
+              The prebuilt Amazon connection forms collect the API type, selling region and marketplace
+              and save an OAuth 2.0 authorization-code connection (`http.auth.type` `oauth`,
+              `http.auth.oauth.grantType` `authorizecode`, `useIClientFields` false) whose authorization
+              URI is the Seller Central or Vendor Central `/apps/authorize/consent` page — Amazon's
+              public-application consent, granted by the selling partner to Celigo's registered
+              Selling Partner API application. Celigo's Seller Central documentation states the customer
+              need not register as an Amazon developer (article 360060827012); the Vendor Central form
+              carries no developer credentials either.
+            - |-
+              The prebuilt forms collect no Amazon developer application id, client secret, AWS
+              credentials or iClient — the Vendor Central form has no iClient field, and the Seller
+              Central form sets `http._iClientId` only for its legacy `Amazon-MWS` choice — so creating
+              one of these connections asks the customer for a Seller Central or Vendor Central account
+              for the chosen region and marketplace and a user who can complete Amazon's consent screen,
+              nothing more. A customer who must run on their OWN developer registration builds a
+              token-based or OAuth 2.0 universal HTTP connection to the Selling Partner API base URI
+              instead (articles 6204088366363 and the OAuth 2.0 universal connector) and takes on
+              Amazon's developer agreements themselves.
           examples:
             - Amazon-SP-API
         clientCertificates:
@@ -14948,7 +14972,10 @@ components:
           description: |-
             Name of the file written to the server, including its extension; do not include directory
             separators — the location comes from directoryPath. Supports handlebars placeholders such
-            as items-{{timestamp}}.csv to generate a unique name per run. The template is rendered
+            as items-{{timestamp}}.csv to generate a unique name per run; `{{timestamp}}` alone renders
+            the full ISO-8601 time, colons included (`2026-10-23T08:25:21.743Z`), and a format gives
+            a date stamp instead: `orders-{{timestamp 'YYYYMMDD'}}.csv`. There is no `date` helper. The
+            template is rendered
             against the incoming record: a file-transfer import from an FTP source kept the source
             file's name with `{{record.fileMeta.fileName}}` set on `file.fileName` and this field left
             unset — other source providers expose the name under their own `fileMeta` field.
@@ -15020,7 +15047,7 @@ components:
               - May be influenced by file transfer mode (binary or ASCII) based on the file type.
           examples:
             - items-{{timestamp}}.csv
-            - orders-{{date 'YYYYMMDD'}}.xml
+            - orders-{{timestamp 'YYYYMMDD'}}.xml
             - export.json
         inProgressFileName:
           type: string
@@ -15131,7 +15158,7 @@ components:
           examples:
             - processed
             - archive
-            - backup/{{date 'YYYY-MM'}}
+            - backup/{{timestamp 'YYYY-MM'}}
     Jdbc:
       type: object
       description: |-
@@ -20321,13 +20348,13 @@ components:
             **Common patterns**
             - `"data-{{timestamp}}.json"` - Timestamped JSON file (DEFAULT — use this pattern when not specified)
-            - `"export-{{date}}.csv"` - Date-stamped CSV file
+            - `"export-{{timestamp 'YYYY-MM-DD'}}.csv"` - Date-stamped CSV file
             - `"{{recordType}}-backup.xml"` - Dynamic record type naming
             **Examples**
             - `"customers-{{timestamp}}.json"`
             - `"orders-export.csv"`
-            - `"inventory-{{date}}.xlsx"`
+            - `"inventory-{{timestamp 'YYYY-MM-DD'}}.xlsx"`
             **Important**
             - For S3 imports, this should typically match the `s3.fileKey` value
@@ -34678,7 +34705,7 @@ components:
             Directory on the server to retrieve files from, either absolute or relative to the login
             directory; the FTP user must have read permission on it. Use forward slashes regardless
             of server OS — paths are case-sensitive on UNIX/Linux servers. Supports handlebars
-            templates, e.g. archive/{{date 'YYYY-MM-DD'}}.
+            templates, e.g. archive/{{timestamp 'YYYY-MM-DD'}}.
           examples:
             - users/dave
             - incoming/orders
@@ -34700,12 +34727,12 @@ components:
               - Can use static text or handlebars templates
               - Examples:
                 - `"ORDER_"` - matches ORDER_123.csv but not order_123.csv
-                - `"INV_{{date 'YYYYMMDD'}}"` - matches current date's invoices
+                - `"INV_{{timestamp 'YYYYMMDD'}}"` - matches current date's invoices
           examples:
             - ORDER_
             - INV_
             - EXPORT_
-            - PO_{{date 'YYYYMMDD'}}
+            - PO_{{timestamp 'YYYYMMDD'}}
         fileNameEndsWith:
           type: string
           x-celigo-agent:
@@ -34759,7 +34786,7 @@ components:
           examples:
             - processed
             - archive
-            - backup/{{date 'YYYY-MM'}}
+            - backup/{{timestamp 'YYYY-MM'}}
             - /var/ftp/archive
           x-celigo-agent:
             - handlebars
@@ -37288,12 +37315,12 @@ components:
               - Can contain static text or handlebars templates
               - Examples:
                 - `"processed/"` - places files under a processed folder
-                - `"archive/{{date 'YYYY-MM-DD'}}/"` - organizes by date
+                - `"archive/{{timestamp 'YYYY-MM-DD'}}/"` - organizes by date
           examples:
             - processed/
-            - archive/{{date 'YYYY-MM'}}/
+            - archive/{{timestamp 'YYYY-MM'}}/
             - history/
-            - completed/{{date 'YYYY/MM/DD'}}/
+            - completed/{{timestamp 'YYYY/MM/DD'}}/
           x-celigo-agent:
             - handlebars
     Wrapper-3:

package/package.json CHANGED Viewed

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

package/schemas.json CHANGED Viewed

@@ -1,8 +1,8 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "9951106d",
-		"generatedAt": "2026-10-22"
+		"iasCommit": "7c984e81",
+		"generatedAt": "2026-10-23"
 	},
 	"roots": {
 		"aiagent": 127,