@celigo/api-specs 0.2.179 → 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 (7) hide show
  1. package/dist/api.yml +28 -4
  2. package/dist/connection.yml +28 -4
  3. package/dist/enduser.yml +28 -4
  4. package/dist/mcp-server.yml +28 -4
  5. package/dist/tool.yml +28 -4
  6. package/package.json +1 -1
  7. package/schemas.json +1 -1
package/dist/api.yml CHANGED
@@ -6899,10 +6899,34 @@ components:
6899
6899
  - Amazon-Hybrid
6900
6900
  - vendor_central
6901
6901
  x-enumDescriptions:
6902
- Amazon-SP-API: Amazon Selling Partner API connection.
6903
- Amazon-Hybrid: Hybrid Amazon connection supporting both MWS and SP-API.
6904
- vendor_central: Amazon Vendor Central API connection.
6905
- description: Specific API type for Amazon integrations. Only set this for Amazon connections.
6902
+ Amazon-SP-API: Amazon Seller Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
6903
+ Amazon-Hybrid: Amazon Seller Central over both the legacy MWS and the Selling Partner API, for integrations not yet fully on SP-API
6904
+ vendor_central: Amazon Vendor Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
6905
+ description: |-
6906
+ Selects which Amazon selling program and API family a prebuilt Amazon connection talks to.
6907
+ Set by the Amazon Seller Central and Amazon Vendor Central connection forms; a custom
6908
+ Selling Partner API integration built on the customer's own developer application is a
6909
+ plain HTTP connection and does not carry this field.
6910
+ x-celigo-ai-guidance:
6911
+ - |-
6912
+ The prebuilt Amazon connection forms collect the API type, selling region and marketplace
6913
+ and save an OAuth 2.0 authorization-code connection (`http.auth.type` `oauth`,
6914
+ `http.auth.oauth.grantType` `authorizecode`, `useIClientFields` false) whose authorization
6915
+ URI is the Seller Central or Vendor Central `/apps/authorize/consent` page — Amazon's
6916
+ public-application consent, granted by the selling partner to Celigo's registered
6917
+ Selling Partner API application. Celigo's Seller Central documentation states the customer
6918
+ need not register as an Amazon developer (article 360060827012); the Vendor Central form
6919
+ carries no developer credentials either.
6920
+ - |-
6921
+ The prebuilt forms collect no Amazon developer application id, client secret, AWS
6922
+ credentials or iClient — the Vendor Central form has no iClient field, and the Seller
6923
+ Central form sets `http._iClientId` only for its legacy `Amazon-MWS` choice — so creating
6924
+ one of these connections asks the customer for a Seller Central or Vendor Central account
6925
+ for the chosen region and marketplace and a user who can complete Amazon's consent screen,
6926
+ nothing more. A customer who must run on their OWN developer registration builds a
6927
+ token-based or OAuth 2.0 universal HTTP connection to the Selling Partner API base URI
6928
+ instead (articles 6204088366363 and the OAuth 2.0 universal connector) and takes on
6929
+ Amazon's developer agreements themselves.
6906
6930
  examples:
6907
6931
  - Amazon-SP-API
6908
6932
  clientCertificates:
package/dist/connection.yml CHANGED
@@ -5756,10 +5756,34 @@ components:
5756
5756
  - Amazon-Hybrid
5757
5757
  - vendor_central
5758
5758
  x-enumDescriptions:
5759
- Amazon-SP-API: Amazon Selling Partner API connection.
5760
- Amazon-Hybrid: Hybrid Amazon connection supporting both MWS and SP-API.
5761
- vendor_central: Amazon Vendor Central API connection.
5762
- description: Specific API type for Amazon integrations. Only set this for Amazon connections.
5759
+ Amazon-SP-API: Amazon Seller Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
5760
+ Amazon-Hybrid: Amazon Seller Central over both the legacy MWS and the Selling Partner API, for integrations not yet fully on SP-API
5761
+ vendor_central: Amazon Vendor Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
5762
+ description: |-
5763
+ Selects which Amazon selling program and API family a prebuilt Amazon connection talks to.
5764
+ Set by the Amazon Seller Central and Amazon Vendor Central connection forms; a custom
5765
+ Selling Partner API integration built on the customer's own developer application is a
5766
+ plain HTTP connection and does not carry this field.
5767
+ x-celigo-ai-guidance:
5768
+ - |-
5769
+ The prebuilt Amazon connection forms collect the API type, selling region and marketplace
5770
+ and save an OAuth 2.0 authorization-code connection (`http.auth.type` `oauth`,
5771
+ `http.auth.oauth.grantType` `authorizecode`, `useIClientFields` false) whose authorization
5772
+ URI is the Seller Central or Vendor Central `/apps/authorize/consent` page — Amazon's
5773
+ public-application consent, granted by the selling partner to Celigo's registered
5774
+ Selling Partner API application. Celigo's Seller Central documentation states the customer
5775
+ need not register as an Amazon developer (article 360060827012); the Vendor Central form
5776
+ carries no developer credentials either.
5777
+ - |-
5778
+ The prebuilt forms collect no Amazon developer application id, client secret, AWS
5779
+ credentials or iClient — the Vendor Central form has no iClient field, and the Seller
5780
+ Central form sets `http._iClientId` only for its legacy `Amazon-MWS` choice — so creating
5781
+ one of these connections asks the customer for a Seller Central or Vendor Central account
5782
+ for the chosen region and marketplace and a user who can complete Amazon's consent screen,
5783
+ nothing more. A customer who must run on their OWN developer registration builds a
5784
+ token-based or OAuth 2.0 universal HTTP connection to the Selling Partner API base URI
5785
+ instead (articles 6204088366363 and the OAuth 2.0 universal connector) and takes on
5786
+ Amazon's developer agreements themselves.
5763
5787
  examples:
