npm - @celigo/api-specs - Versions diffs - 0.2.178 → 0.2.180 - Mend

@celigo/api-specs 0.2.178 → 0.2.180

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 (8) 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

@@ -8025,11 +8025,13 @@ components:
           It defines how data is extracted from Salesforce,
           either through queries or real-time events.
         - |-
-          Always set `type` on new Salesforce exports (`soql` or `distributed`) —
-          the form always writes it. It is absent only from legacy real-time
-          exports created before the field existed, and file/byId retrievals
-          (`id` + `sObjectType`, no `soql` object) carry `type: soql` without a
-          `soql` object.
+          Set `type` on every Salesforce export you create (`soql` or `distributed`).
+          Never read its absence on an existing export as a defect: a listener saved
+          from the integrator.io form carries no `salesforce.type` and the platform
+          fires it without the field, and file/byId retrievals (`id` + `sObjectType`,
+          no `soql` object) carry `type: soql` without a `soql` object. A listener
+          that never creates a job is diagnosed from `distributed` (below), not from
+          this field.
         - |-
           ## SALESFORCE EXPORT MODES
@@ -8061,8 +8063,10 @@ components:
             Required fields: type, soql.query
             Optional fields: api, includeDeletedRecords, bulk (when api="bulk")
-          - For Distributed exports (type="distributed"):
-            Required fields: type, distributed configuration
+          - For Distributed exports (real-time listeners):
+            Set type="distributed" with the distributed object and sObjectType when creating one.
+            A listener saved from the integrator.io form carries the distributed object and
+            sObjectType with no type, and the platform fires it — a valid listener, not a missing field.
             Optional fields: distributed.referencedFields, distributed.qualifier
           - For Blob exports (when export.type="blob"):
@@ -8078,7 +8082,10 @@ components:
               This field determines the core operating mode of the Salesforce export:
-              - REQUIRED for all Salesforce exports
+              - Set it on every Salesforce export you create; a listener saved from the
+                integrator.io form carries none and the platform fires it without the
+                field, so an absent `type` beside a `distributed` object is the normal
+                shape of a form-saved listener, not a missing setting
               - Controls which additional configuration objects must be provided
               - Affects how the export appears and functions in the flow builder UI
               - Cannot be changed after creation without significant reconfiguration
@@ -8573,7 +8580,7 @@ components:
                 - SELECT Id, Name, (SELECT Id, FirstName, LastName FROM Contacts) FROM Account
         distributed:
           type: object
-          description: Real-time listener configuration; required when `type` is `distributed` and not used otherwise. Records reach the flow only when an Apex trigger on `sObjectType` in the connected org calls the Celigo package (`integrator_da__.RealTimeExporter.processExport()`) — no scheduling or manual execution is involved. Integration Apps create their triggers at installation; for a custom flow the customer deploys the trigger in Salesforce, starting from the code the export page shows under Required trigger.
+          description: 'Real-time listener configuration — the object that makes an export a listener. Set it, with `type: distributed`, when creating one; a listener saved from the integrator.io form carries it with no `type`, and the platform fires it either way. Not used on SOQL or file exports. Records reach the flow only when an Apex trigger on `sObjectType` in the connected org calls the Celigo package (`integrator_da__.RealTimeExporter.processExport()`) — no scheduling or manual execution is involved. Integration Apps create their triggers at installation; for a custom flow the customer deploys the trigger in Salesforce, starting from the code the export page shows under Required trigger.'
           x-celigo-ai-guidance:
             - |-
               After creating a listener on a custom flow, relay what the Help Center's "Listen for real-time data
@@ -8588,6 +8595,12 @@ components:
               Help Center's trigger requirement in the connected org: an active Apex trigger on the object whose
               code calls `integrator_da__.RealTimeExporter`, and the Celigo package reachable through the
               connection (`GET /v1/connections/{_id}/distributed`, documented in this spec set).
+            - |-
+              Two things are never why a listener does not fire. The export preview cannot run a listener:
+              it validates the body as a SOQL export and answers 422 `missing_required_field` for
+              `soql.query` (and for `type` when the listener carries none) before the connection is used,
+              so a failed preview is expected, not a configuration defect. And an absent `salesforce.type`
+              is the normal shape of a listener saved from the integrator.io form (see `type`).
           properties:
             referencedFields:
               type:

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:
@@ -33046,11 +33070,13 @@ components:
           It defines how data is extracted from Salesforce,
           either through queries or real-time events.
         - |-
