Overview

Amazon has refreshed Orders API version 0 to deliver a new ExtendedFields object for shipments destined for Brazil. The change is live now and adds separate fields for street number, street name, complement and neighborhood. Sellers who ship to Brazilian customers must modify their integrations to capture these elements, or risk address‑related fulfillment problems.

Key Points

• ExtendedFields introduced — The response payload now carries a nested object that isolates Brazil‑specific address parts.
• Four granular data points — Street number, street name, complement (e.g., apartment or suite) and neighborhood are returned for every order with a Brazilian destination.
• Selective appearance — Existing address fields stay unchanged; the new object is included only when the country code equals BR.
• Carrier‑friendly validation — Sellers can now compare each component against the formatting rules of local carriers such as Correios and Jadlog, cutting the odds of shipment rejections.
• Schema‑update requirement — Failure to map the new fields will leave downstream systems with incomplete address records, potentially triggering delivery delays.
• No impact on non‑Brazil orders — Orders shipping to other countries continue to use the original address schema, preserving backward compatibility for mixed‑region sellers.

How the ExtendedFields Feature Works

1. API call detection — When a seller issues GET /orders/v0/orders and the order’s shippingAddress.countryCode is BR, Amazon injects an extendedFields node beneath the existing shippingAddress.
   • Example: Order #987654 returns "countryCode":"BR" together with "extendedFields":{...} in the JSON payload.
2. Field population – Amazon fills the four sub‑fields directly from the buyer’s checkout entry. Each field is a plain‑text string limited to 100 characters, matching the exact format required by Brazilian postal services.