Removing marketCurrencySettingsUpdate mutation

As of GraphQL Admin API version 2027-01, the marketCurrencySettingsUpdate mutation is removed, along with the MarketCurrencySettingsUpdatePayload, MarketCurrencySettingsUserError, and MarketCurrencySettingsUserErrorCode types. The mutation already returns an error for every request, so this removes an endpoint that can no longer be used.

What's changed

In API version 2027-01, the Admin GraphQL API removes:

• marketCurrencySettingsUpdate
• MarketCurrencySettingsUpdatePayload
• MarketCurrencySettingsUserError
• MarketCurrencySettingsUserErrorCode

The mutation was deprecated when Markets Home launched in version 2025-04. Since 2025-04 became inaccessible, every call has returned the UNIFIED_MARKETS_ENABLED user error instead of updating anything.

To create or update market currency settings, use marketCreate and marketUpdate. Both accept currency settings directly, so you don't need a separate call.

Versions 2026-10 and earlier are unaffected and keep the mutation for the remainder of their supported lifetime.

Who's affected

You're affected if your app still calls marketCurrencySettingsUpdate. Those calls aren't updating currency settings today, and in 2027-01 they'll fail differently: the field no longer exists, so the request is rejected at validation.

You're not affected if you already use marketCreate and marketUpdate to manage market currency settings.

Action required

Replace any remaining calls to marketCurrencySettingsUpdate:

1. Use marketCreate when you create a market and its currency settings.
2. Use marketUpdate when you change the currency settings of an existing market.
3. Pass the same currency settings directly in the marketCreate or marketUpdate input.

Because a request that references a removed field fails validation, an unmigrated call in 2027-01 fails the entire request rather than returning a user error for one mutation.

Related docs

• marketCreate mutation
• marketUpdate mutation
• Market object