Starting with Customer Account API version 2026-10, customer address inputs and objects support . The existing field is deprecated but remains fully supported, so current integrations continue working without interruption. Developers should migrate to when adopting API version 2026-10.
What changed
The input object and object now include .
Use when creating, updating, or reading a customer address. It uses the enum and accepts ISO 3166-1 alpha-2 country codes such as US or CA.
The existing field is marked as deprecated in API version 2026-10.
has not been removed. Existing queries and mutations that use it continue to work as before, including integrations using older API versions.
has not been removed. Existing queries and mutations that use it continue to work as before, including integrations using older API versions.
Note: <code><span class="PreventFireFoxApplyingGapToWBR">territory<wbr/>Code</span></code> has not been removed. Existing queries and mutations that use it continue to work as before, including integrations using older API versions.
If both fields are supplied in an address input, takes precedence.
Who’s affected
This change affects apps using the Customer Account API to create, update, or read customer addresses.
Apps using API version 2026-10 or later can use and will see marked as deprecated. Apps using API version 2026-07 or earlier are unchanged and can continue using .
There is no immediate disruption for existing clients, and no removal version has been announced.
Why this matters
aligns customer addresses with the country-code terminology and strongly typed enum used elsewhere in Shopify APIs. This provides clearer input requirements and avoids ambiguity between country and territory terminology.
What to do
When adopting Customer Account API version 2026-10:
- Check customer address queries and mutations for uses of
. - Replace those uses with
. - Supply ISO 3166-1 alpha-2 values, such as
US, instead of alpha-3 or numeric values such asUSAor840. - Test customer address creation, updates, and reads against API version 2026-10.
No immediate change is required for apps that remain on an earlier API version. continues to work in version 2026-10, but migrating prepares integrations for its possible removal in a future API version.