--- title: 2023-01 release notes description: Update your app from API version 2022-10 to 2023-01. api_name: release-notes source_url: html: 'https://shopify.dev/docs/api/release-notes/previous-versions/2023-01' md: 'https://shopify.dev/docs/api/release-notes/previous-versions/2023-01.md' --- ExpandOn this page * [Breaking changes](https://shopify.dev/docs/api/release-notes/previous-versions/2023-01.md#breaking-changes) * [Graph​QL Admin API changes](https://shopify.dev/docs/api/release-notes/previous-versions/2023-01.md#graphql-admin-api-changes) * [Graph​QL Storefront API changes](https://shopify.dev/docs/api/release-notes/previous-versions/2023-01.md#graphql-storefront-api-changes) * [REST Admin API changes](https://shopify.dev/docs/api/release-notes/previous-versions/2023-01.md#rest-admin-api-changes) # 2023-01 release notes Note We're no longer publishing API release notes. Instead, you can find the latest updates on Shopify APIs in our [developer changelog](https://shopify.dev/changelog). You can filter updates by area. For example, you can filter API updates by the API name and version, such as GraphQL Admin API changes in version 2025-04. | Release date | Date version is no longer supported | | - | - | | January 1, 2023 | January 1, 2024 | **What's new in 2023-01** The following features were added in version 2023-01 of Shopify's APIs. Highlights from the GraphQL Admin API changes: * Asynchronous queries in the Segmentation API * Delivery settings support for more locations * Duplicate and delete Product asynchronously * Fulfillment API updates * Inventory States API * Metafields available on Company and CompanyLocation * Metaobjects API * ShopifyQL API * New Webhook topics added and updated Highlights from the GraphQL Storefront API changes: * Metaobjects API * StoreAvailability can now be searched based on proximity Highlights from the REST Admin API changes: * B2B Order Import * New credit card fields added to Transaction *** ## Breaking changes These changes require special attention. If your app uses these API resources, and you don’t adjust your usage of the resources according to the following instructions, then your app might break when you update to this API version. ### Checkout​Profiles sort order has changed The new `EditedAt` field has been added to the [`CheckoutProfile`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/CheckoutProfile) object. CheckoutProfiles are now sorted by the `EditedAt` field instead of `updatedAt`. ### The line​Item field on Fulfillment​Order​Line​Item has been deprecated The `lineItem` field on [FulfillmentOrderLineItem](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/FulfillmentOrderLineItem) has been deprecated. The order line item associated with a `FulfillmentOrderLineItem` shouldn't be used to determine what to fulfill. Use the `FulfillmentOrderLineItem` and [`FulfillmentOrder`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/FulfillmentOrder) objects instead. ### Removal of error code from Location​Deactivate​User​Error​Code The error coded `INVALID` has been removed from [`LocationDeactivateUserErrorCode`](https://shopify.dev/docs/api/admin-graphql/2023-01/enums/LocationDeactivateUserErrorCode). ### Shop billing address uses a new Shop​Address type The `billingAddress` field on [`Shop`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/Shop) uses a new [`ShopAddress`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/ShopAddress) type instead of `MailingAddress`. Since `Shop.billingAddress` never returns non-null first or last names, these fields have been marked as deprecated on the new `ShopAddress` type. You should stop requesting those fields as they will be removed in a later version. *** ## Graph​QL Admin API changes The following are all the changes currently introduced in the 2023-01 version of the GraphQL Admin API. ### Access controls for app metafields You can optionally specify an `access` setting when you create or update metafield definitions via the API. This new setting will allow you to control who else can access the metafields under your definition via the Admin API. Note that this setting can only be set when the definition is in your own [reserved namespace](https://shopify.dev/). Possible settings you can use are `PRIVATE` (no one else can access the metafields), `MERCHANT_READ` (the merchant has read-only access to the metafields via the Shopify admin UI), and `MERCHANT_READ_WRITE` (the merchant can view and edit the metafields via the Shopify admin UI). Learn more about access controls in our [documentation](https://shopify.dev/). ### Asynchronous queries in the Segmentation API Starting in this verion, some queries could be processed and returned asynchronously based on complexity and the amount of shop data. Most queries will continue to be evaluated synchronously. This breaking change allows you to build the best possible user experience as we introduce more complex filters in Segmentation. Asynchronous queries should revolve within 5 seconds but some queries might take up to 1-2 minutes or even longer. To get up to date, make sure you are handling responses returning an error code because the query must be processed asynchronously. You can follow our [migration guide](https://shopify.dev/docs/apps/build/marketing-analytics/customer-segments/migrate-to-async-queries). Learn more about building for asynchronous queries in our [developer documentation](https://shopify.dev/docs/apps/build/marketing-analytics/customer-segments/manage#query-a-list-of-segment-members) or visit our [API forum for questions](https://community.shopify.com/c/shopify-apis-and-sdks/segmentation-api-now-available/m-p/1465812?). ### Automated collections with metafield conditions Automated [`collections`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/Collection) now support metafield conditions. These are controlled by enabling the respective metafield definition on your settings page. ### New Edited​At field for Checkout​Profile #### Breaking The new `EditedAt` field has been added to the [`CheckoutProfile`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/CheckoutProfile) object. CheckoutProfiles are now sorted by the `EditedAt` field instead of `updatedAt`. ### Due on Fulfillment is now a Payment​Terms​Type A new value of `FULFILLMENT` is now available on the [`PaymentTermsType`](https://shopify.dev/docs/api/admin-graphql/2023-01/enums/PaymentTermsType) enum. With this change, apps can create and update orders and draft orders with payment terms whose due date will be set upon fulfillment of the order. ### Duplicate and delete Product asynchronously New mutations, [`productDuplicateAsync`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/productDuplicateAsync) and [`productDeleteAsync`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/productDeleteAsync), have been added to allow you to asynchronously duplicate and delete products that have a high number of variants that are stocked at several locations. The existing mutations [`productDuplicate`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/productDuplicate) and [`productDelete`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/productDelete) may time out for these *larger* products. **New mutations**: * [`productDuplicateAsync`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/productDuplicateAsync) * [`productDeleteAsync`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/productDeleteAsync) ### The line​Item field on Fulfillment​Order​Line​Item has been deprecated #### Breaking The `lineItem` field on [FulfillmentOrderLineItem](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/FulfillmentOrderLineItem) has been deprecated. The order line item associated with a `FulfillmentOrderLineItem` shouldn't be used to determine what to fulfill. Use the `FulfillmentOrderLineItem` and [`FulfillmentOrder`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/FulfillmentOrder) objects instead. ### Fulfillment Events can be created [`FulfillmentEvents`](https://shopify.dev/api/admin-graphql/2023-01/objects/FulfillmentEvent) can now be created through the API using the [`fulfillmentEventCreate`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/fulfillmentEventCreate) mutation. This was previously only possible through the REST Admin API. **New mutations**: * [`fulfillmentEventCreate`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/fulfillmentEventCreate) ### Fulfillment​Order​Line​Items can be marked as being ready for pickup Using the new [`fulfillmentOrderLineItemsPreparedForPickup`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/fulfillmentOrderLineItemsPreparedForPickup) mutation, line items associated with a [FulfillmentOrder](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/FulfillmentOrder) can be marked as being ready for pickup by the customer. **New mutations**: * [`fulfillmentOrderLineItemsPreparedForPickup`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/fulfillmentOrderLineItemsPreparedForPickup) ### Fulfillment orders can now be accessed from Query​Root You can now access fulfillment orders from `QueryRoot.fulfillmentOrders` in addition to the existing `Shop.fulfillmentOrders` connection, which is now deprecated. To learn more, take a look at our documentation on [fulfillment orders](https://shopify.dev/docs/api/admin-graphql/2023-01/connections/FulfillmentOrderConnection#connection-fulfillmentorderconnection-edges) ### Changes to the `metafieldsSet` mutation The [`metafieldsSet`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/metafieldsSet) mutation has been updated so that the `MetafieldsSetInput.type` field can be omitted only when the metafield already has corresponding Metafield definitions. Additionally, the mutation is now atomic and will not persist changes if any errors are encountered. ### Orders can be sorted by destination The [`orders`](https://shopify.dev/docs/api/admin-graphql/2023-01/queries/orders) query can now be sorted by destination. Using this sort key will return Orders by country, then by zone (e.g. state, province, etc.) and finally by city. ### Inventory States API New mutations have been added that allow the editing for inventory quantities at a specific location, as well as quantities reserved and on hold. New queries are also available to retrieve quantities for every state as well. For more information, check out the documentation on [Inventory States](https://shopify.dev/). **New queries**: * [`inventoryLevel`](https://shopify.dev/docs/api/admin-graphql/2023-01/queries/inventoryLevel) * [`inventoryItem`](https://shopify.dev/docs/api/admin-graphql/2023-01/queries/inventoryItem) **New mutations**: * [`inventorySetOnHandQuantities`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/inventorySetOnHandQuantities) * [`inventoryAdjustQuantities`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/inventoryAdjustQuantities) * [`inventoryMoveQuantities`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/inventoryMoveQuantities) ### Metafields are now available on Company and Company​Location Metafields can now be added to [`Company`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/Company) and [`CompanyLocation`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/CompanyLocation) as part of B2B. Addtionally, a subset of mutations are now available for use asynchronous usage via [BulkOperation](https://shopify.dev/docs/api/usage/bulk-operations/). ### Querying on Metafields has been simplified When querying on [`Metafield`](https://shopify.dev/docs/api/admin-graphql/2023-01/queries/metafield), you can now optionally supply the `key` argument in the format of `namespace.key`. You will also be able to optionally supply the `keys` argument to the `metafields` connection as a list of strings in the same format. The key returned will also be in the format of `namespace.key`. ### Removal of SMS Templates as a translatable resource `SMS_Templates` has been removed from the [`TranslatableResourceType`](https://shopify.dev/docs/api/admin-graphql/2023-01/enums/TranslatableResourceType) enum. The corresponding mutations and queries will no longer accept SMS Template IDs: * [`translationsRemove`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/translationsRemove) * [`translationsRegister`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/translationsRegister) * [`translatableResource`](https://shopify.dev/docs/api/admin-graphql/2023-01/queries/translatableResource) * [`translatableResourcesByIds`](https://shopify.dev/docs/api/admin-graphql/2023-01/queries/translatableResourcesByIds) ### Delivery settings support for more locations We've introduced a few changes that will improve managing delivery settings for merchants with a high number of locations: * A new and more efficient way of managing locations associated with groups within a delivery profile. Instead of using the [locations](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/DeliveryLocationGroup#connection-deliverylocationgroup-locations) field, which always requires the full list of locations to have in a location group, you can now use the [locationsToAdd](https://shopify.dev/docs/api/admin-graphql/2023-01/input-objects/DeliveryProfileLocationGroupInput#field-deliveryprofilelocationgroupinput-locationstoadd) and [locationsToRemove](https://shopify.dev/docs/api/admin-graphql/2023-01/input-objects/DeliveryProfileLocationGroupInput#field-deliveryprofilelocationgroupinput-locationstoremove) fields to specify exactly the locations you want to adjust from a group. * A new argument `locationGroupId` has been added to [profileLocationGroups](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/DeliveryProfile#field-deliveryprofile-profilelocationgroups) field. You can use this to query a specific [`location group`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/DeliveryLocationGroup#field-deliverylocationgroup-id) and fetch its paginated locations more efficiently. * A new [`unassignedLocationsPaginated`](https://shopify.dev/api/admin-graphql/2023-01/objects/DeliveryProfile#connection-deliveryprofile-unassignedlocationspaginated) field has been added to [`DeliveryProfile`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/DeliveryProfile). You can use this field to query locations that are not assigned to a delivery profile in a more efficient way. * A new [`locationsCount`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/DeliveryLocationGroup#field-deliverylocationgroup-locationscount) field has been added to the [DeliveryLocationGroup](https://shopify.dev/api/admin-graphql/2023-01/objects/DeliveryLocationGroup) object. * The Local Pickup API is now stable view the [`locationLocalPickupEnable`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/locationLocalPickupEnable) and [`locationLocalPickupDisable`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/locationLocalPickupDisable) mutations. ### Draft​Order and Order fields added to Payment​Terms object When querying for a [`PaymentTerms`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/PaymentTerms) object, you now have access to both the associated [`DraftOrder`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/DraftOrder) or [`Order`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/Order). ### Fulfillment Service Creation will now throw errors without opt-in enabled When trying to create a [`Fulfillment Service`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/FulfillmentService) using the [`fulfillmentServiceCreate`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/fulfillmentServiceCreate) mutation, and error will be returned if the `fulfillment_orders_opt_in` field is not set to `true` in the parameters. Similarly, when trying to update a Fulfillment Service using the [`fulfillmentServiceUpdate`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/fulfillmentServiceUpdate) mutation, an error will be returned if the fulfillment service being updated has `fulfillment_orders_opt_in` set to `false` and the update request does not promote `fulfillment_orders_opt_in` to `true`. Learn how to [migrate to fulfillment orders](https://shopify.dev/docs/apps/build/orders-fulfillment/migrate-to-fulfillment-orders) how to [fulfill fulfillment orders as a service app](https://shopify.dev/docs/apps/build/orders-fulfillment/fulfillment-service-apps/build-for-fulfillment-services). ### Create fulfillment events You can now create [`FulfillmentEvents`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/FulfillmentEvent) using the GraphQL Admin API using the [`fulfillmentEventCreate`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/fulfillmentEventCreate) mutation. This was previously only possible using the REST Admin API. **New mutations**: * [`fulfillmentEventCreate`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/fulfillmentEventCreate) ### Fulfillment order holds can be flagged with an external id The [`FulfillmentOrderHoldInput`](https://shopify.dev/docs/api/admin-graphql/2023-01/input-objects/FulfillmentOrderHoldInput) has a new field called `externalId`. This can be used to track states within your own application on why a fulfillment order has been placed on hold and when it needs to be released. To learn more about the fulfillment order API see the [fulfillment order object documentation](https://shopify.dev/api/admin-graphql/2023-01/objects/FulfillmentOrder#field-fulfillmentorder-fulfillmentHolds). ### Metaobjects API We are introducing a new Admin API that allows the creation of custom data structures called [`Metaobjects`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/Metaobject). Similar to metafields, which enable custom fields to be associated with core resources within Shopify, Metaobjects provide a way to create and associate entirely new data models. The API includes: * Defining objects with granular access control on how merchants and apps can interact with them. * Creating entries of custom defined objects and making them publishable to storefronts. ### Removal of the error code when deactivating Location #### Breaking We have removed the error code `INVALID` from `LocationDeactivateUserErrorCode`. This error code was never returned * [`inventorySetOnHandQuantities`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/inventorySetOnHandQuantities) * [`inventoryAdjustQuantities`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/inventoryAdjustQuantities) * [`inventoryMoveQuantities`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/inventoryMoveQuantities) ### Release holds on multiple fulfillment orders You can now use the [`fulfillmentOrdersReleaseHolds`](https://shopify.dev/docs/api/admin-graphql/unstable/mutations/fulfillmentOrdersReleaseHolds) mutation to release holds on multiple fulfillment orders in a single request. This will allow developers to reduce the number of individual requests used to complete bulk fulfillment actions with their apps. **New mutations**: * [`fulfillmentOrdersReleaseHolds`](https://shopify.dev/docs/api/admin-graphql/unstable/mutations/fulfillmentOrdersReleaseHolds) ### Reengagement Automations You can now integrate marketing automation flow actions inside of our reengagement marketing automation workflows. These actions include: * Abandoned checkout * Abandoned cart * Abandoned product browse To learn more about reengagement automations, check out or [blog post](https://www.shopify.com/ca/blog/reengagement-automations). ### Selling Plan Group Limit Increase The [limit on the number of associated Selling plans](https://shopify.dev/docs/api/admin-graphql/2023-01/enums/SellingPlanGroupUserErrorCode#value-sellingplancountupperbound) for [Selling Plan Groups](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/sellingplangroup) has been increased from 20 to 31. We recommend paginating all queries on a Selling Plan Group's Selling Plans, rather than relying on this fixed limit. Learn more about Selling Plan Groups by referring to the [purchase options documentation](https://shopify.dev/docs/apps/build/purchase-options). ### Send payment reminders via email You can use the new [`paymentReminderSend`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/paymentReminderSend) mutation to send payment reminder emails to customers. **New mutations**: * [`paymentReminderSend`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/paymentReminderSend) ### Mutation to change Shipping Packages has been updated The [`shippingPackageUpdate`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/shippingPackageUpdate) mutation has been updated so that `shippingPackage` is a required argument. `shippingPackage` is a set of attributes that describes a shipping package, including: `weight`, `dimensions`, `name`, `default` and `type`. ### Shopify​QL API is now available The [ShopifyQL API](https://shopify.dev/docs/api/shopifyql) is now available to query analytical data from merchant stores to create reporting apps that provide business insights for merchants. **New queries**: * [shopifyqlQuery](https://shopify.dev/docs/api/admin-graphql/2023-01/queries/shopifyqlQuery) ### Shop Policy supports Contact Information The [`ShopPolicyType`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/ShopPolicyType) has been updated to include a new value of `CONTACT_INFORMATION`. This policy is intended to allow users to add regulatory information, including a Value-Added Tax (VAT) and trade number. ### Shop Resource Feedback The new mutation [`shopResourceFeedbackCreate`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/shopResourceFeedbackCreate) allows clients to create resource feedback to let a merchant know what steps are needed to ensure it is set up correctly. **New mutations**: * [`shopResourceFeedbackCreate`](https://shopify.dev/docs/api/admin-graphql/2023-01/mutations/shopResourceFeedbackCreate) ### Shop billing address uses a new Shop​Address type #### Breaking The `billingAddress` field on [`Shop`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/Shop) uses a new [`ShopAddress`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/ShopAddress) type instead of `MailingAddress`. Since `Shop.billingAddress` never returns non-null first or last names, these fields have been marked as deprecated on the new `ShopAddress` type. You should stop requesting those fields as they will be removed in a later version. ### Payment ID has been added to Order​Transaction A new `paymentId` field has been added to [OrderTransaction](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/OrderTransaction). This unique ID is now sent to payment providers when a customer pays at checkout. This ID can be used to match order information between Shopify and payment providers. An Order can have more than one Payment ID. It only includes successful or pending payments. It does not include captures and refunds. ### Webhook topics added for Locations Dedicated webhook topics have been introduced that will be sent out whenever a location is deactivated (`locations/deactivate`) or when a deactivated location is re-activated (`locations/activate`). Currently location deactivation and activation webhooks are lumped under the `locations/update` webhook topic. Webhooks on the `locations/update` topic will also continue to be sent out for location activation/deactivation, in case any clients are already consuming these `update` notifications for this purpose. It is recommended that such clients switch over to consuming the dedicated `locations/activate` and `locations/deactivate` topics, as eventually lumping them together with `locations/update` webhooks will be deprecated in a future API version. **New webhooks**: * `locations/deactivate` * `locations/activate` ### Webhook topics updated for fulfillment orders Webhooks related to Fulfillment Orders have been added and updated. For a full list of topics, refer to the documentation on [Fulfillment Order Webooks](https://shopify.dev/docs/apps/build/orders-fulfillment/fulfillment-service-apps#webhooks). ### Webhooks added for returns apps [Returns apps](https://shopify.dev/docs/apps/build/orders-fulfillment/returns-apps) can now give merchants greater visibility into critical returns data across platforms, and help them manage orders more efficiently. Returns apps can automate the return management process by taking actions on behalf of merchants. These actions can include the following: * Creating and canceling returns * Approving or declining return requests * Managing reverse fulfillment orders and deliveries, including creating a reverse delivery with shipping information, and disposing or restocking items * Issuing refunds * Closing and reopening returns We've also added new webhooks that your app can use to listen for events related to returns, refunds, reverse fulfillment orders, and reverse deliveries. Check out our documentation on [returns apps](https://shopify.dev/docs/apps/build/orders-fulfillment/returns-apps) for a full list. ### Webhook topic for when a payment schedule is due You can subscribe to the new [`PAYMENT_SCHEDULES_DUE`](https://shopify.dev/docs/api/admin-graphql/2023-01/enums/WebhookSubscriptionTopic#value-paymentschedulesdue) webhook topic to be notified of when a [`PaymentSchedule.due_at`](https://shopify.dev/docs/api/admin-graphql/2023-01/objects/PaymentSchedule) date is reached. ### Webhooks added for subscription billing cycles We have added webhooks for the [`subscription billing cycles API`](https://shopify.dev/docs/apps/build/purchase-options/subscriptions/billing-cycles). The following are topics now available: * `subscription_billing_cycle_edits_create` * `subscription_billing_cycle_delete` * `subscription_billing_cycle_edits_update` We have also added new error codes to [`BillingAttemptUserErrorCode`](https://shopify.dev/docs/api/admin-graphql/2023-01/enums/BillingAttemptUserErrorCode) and [`SubscriptionBillingCycleUserError`](https://shopify.dev/docs/api/admin-graphql/2023-01/enums/SubscriptionBillingCycleErrorCode). *** ## Graph​QL Storefront API changes The following are all the changes currently introduced in the 2023-01 version of the GraphQL Storefront API: ### Metaobjects API You can now access custom data structures called [`Metaobjects`](https://shopify.dev/docs/api/storefront/2023-01/objects/Metaobject) using the Storefront API. Similar to metafields, which enable custom fields to be associated with core resources in Shopify, metaobjects provide a way to associate entirely new data models. You can access entries of custom defined objects that were created through the Admin API and publish them to storefronts. ### New tag field has been added to the Product​Filter object The [`ProductFilter`](https://shopify.dev/docs/api/storefront/2023-01/input-objects/ProductFilter) object has a new `tag` field, which can be used for filtering if tags are enabled as a filter setting on the shop. ### Store​Availability can now be searched based on proximity You can now use the `near` parameter to search [`StoreAvailability`](https://shopify.dev/docs/api/storefront/2023-01/objects/StoreAvailability) by proximity, via Storefront API. This parameter uses the [`GeoCoordinateInput`](https://shopify.dev/docs/api/storefront/2023-01/input-objects/GeoCoordinateInput). *** ## REST Admin API changes The following are all the changes currently introduced in the 2023-01 version of the REST Admin API. ### B2B Order Import Merchants with B2B enabled on their stores can now [`Import Orders`](https://shopify.dev/docs/apps/build/b2b/import-orders) in a B2B context. ### New credit card fields added to Transaction New fields have been added to the `payment_details` property on [`Transaction`](https://shopify.dev/docs/api/admin-rest/2023-01/resources/transaction). **New fields**: * `credit_card_name`: The holder of the credit card. * `credit_card_wallet`: The wallet type where this credit card was retrieved from. * `credit_card_expiration_month`: The month in which the credit card expires. * `credit_card_expiration_year`: The year in which the credit card expires. ### Payment ID has been added to Order​Transaction A new `paymentId` field has been added to [Transaction](https://shopify.dev/docs/api/admin-rest/2023-01/resources/transaction). This unique ID is now sent to payment providers when a customer pays at checkout. This ID can be used to match order information between Shopify and payment providers. An Order can have more than one Payment ID. It only includes successful or pending payments. It does not include captures and refunds. *** * [Breaking changes](https://shopify.dev/docs/api/release-notes/previous-versions/2023-01.md#breaking-changes) * [Graph​QL Admin API changes](https://shopify.dev/docs/api/release-notes/previous-versions/2023-01.md#graphql-admin-api-changes) * [Graph​QL Storefront API changes](https://shopify.dev/docs/api/release-notes/previous-versions/2023-01.md#graphql-storefront-api-changes) * [REST Admin API changes](https://shopify.dev/docs/api/release-notes/previous-versions/2023-01.md#rest-admin-api-changes)