5764
5788
  - Amazon-SP-API
5765
5789
  clientCertificates:
package/dist/enduser.yml CHANGED
@@ -3807,10 +3807,34 @@ components:
3807
3807
  - Amazon-Hybrid
3808
3808
  - vendor_central
3809
3809
  x-enumDescriptions:
3810
- Amazon-SP-API: Amazon Selling Partner API connection.
3811
- Amazon-Hybrid: Hybrid Amazon connection supporting both MWS and SP-API.
3812
- vendor_central: Amazon Vendor Central API connection.
3813
- description: Specific API type for Amazon integrations. Only set this for Amazon connections.
3810
+ Amazon-SP-API: Amazon Seller Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
3811
+ Amazon-Hybrid: Amazon Seller Central over both the legacy MWS and the Selling Partner API, for integrations not yet fully on SP-API
3812
+ vendor_central: Amazon Vendor Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
3813
+ description: |-
3814
+ Selects which Amazon selling program and API family a prebuilt Amazon connection talks to.
3815
+ Set by the Amazon Seller Central and Amazon Vendor Central connection forms; a custom
3816
+ Selling Partner API integration built on the customer's own developer application is a
3817
+ plain HTTP connection and does not carry this field.
3818
+ x-celigo-ai-guidance:
3819
+ - |-
3820
+ The prebuilt Amazon connection forms collect the API type, selling region and marketplace
3821
+ and save an OAuth 2.0 authorization-code connection (`http.auth.type` `oauth`,
3822
+ `http.auth.oauth.grantType` `authorizecode`, `useIClientFields` false) whose authorization
3823
+ URI is the Seller Central or Vendor Central `/apps/authorize/consent` page — Amazon's
3824
+ public-application consent, granted by the selling partner to Celigo's registered
3825
+ Selling Partner API application. Celigo's Seller Central documentation states the customer
3826
+ need not register as an Amazon developer (article 360060827012); the Vendor Central form
3827
+ carries no developer credentials either.
3828
+ - |-
3829
+ The prebuilt forms collect no Amazon developer application id, client secret, AWS
3830
+ credentials or iClient — the Vendor Central form has no iClient field, and the Seller
3831
+ Central form sets `http._iClientId` only for its legacy `Amazon-MWS` choice — so creating
3832
+ one of these connections asks the customer for a Seller Central or Vendor Central account
3833
+ for the chosen region and marketplace and a user who can complete Amazon's consent screen,
3834
+ nothing more. A customer who must run on their OWN developer registration builds a
3835
+ token-based or OAuth 2.0 universal HTTP connection to the Selling Partner API base URI
3836
+ instead (articles 6204088366363 and the OAuth 2.0 universal connector) and takes on
3837
+ Amazon's developer agreements themselves.
3814
3838
  examples:
3815
3839
  - Amazon-SP-API
3816
3840
  clientCertificates:
package/dist/mcp-server.yml CHANGED
@@ -5643,10 +5643,34 @@ components:
5643
5643
  - Amazon-Hybrid
5644
5644
  - vendor_central
5645
5645
  x-enumDescriptions:
