Amazon Launches Official SP-API SDKs for Java and PHP, Expanding Developer Toolkit
Amazon released official SP-API SDKs for Java and PHP on 2024-11-15, adding Maven artifact com.amazon:selling-partner-api-java:1.2.0 and Composer package amazon/sp-api-sdk-php. The libraries include built‑in AWS Signature V4, LWA token refresh, exponential backoff retries and multi‑region routing.
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
-
Installation & configuration —
- Java: Add the Maven artifact to the
pom.xml; specifyclientId,clientSecret, and target region in a properties file. - PHP: Run
composer require amazon/sp-api-sdk-php; place credentials in a.envfile and reference them when creating the SDK client.
Example: A developer in Berlin adds the Maven dependency and sets to target the German marketplace.
- Java: Add the Maven artifact to the
Analysis & Recommendations
Why This Matters
Developers can now install a single package, configure clientId, clientSecret and region, and immediately call endpoints like listOrders without writing custom signing code. Automatic retries and typed responses lower downtime and runtime bugs, accelerating multi‑marketplace scaling for US, EU and APAC sellers.
Key Takeaways
- Java SDK version 1.2.0 is available via Maven (com.amazon:selling-partner-api-java:1.2.0).
- PHP SDK is installed with composer require amazon/sp-api-sdk-php and uses a .env file for credentials.
- Both SDKs embed AWS Signature V4, LWA token handling and exponential backoff with respect for Retry‑After headers.
- Multi‑region support is configured by a single 'region' property (e.g., eu-west-1, us-east-1, ap-southeast-1).
Recommended Actions
- →Java developers: add com.amazon:selling-partner-api-java:1.2.0 to pom.xml, set clientId, clientSecret and region in a properties file, then rebuild...
- →PHP developers: run composer require amazon/sp-api-sdk-php, create a .env with LWA and AWS keys, and instantiate the SDK client as shown in the docs.
- →All sellers: test the new SDKs by calling listOrders() for one marketplace, then change the region value to verify multi‑region endpoint switching.
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!