Update: Easy Ship API v2022-03-23 now supports the Japan (JP) marketplace
In April 2024 Amazon extended the Easy Ship API version 2022‑03‑23 to include the Japan marketplace (MarketplaceId A1VC38T7YXB528). The same v2022‑03‑23 endpoint now accepts JP orders and returns Japan‑specific carrier codes such as Yamato Transport and Japan Post, with no version bump required.
Overview
Amazon has added support for the Japan (JP) marketplace to the Easy Ship API version 2022‑03‑23. The update, released this week, lets developers and sellers programmatically manage Easy Ship orders originating from Japan. Anyone using automated fulfillment tools should take note, as the change opens a path to fully integrated shipping workflows in a key Asian market.
Key Points
- Japan marketplace enabled — The API now accepts Easy Ship requests for orders tied to the Japanese marketplace identifier, expanding automation capabilities to sellers based in Japan.
- Same version retained — The new region is covered by the existing v2022‑03‑23 endpoint, so no version bump or code overhaul is required to start using JP support.
- Marketplace identifier added — The only structural change is the inclusion of
MarketplaceId = A1VC38T7YXB528among the accepted values; request and response schemas stay identical. - Automation across borders — Japanese Easy Ship orders can be merged into the same order‑processing pipelines that already handle US, EU, or Canada shipments, cutting manual entry time.
- Local carrier data supplied — Responses now contain Japan‑specific carrier codes and service levels, such as Yamato Transport and Japan Post, ensuring compliance with domestic shipping rules.
- No new cost burden — Amazon applies the same throttling limits and pricing model to JP calls, meaning sellers incur no extra fees for the expanded coverage.
How Easy Ship API Works with Japan Marketplace
-
Specify the JP marketplace — Include the Japanese marketplace ID (
A1VC38T7YXB528) in any Easy Ship request payload.
Example: A nightly script that pulls pending orders adds a filter forMarketplaceId = "A1VC38T7YXB528"before invokingGET /easyShip/v1/eligibleShippingServices. -
Fetch eligible shipping services — Call the endpoint, passing the order’s weight, dimensions, and destination postal code. : For a 500‑gram parcel destined for Tokyo’s 100‑0001 ZIP, the API returns options like Yamato Transport’s “TA‑Q‑BIN” and Japan Post’s “Yu‑Pack” with associated service codes.
Analysis & Recommendations
Why This Matters
Japanese sellers can now automate the full Easy Ship workflow—service selection, shipment confirmation, tracking and exception handling—directly from their ERP or logistics platforms. This reduces manual entry, speeds order processing, and keeps throttling limits (30 calls/sec) unchanged, avoiding extra fees.
Key Takeaways
- MarketplaceId for Japan is A1VC38T7YXB528 and is accepted by the current v2022‑03‑23 endpoint.
- No new API version is required; existing Easy Ship calls work unchanged for JP orders.
- Responses now include Japan‑specific carrier codes (e.g., Yamato’s TA‑Q‑BIN) and tracking numbers starting with “YT”.
- Standard throttling limits (≈30 calls per second) and pricing remain the same for JP calls.
Recommended Actions
- →Update order‑retrieval scripts to add MarketplaceId = "A1VC38T7YXB528" in your code or in Seller Central > Reports > Order Export.
- →Modify Easy Ship request payloads to include the JP MarketplaceId and handle new carrierCode values in your integration code.
- →Monitor API usage against the 30 calls/sec limit and add exponential back‑off in your error‑handling routine.
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!