Developer changelog

On September 17, 2018, we'll be changing how we display fraud risk information on the order page in the Shopify admin. This will also impact how risk information is exposed in the Order Risk resource.

We've shipped a change that removes inventory validation from the checkoutCreate mutation in the Storefront API. This is part of our effort to remove the risk of bots and crawlers getting access to inventory information on stores.

We're adding a highly requested new parameter to the PriceRule API: allocation_limit. This new parameter represents the number of times a discount can be applied to the cart, if eligible. This additional parameter will only be available for Buy X Get Y discount types.

We've started removing all HTTP proxies on the platform. You should transition your app to create HTTPS proxies instead.

Currently, Admin API requests to locked stores return a 420 status code. As of Thursday, August 30th, this response will change to 423. We're pushing this change to reduce ambiguity around the 420 response code and make sure our responses are as accurate as possible.

In May, we shared communications regarding the European Union’s new General Data Protection Regulation (“GDPR”) and what it means for merchants and developers on our platform.

On July 19, 2018, Shopify will be releasing v2.5 POS Android and v4.8 POS iOS, which means that all merchants will be able to view your POS apps on their iOS and Android phones and tablets. Make sure to test the design and functionality of your POS apps on iOS and Android phones and tablets prior to the public release of v2.5 POS Android and v4.8 POS iOS.

Shopify is introducing an important change to the Order resource to help preserve the trust that merchants have when using third-party apps.

Shopify is preparing to let merchants track inventory across multiple locations. As part of this change, on July 1, 2018, apps will no longer be able to create fulfillments without specifying a location, or be able to set inventory on the Product and Product Variant resources. All apps that create fulfillments or manage inventory will need to be updated by July 1 to remain functional on shops that track inventory across multiple locations.

To help you better identify multiple fulfillments for a single order, responses from the Fulfillment resource endpoint will now include a name property.

As part of our commitment to providing a safe and secure platform, as of June 20, 2018, Shopify no longer support the outdated TLS 1.0 and 1.1 security protocols. Your apps will have to connect to our APIs using TLS 1.2.

If you missed it at Unite this year, we've exposed line-level discount information on the Order API through a new discount_applications property. You can use this property to account more accurately for when discounts are added to orders.

We've changed the error messages returned in REST responses to include the attribute name, which matches what we currently return in GraphQL.

Partners with POS Android v2.4.8 and POS iOS v4.6 can now beta test their POS apps on Shopify development stores.

In response to the General Data Protection Regulation (GDPR), we've introduced some important changes to our platform to help you properly handle the privacy and security of customers’ personal information.

Shopify Plus Partners can now create Shopify Plus sandbox stores. Sandbox stores includes most of the features that are available on the Shopify Plus plan so you can learn how to build on Shopify Plus and create demos for prospective merchants.

In 2013, we started to transition ID columns from 32-bit to 64-bit in order to handle the large amount of data we process. Shop IDs have now exceeded the 32-bit threshold. If your app processes the shop ID from an API call, you need to make sure that your data type can handle 64-bit integers.

We're introducing a new prerequisite_quantity_range property on PriceRule! You can use this to let merchants selll products with discounts that require a minimum quantity of items.

In the coming weeks, Shopify will release a new feature: pre-launch pages. This feature is a static “coming soon” style page that acts as an interactive placeholder while a merchant works on their store and prepares it for launch.

On March 1, 2018, Shopify will prevent cancellations of fulfilled or partially-fulfilled orders. Post-fulfillment order cancellations are rare and can lead to confusing fulfillment states and discrepancies in reporting. Thus, attempting to cancel a fulfilled or partially fulfilled order using the cancel endpoint of the Order resource will return an error.

Today we're launching the new AccessScope resource, which allows you to query a merchant's shop for the list of permissions associated to your app. Using this functionality you can easily manage scopes across your various users' shops.

