Amazon Releases Official Prebuilt SP-API SDK for C# and .NET Developers
Amazon launched the official pre‑built SP‑API SDK for C#/.NET (NuGet package software.amzn.spapi) supporting .NET 7.0+. The SDK installs with a single `dotnet add package` command, includes a fluent OAuth builder, async methods and auto‑updates (e.g., from version 1.3.0 to 1.4.0).
Overview
Amazon has launched an official, pre‑built SDK for the Selling Partner API (SP‑API) that targets C# and .NET developers. Distributed as a NuGet package, the library eliminates the manual step of generating client code from Amazon’s OpenAPI definitions, a process that previously consumed many hours of development and ongoing upkeep. Sellers and their technical partners should pay attention because the SDK promises quicker time‑to‑market, automatic alignment with Amazon’s API revisions, and built‑in handling of OAuth authentication.
Key Points
- One‑command install — Adding the
software.amzn.spapipackage to any .NET 7.0 or later project requires a singledotnet add packagecall, replacing the multi‑hour workflow of downloading specs and running code generators. - Automatic API updates — Amazon publishes SDK updates centrally; when a developer bumps the NuGet version, the latest SP‑API changes are incorporated without re‑running generation scripts.
- Built‑in OAuth flow — Fluent builder methods accept client ID, client secret and refresh token, allowing the SDK to obtain and refresh access tokens automatically, removing the need for custom signing code.
- Comprehensive endpoint coverage – Core SP‑API sections such as Orders, Catalog Items, Feeds, Listings and many ancillary services are exposed through strongly‑typed C# methods, enabling a single line call for most operations.
- Modern .NET design — The library follows current C# patterns, offering async methods, dependency‑injection‑ready interfaces and builder‑style configuration, which fits naturally into existing .NET architectures.
How the Prebuilt SP‑API SDK Works
- Add the package — Execute
dotnet add package software.amzn.spapiin the solution directory; the NuGet manager retrieves the compiled client library together with all required dependencies. - Configure credentials — Instantiate the builder and supply the three OAuth pieces:
The builder stores these values, requests an access token from Amazon, and refreshes it automatically when it expires.var spApiClient = new SpApiClientBuilder() .WithClientId("YOUR_CLIENT_ID") .WithClientSecret("YOUR_CLIENT_SECRET") .WithRefreshToken("YOUR_REFRESH_TOKEN") .Build();
Analysis & Recommendations
Why This Matters
Developers can cut integration time from weeks to a day by eliminating manual OpenAPI generation and custom OAuth code. Automatic NuGet updates (e.g., 1.4.0) ensure new Amazon API fields are available without code changes, reducing maintenance overhead for sellers and partners.
Key Takeaways
- One‑command install via `dotnet add package software.amzn.spapi` replaces multi‑hour generation steps.
- Built‑in OAuth builder requires client ID, secret and refresh token, handling token refresh automatically.
- SDK covers core SP‑API sections (Orders, Catalog Items, Feeds, Listings) with async, DI‑ready interfaces.
- Version bump from 1.3.0 to 1.4.0 delivers automatic API updates without regenerating code.
Recommended Actions
- →Run `dotnet add package software.amzn.spapi` in your solution to add the SDK.
- →Configure credentials using SpApiClientBuilder in code and register ISpApiClient with your DI container.
- →Schedule a quarterly NuGet package upgrade (e.g., via Azure DevOps or GitHub Actions) to stay current with Amazon API changes.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!