Overview

Amazon has added official Selling Partner API (SP‑API) Software Development Kits for Java and PHP, expanding the toolkit that already included JavaScript and Python libraries. The new SDKs are production‑ready, handling authentication, error recovery, and multi‑region routing automatically, which removes a major technical barrier for sellers and developers building integrations on Java or PHP stacks.

Key Points

• Official Java & PHP SDKs — Amazon now offers pre‑configured libraries for the two most widely used backend languages, joining its existing JavaScript and Python options.
• Zero‑code client generation — The SDKs stay in sync with SP‑API revisions automatically, so developers no longer need to regenerate client code whenever Amazon adds or deprecates endpoints.
• Built‑in auth flow — Full support for AWS Signature Version 4 signing, Login with Amazon (LWA) token handling, and credential refresh is embedded, eliminating manual token management.
• Smart retry logic — Each library applies exponential backoff, respects Amazon’s retry‑after headers, and categorises errors to distinguish transient throttling from permanent request faults.
• Typed language support — Java type definitions and PHPDoc annotations give IDE autocomplete and compile‑time safety, reducing runtime bugs.
• Single‑code multi‑region access — Sellers can switch between North America, Europe, and Far East marketplaces through configuration alone, without rewriting request logic.

How the New SDKs Work

1. Installation & configuration —

   • Java: Add the Maven artifact to the pom.xml; specify clientId, clientSecret, and target region in a properties file.
   • PHP: Run composer require amazon/sp-api-sdk-php; place credentials in a .env file and reference them when creating the SDK client.
     Example: A developer in Berlin adds the Maven dependency and sets to target the German marketplace.