5646
- Amazon-SP-API: Amazon Selling Partner API connection.
5647
- Amazon-Hybrid: Hybrid Amazon connection supporting both MWS and SP-API.
5648
- vendor_central: Amazon Vendor Central API connection.
5649
- description: Specific API type for Amazon integrations. Only set this for Amazon connections.
5646
+ Amazon-SP-API: Amazon Seller Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
5647
+ Amazon-Hybrid: Amazon Seller Central over both the legacy MWS and the Selling Partner API, for integrations not yet fully on SP-API
5648
+ vendor_central: Amazon Vendor Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
5649
+ description: |-
5650
+ Selects which Amazon selling program and API family a prebuilt Amazon connection talks to.
5651
+ Set by the Amazon Seller Central and Amazon Vendor Central connection forms; a custom
5652
+ Selling Partner API integration built on the customer's own developer application is a
5653
+ plain HTTP connection and does not carry this field.
5654
+ x-celigo-ai-guidance:
5655
+ - |-
5656
+ The prebuilt Amazon connection forms collect the API type, selling region and marketplace
5657
+ and save an OAuth 2.0 authorization-code connection (`http.auth.type` `oauth`,
5658
+ `http.auth.oauth.grantType` `authorizecode`, `useIClientFields` false) whose authorization
5659
+ URI is the Seller Central or Vendor Central `/apps/authorize/consent` page — Amazon's
5660
+ public-application consent, granted by the selling partner to Celigo's registered
5661
+ Selling Partner API application. Celigo's Seller Central documentation states the customer
5662
+ need not register as an Amazon developer (article 360060827012); the Vendor Central form
5663
+ carries no developer credentials either.
5664
+ - |-
5665
+ The prebuilt forms collect no Amazon developer application id, client secret, AWS
5666
+ credentials or iClient — the Vendor Central form has no iClient field, and the Seller
5667
+ Central form sets `http._iClientId` only for its legacy `Amazon-MWS` choice — so creating
5668
+ one of these connections asks the customer for a Seller Central or Vendor Central account
5669
+ for the chosen region and marketplace and a user who can complete Amazon's consent screen,
5670
+ nothing more. A customer who must run on their OWN developer registration builds a
5671
+ token-based or OAuth 2.0 universal HTTP connection to the Selling Partner API base URI
5672
+ instead (articles 6204088366363 and the OAuth 2.0 universal connector) and takes on
5673
+ Amazon's developer agreements themselves.
5650
5674
  examples:
5651
5675
  - Amazon-SP-API
5652
5676
  clientCertificates:
package/dist/tool.yml CHANGED
@@ -9177,10 +9177,34 @@ components:
9177
9177
  - Amazon-Hybrid
9178
9178
  - vendor_central
9179
9179
  x-enumDescriptions:
9180
- Amazon-SP-API: Amazon Selling Partner API connection.
9181
- Amazon-Hybrid: Hybrid Amazon connection supporting both MWS and SP-API.
9182
- vendor_central: Amazon Vendor Central API connection.
9183
- description: Specific API type for Amazon integrations. Only set this for Amazon connections.
9180
+ Amazon-SP-API: Amazon Seller Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
9181
+ Amazon-Hybrid: Amazon Seller Central over both the legacy MWS and the Selling Partner API, for integrations not yet fully on SP-API
9182
+ vendor_central: Amazon Vendor Central over the Selling Partner API, authorized against Celigo's registered application through Login with Amazon
9183
+ description: |-
9184
+ Selects which Amazon selling program and API family a prebuilt Amazon connection talks to.
9185
+ Set by the Amazon Seller Central and Amazon Vendor Central connection forms; a custom
9186
+ Selling Partner API integration built on the customer's own developer application is a
9187
+ plain HTTP connection and does not carry this field.
9188
+ x-celigo-ai-guidance:
9189
+ - |-
9190
+ The prebuilt Amazon connection forms collect the API type, selling region and marketplace
9191
+ and save an OAuth 2.0 authorization-code connection (`http.auth.type` `oauth`,
9192
+ `http.auth.oauth.grantType` `authorizecode`, `useIClientFields` false) whose authorization
9193
+ URI is the Seller Central or Vendor Central `/apps/authorize/consent` page — Amazon's
9194
+ public-application consent, granted by the selling partner to Celigo's registered
9195
+ Selling Partner API application. Celigo's Seller Central documentation states the customer
9196
+ need not register as an Amazon developer (article 360060827012); the Vendor Central form
9197
+ carries no developer credentials either.
9198
+ - |-
9199
+ The prebuilt forms collect no Amazon developer application id, client secret, AWS
9200
+ credentials or iClient — the Vendor Central form has no iClient field, and the Seller
9201
+ Central form sets `http._iClientId` only for its legacy `Amazon-MWS` choice — so creating
9202
+ one of these connections asks the customer for a Seller Central or Vendor Central account
9203
+ for the chosen region and marketplace and a user who can complete Amazon's consent screen,
9204
+ nothing more. A customer who must run on their OWN developer registration builds a
9205
+ token-based or OAuth 2.0 universal HTTP connection to the Selling Partner API base URI
9206
+ instead (articles 6204088366363 and the OAuth 2.0 universal connector) and takes on
9207
+ Amazon's developer agreements themselves.
9184
9208
  examples:
9185
9209
  - Amazon-SP-API
9186
9210
  clientCertificates:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@celigo/api-specs",
3
- "version": "0.2.179",
3
+ "version": "0.2.180",
4
4
  "private": false,
5
5
  "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
6
6
  "keywords": [
package/schemas.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "provenance": {
3
3
  "repo": "celigo/integrator-api-specs",
4
- "iasCommit": "9951106d",
4
+ "iasCommit": "e36986cc",
5
5
  "generatedAt": "2026-10-22"
6
6
  },
7
7
  "roots": {