-          Always set `type` on new Salesforce exports (`soql` or `distributed`) —
-          the form always writes it. It is absent only from legacy real-time
-          exports created before the field existed, and file/byId retrievals
-          (`id` + `sObjectType`, no `soql` object) carry `type: soql` without a
-          `soql` object.
+          Set `type` on every Salesforce export you create (`soql` or `distributed`).
+          Never read its absence on an existing export as a defect: a listener saved
+          from the integrator.io form carries no `salesforce.type` and the platform
+          fires it without the field, and file/byId retrievals (`id` + `sObjectType`,
+          no `soql` object) carry `type: soql` without a `soql` object. A listener
+          that never creates a job is diagnosed from `distributed` (below), not from
+          this field.
         - |-
           ## SALESFORCE EXPORT MODES
@@ -33082,8 +33108,10 @@ components:
             Required fields: type, soql.query
             Optional fields: api, includeDeletedRecords, bulk (when api="bulk")
-          - For Distributed exports (type="distributed"):
-            Required fields: type, distributed configuration
+          - For Distributed exports (real-time listeners):
+            Set type="distributed" with the distributed object and sObjectType when creating one.
+            A listener saved from the integrator.io form carries the distributed object and
+            sObjectType with no type, and the platform fires it — a valid listener, not a missing field.
             Optional fields: distributed.referencedFields, distributed.qualifier
           - For Blob exports (when export.type="blob"):
@@ -33099,7 +33127,10 @@ components:
               This field determines the core operating mode of the Salesforce export:
-              - REQUIRED for all Salesforce exports
+              - Set it on every Salesforce export you create; a listener saved from the
+                integrator.io form carries none and the platform fires it without the
+                field, so an absent `type` beside a `distributed` object is the normal
+                shape of a form-saved listener, not a missing setting
               - Controls which additional configuration objects must be provided
               - Affects how the export appears and functions in the flow builder UI
               - Cannot be changed after creation without significant reconfiguration
@@ -33594,7 +33625,7 @@ components:
                 - SELECT Id, Name, (SELECT Id, FirstName, LastName FROM Contacts) FROM Account
         distributed:
           type: object
-          description: Real-time listener configuration; required when `type` is `distributed` and not used otherwise. Records reach the flow only when an Apex trigger on `sObjectType` in the connected org calls the Celigo package (`integrator_da__.RealTimeExporter.processExport()`) — no scheduling or manual execution is involved. Integration Apps create their triggers at installation; for a custom flow the customer deploys the trigger in Salesforce, starting from the code the export page shows under Required trigger.
+          description: 'Real-time listener configuration — the object that makes an export a listener. Set it, with `type: distributed`, when creating one; a listener saved from the integrator.io form carries it with no `type`, and the platform fires it either way. Not used on SOQL or file exports. Records reach the flow only when an Apex trigger on `sObjectType` in the connected org calls the Celigo package (`integrator_da__.RealTimeExporter.processExport()`) — no scheduling or manual execution is involved. Integration Apps create their triggers at installation; for a custom flow the customer deploys the trigger in Salesforce, starting from the code the export page shows under Required trigger.'
           x-celigo-ai-guidance:
             - |-
               After creating a listener on a custom flow, relay what the Help Center's "Listen for real-time data
@@ -33609,6 +33640,12 @@ components:
               Help Center's trigger requirement in the connected org: an active Apex trigger on the object whose
               code calls `integrator_da__.RealTimeExporter`, and the Celigo package reachable through the
               connection (`GET /v1/connections/{_id}/distributed`, documented in this spec set).
+            - |-
+              Two things are never why a listener does not fire. The export preview cannot run a listener:
+              it validates the body as a SOQL export and answers 422 `missing_required_field` for
+              `soql.query` (and for `type` when the listener carries none) before the connection is used,
+              so a failed preview is expected, not a configuration defect. And an absent `salesforce.type`
+              is the normal shape of a listener saved from the integrator.io form (see `type`).
           properties:
             referencedFields:
               type:

package/package.json CHANGED Viewed

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

package/schemas.json CHANGED Viewed

@@ -1,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "d78b4324",
+		"iasCommit": "e36986cc",
 		"generatedAt": "2026-10-22"
 	},
 	"roots": {