Order Update Phone Field Public
As of Admin API 2026-01, the phone field is now publicly available in the orderUpdate mutation's OrderInput . This field allows developers to update the customer phone number for an order, overwriting the existing phone number. This change brings parity with the REST API, which already supports updating the phone field through the Order resource .
Also shipped Nov 1, 2025Shopify in November 2025 →
Agent tools adapt to Grok 4.1 Fast models and tool prices dropped
- You can now use Grok 4.1 Fast models with the agent tools, check out the documentation of agent tools to get started. The price of agent tools drops by up to 50% to no more than $5 per 1000 successful calls, see the new prices at the pricing page.
Files API is generally available
You can now upload files and use them in chat conversations with the Files API. For more details, check out our guide on Files.
Grok 4.1 Fast is available in Enterprise API
You can now use Grok 4.1 Fast in the xAI Enterprise API. For more details, check out our blogpost.
New Tools Available
- Collections Search Tool: You can now search through uploaded knowledge bases (collections) in chat conversations via the API. For more details, check out the docs. Remote MCP Tools: You can now use tools from remote MCP servers in chat conversations via the API. For more details, check out the docs.
feldera 0.174.0
- Fix user auth session not automatically refreshed [docs] remove broken link
More from Shopify developer platformEvery Shopify developer platform release →
New Queries for Bulk Operations
We've introduced new GraphQL queries to help you retrieve and manage bulk operations in the Admin API. What's Changed Here's an overview of the updates: New Bulk Operations Retrieval Queries We have added two new queries for accessing your bulk operations: bulkOperations : A connection-based query that returns a paginated list of all your bulk operations...
Support metafield and metaobject standards in Declarative Custom Data Definitions
We now support enabling and referencing standard metafield and metaobject definitions through an app’s TOML file. Key benefits include: Standard metafield and metaobject definitions can be enabled through TOML, and managed through the app dev or app deploy command.
The `cartDiscountCodeUpdate` mutation now requires the `discountCodes` field
As part of the GraphQL Storefront API 2026-01 release , the cartDiscountCodesUpdate mutation now requires the discountCodes argument to be included. Previously, mutation calls without the discountCodes argument were allowed, but would not actually modify the cart in any way.
Built for Shopify apps get priority visibility across the Shopify App Store
Built for Shopify (BFS) apps are now featured more prominently across key App Store surfaces, helping merchants discover them faster. What's new: Homepage spotlight: BFS now appears in the featured header section of the App Store homepage , giving certified apps maximum exposure to browsing merchants.
Carrier Service API now includes order totals and customer tags
The Carrier Service API callback payload now includes order totals and customer tags. This enhancement enables more effective shipping rate calculations by taking into account the order value and customer segments. New Payload Fields: order_totals subtotal_price : The total price of all items in the cart before discounts.
Bulk operations group objects default changed to `false`
We have optimized the output of bulk operations in the GraphQL Admin API to enhance speed and reliability. What's Changed Bulk Queries ( bulkOperationRunQuery ) The groupObjects argument now defaults to false . Grouping objects can slow down operations and increase failure rates, especially with large datasets.
tax_summaries/create webhook and taxSummaryCreate mutation now available
As of the 2026-01 API version, the tax_summaries/create webhook and taxSummaryCreate mutation are available for Tax Partner Apps. What's New The taxSummaryCreate mutation enables apps to request the generation of tax summaries for orders. The tax_summaries/create webhook is triggered by events that may affect tax liability, such as fulfillments and refunds.
Optional location inputs for inventory transfers
You can now create inventory transfers without specifying an origin or destination location. Previously, the InventoryTransferCreateAsReadyToShip mutation required both origin and destination location IDs. Now, these inputs are optional. This change supports workflows where the transfer's origin or destination is unknown at creation time.