npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-amazon-selling-partner-marketplace

v0.0.22

Published

n8n community node for the Amazon Selling Partner API

Readme

n8n-nodes-amazon-selling-partner-marketplace

Community node for the Amazon Selling Partner API (SP-API).

Installation

Follow the n8n community nodes installation guide: https://docs.n8n.io/integrations/community-nodes/installation/

Credentials

Create your SP-API application in Seller Central: https://sellercentral.amazon.de/sellingpartner/developerconsole

You will need:

  • Application ID
  • LWA Client ID
  • LWA Client Secret
  • LWA Refresh Token (from app authorization)
  • AWS Access Key ID
  • AWS Secret Access Key
  • Primary Marketplace (must match your app authorization)
  • AWS Region (must match your marketplace)

Note:

  • Seller ID is optional. If provided, it is used directly. If missing, the node tries to auto-detect via marketplace participations.
  • LWA access tokens are refreshed automatically.
  • If Marketplace/Region do not match, Amazon returns 401/403.

Supported Resources (current)

Amazon Warehousing And Distribution, Aplus Content, Application Integrations, Application Management, Catalog Items, Customer Feedback, Data Kiosk, Delivery By Amazon, Easy Ship, External Fulfillment, Fba Inbound Eligibility, Fba Inventory, Feeds, Finances, Fulfillment Inbound, Fulfillment Outbound, Invoices, Listings Items, Listings Restrictions, Merchant Fulfillment, Messaging, Notifications, Orders, Product Fees, Product Pricing, Product Type Definitions, Replenishment, Reports, Sales, Seller Wallet, Sellers, Services, Shipment Invoicing, Shipping, Solicitations, Supply Sources, Tokens, Uploads, Vehicles, Vendor Direct Fulfillment Inventory, Vendor Direct Fulfillment Orders, Vendor Direct Fulfillment Payments, Vendor Direct Fulfillment Sandbox Test Data, Vendor Direct Fulfillment Shipping, Vendor Direct Fulfillment Transactions, Vendor Invoices, Vendor Orders, Vendor Shipments, Vendor Transaction Status.

Custom API Call

Use the Custom resource when you need an endpoint that is not mapped yet or when you want full control.

Custom Request supports:

  • Method
  • Endpoint (path or full URL)
  • Query (JSON)
  • Body (JSON)
  • Headers (JSON)
  • Response type (json or text)
  • Include response metadata

You can also use "Request via JSON Definition" to submit a full request object (or an array of requests).

Example 1: Catalog Items search (Custom Request)

  • Resource: Custom
  • Operation: Custom Request
  • Method: GET
  • Endpoint: /catalog/2022-04-01/items
  • Query (JSON):
{
  "marketplaceIds": ["A1PA6795UKMFR9"],
  "keywords": ["keyboard"],
  "includedData": ["summaries"],
  "pageSize": 10
}

Example 2: Listings Items get (Custom Request)

Replace the placeholders with your sellerId and SKU.

  • Resource: Custom
  • Operation: Custom Request
  • Method: GET
  • Endpoint: /listings/2021-08-01/items/SELLER_ID/SKU
  • Query (JSON):
{
  "marketplaceIds": ["A1PA6795UKMFR9"],
  "includedData": ["summaries"],
  "issueLocale": "de_DE"
}

Example 3: JSON Definition (single request)

  • Resource: Custom
  • Operation: Request via JSON Definition
  • Request Definition (JSON):
{
  "method": "GET",
  "endpoint": "/catalog/2022-04-01/items",
  "query": {
    "marketplaceIds": ["A1PA6795UKMFR9"],
    "keywords": ["headphones"],
    "includedData": ["summaries"],
    "pageSize": 5
  },
  "responseType": "json",
  "includeMetadata": false
}

Example 4: JSON Definition (PATCH Listings Item)

  • Resource: Custom
  • Operation: Request via JSON Definition
  • Request Definition (JSON):
{
  "method": "PATCH",
  "endpoint": "/listings/2021-08-01/items/SELLER_ID/SKU",
  "query": {
    "marketplaceIds": ["A1PA6795UKMFR9"],
    "issueLocale": "de_DE"
  },
  "body": {
    "productType": "PRODUCT",
    "patches": [
      {
        "op": "replace",
        "path": "/attributes/item_name",
        "value": [
          {
            "value": "Neuer Produkttitel",
            "languageTag": "de_DE"
          }
        ]
      }
    ]
  },
  "responseType": "json",
  "includeMetadata": false
}

Resources

  • SP-API Reference: https://developer-docs.amazon.com/sp-api/reference/welcome-to-api-references
  • SP-API Setup: https://developer-docs.amazon.com/sp-api/docs/connecting-to-the-selling-partner-api