Using SDKs

An SDK bundles multiple steps together, such as requesting an access token and requesting a security token, to call the SP-APIs seamlessly. After choosing an SDK, you must generate your SDK and connect it to the Selling Partner API.

SDKs available for SP-API

SDKs versions are available based on the code languages they use.

📘

Note

Before integrating with SP-API, it is important to note that these SDKs are not available as pre-packaged, publicly published npm modules. Instead, they use a self-service model where you, the developer, use swagger-codegen to generate SDK code directly from API models. With a self-service model, you can create an SDK to suit your specific needs.

This approach ensures you have the most up-to-date, tailored SDK versions and that they are compatible with the latest SP-API changes and features. While this requires an extra step compared to using a pre-built package, it gives you direct control over SDK generation and versioning, offering a first-hand integration experience.

C# SDK

Tutorial: Automate your SP-API calls using C# SDK Tutorial to automate your SP-API calls with C# SDK with Login with Amazon (LWA) token exchange and authentication.

Java SDK

Tutorial: Automate your SP-API calls using Automate your SP-API calls using Java SDK Tutorial to automate your SP-API calls with Java SDK with Login with Amazon (LWA) token exchange and authentication.

JavaScript SDK for Node.js

Tutorial: Automate your SP-API calls using JavaScript SDK for Node.js Tutorial to automate your SP-API calls with JavaScript SDK for Node.js with Login with Amazon (LWA) token exchange and authentication.

Python SDK

Tutorial: Automate your SP-API calls using Python SDK Tutorial to automate your SP-API calls with Python SDK with Login with Amazon (LWA) token exchange and authentication.