We’re introducing a new plan type to help you identify Shopify employees installing your apps, giving you the option to allow them to use the app for free or at a discounted fee. This helps them better understand the value your app can bring to merchants.

The PriceRule resource now includes the prerequisite_customer_ids property, which can be used to create discounts for specific customers. See the PriceRule reference documentation for more details on how to use it.

When we launched our JS Buy and Mobile Buy SDKs a couple of years ago, we designed the system so that developers would manage their access tokens and any mobile settings through the Buy Button and Mobile App sales channels. As use of these SDKs has grown, we wanted to make it easier for partners and developers to track which products were being sold through each storefront, and have access to reports that more accurately communicate the performance of each.

We are introducing a number of improvements to how Shopify delivers webhooks.

As of December 5, 2017, inventory_quantity and inventory_policy fields accessed through a JSON Liquid filter are deprecated. The JSON filter will not output those fields for shops created after that date.

On December 4, 2017, we will be removing the web_processing_url parameter from the Checkout resource. The web_processing_url was never documented and never intended to be consumed by Shopify applications. This does not remove any functionality from the API, since the web_url parameter remains and continues to provide the same functionality.

On November 1, Shopify will be sunsetting the Bulk Discounts app. Merchants can continue to use it without any interruptions until then and their existing discounts remain active in Shopify.

Themes in the Shopify Theme Store no longer include a page setting type on the homepage by default. The richtext setting type will be the main method to add content to the homepage. Any apps that require merchants to install code to display content on the homepage need to update their docs and setup to provide an easier installation. The page setting type is still available for custom development.

The Shopify Admin API now supports bulk discount code creation. With the introduction of bulk discounts, we will allow a single price rule to be associated with multiple discount codes. Therefore, an app that wishes to create multiple discount codes for a single price rule can perform additional independent API calls for each discount code they wish to create.

Prior to September 18, 2017, requests to GET /admin/orders.json including the since_id parameter would return a list of orders sorted by created_at. This would present problems when multiple orders were created within the same second, as results wouldn't dependably return in the same order on subsequent requests. Going forward, orders with the since_id parameter will correctly be sorted by order ID, even if the orders were processed at identical created_at times.

As of September 1, 2017, Shopify will begin verifying SSL certificates when delivering webhook payloads to HTTPS webhook addresses. After this date, webhooks that fail the SSL certificate verification will not successfully deliver to their hosts.

We've added some validation today to the ScriptTag resource that prevents an application from creating more than 100 script tags for a particular shop. We feel that a limit of 100 per application is more than fair, and any limit higher than this can cause significant performance issues on storefront.

Currently, the Discounts page in the Shopify admin displays discount codes based on the value of discount_code.code. However, as of August 7th, 2017, Shopify will display the price_rule.title value instead. Please take this change into consideration if you have an app that creates or modifies price rules.

Starting on Monday, July 24th, there will be some changes to how certain properties such as tags and handles are encoded. Currently, Shopify only supports ASCII characters for these properties. Going forward, Shopify will support a full UTF-8 character set for these properties, and you can expect the values of these properties to contain non-ASCII characters.

We're making changes to checkout domains for all Shopify stores. Rather than the checkout domain being checkout.shopify.com, checkout will occur on the shop domain that the customer is shopping on.

As of Thursday, July 20th, 2017, a new parameter will be added to Carrier Service rate requests sent by Shopify – a locale parameter that represents the language of the customer browsing the storefront.

As of today, the Discounts resource has been fully deprecated in favour of the new Price Rules resource. If you have any questions or concerns, then email our support directly at discountsmigration@shopify.com.

As of June 12th, 2017, we will be including a new “locale” key-value pair in Hosted Payment SDK requests. When signing the request, you will need to ensure your integration does not rely on specific fields. Instead, the message being signed should be a string of all key-value pairs that start with x_ prefix, sorted alphabetically, and concatenated without separators.

We're making some changes to how addresses are validated when you import orders through the Order resource.