April 2023 SP-API Release Announcement
In April 2023 Amazon released a new SP‑API version that makes the city field optional in the Fulfillment Outbound address schema, eliminating Missing city errors for Japanese shipments.
Overview
In April 2023 Amazon released a new version of the Selling Partner API (SP‑API). The most noticeable change is to the Fulfillment Outbound API’s address schema: the city field is no longer mandatory. This tweak directly addresses a frequent validation problem for sellers shipping to Japan, where many addresses omit a city name. By making the city attribute optional, Amazon removes a common source of 400‑error responses and streamlines order creation for Japanese marketplaces.
Key Points
- City field optional — The city property in the address object is now optional, eliminating “Missing city” validation errors.
- Japanese marketplace focus — The change targets the JP marketplace, where city names are often omitted from shipping addresses.
- Error reduction — Sellers who previously faced “Missing city” errors will no longer receive them when shipping to Japan.
- Backward compatibility — Existing code that includes a city value continues to work without modification.
- Documentation update — The API reference now lists city as optional in the address schema, with updated examples.
How the Update Works
- Address schema change — The address object now defines city as an optional string.
Example: A seller can send{ "addressLine1": "1‑2‑3 Shibuya", "stateOrRegion": "Tokyo" }without a city field. - Request validation — The API accepts the request and processes it normally, even if the city key is missing.
Example: A fulfillment order to a Japanese address lacking a city will be accepted and queued for shipment. - Response handling — The API returns the same success or error messages as before, but without “Missing city” errors.
Example: A seller receives a 200 OK response instead of a 400 error for the same payload. - Legacy code — Code that previously set city to an empty string or placeholder remains valid; no changes are required. : is still accepted and treated as “no city”.
Analysis & Recommendations
Why This Matters
Sellers shipping to Japan will no longer receive 400 errors when city is omitted, cutting support tickets and speeding fulfillment. The change applies only to the JP marketplace and preserves backward compatibility.
Key Takeaways
- City field now optional in Fulfillment Outbound API address schema (April 2023 release).
- Eliminates ‘Missing city’ 400 errors for Japanese shipments.
- Existing city data remains valid; no code changes required.
- Documentation updated to list city as optional in the address schema.
Recommended Actions
- →Update integration tests to include Japanese addresses without a city field, e.g., {"addressLine1":"1‑2‑3 Shibuya","stateOrRegion":"Tokyo"}.
- →Remove hard‑coded city placeholders for JP shipments in order creation code.
- →Set up a log filter for ‘Missing city’ errors in fulfillment logs and confirm zero occurrences after the update.
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!