Release notes

API

• The newly-released metafield endpoints are now available to use. Now, you can manage metafields in batches for the following metafields:

  • Brand Batch Metafields

  • Categories Batch Metafields

  • Products Batch Metafields

  • Product Variants Batch Metafields

  • Customers Batch Metafields

  • Orders Batch Metafields

  • Channels Batch Metafields

  • Carts Batch Metafields

  • Locations Batch Metafields

• We’ve updated the Embedded Checkout Tutorial to indicate that the channel_id is a requirement for a Customer Login JWT used in the embedded checkout process.

Bug Fix

• Updated the sale price definition in the Using Catalog Price Objects article due to a bug fix.

API

• Store-level API accounts now have dedicated scopes for working with metafields. These scopes are helpful for API consumers who wish to prevent their metafields from interference.

• We now have more query examples for the Users feature of the GraphQL Account API. Account admins can include collectionInfo and totalItems in your query requests to collect the total number of items in the collection.

• The Get Store Information endpoint now returns information about storefront limits! The new data includes the number of active storefronts and the total number of storefronts, including inactive ones.

• The Get All Orders parameters now include external_order_id. You can add the parameter to your request to include Order IDs from external systems.

• Updated the Delete All Pricelist endpoint’s parameter to include the in value. To run a request to delete multiple pricelists, you must pair the in value with the id value: id:in.

Bug Fixes

• Corrected the option_id type from a number to an integer in option_selections on POSTS Carts V3.

• Removed unused and empty allOf sections in webhooks.v3.yml.

• Added clarity around the usage of stored PayPal accounts.

• We fixed an error in the category attributes schema in the Stencil Front matter reference. Setting product limits should now be clearer!

• We’ve updated the shipping_provider property throughout the Orders V2 specification to allow arbitrary strings. This update better indicates support for new and custom shipping providers and improves API client autogeneration.

• Fixed categories_catalog.v3.yml to ensure it is a valid Swagger format.

• Added some missing title fields to product-variants_catalog.v3.yml and category-trees_catalog.v3.yml API specification.

Bug Fixes

• Added missing category_id in the sample response for the POST /catalog/trees/categories endpoint. Thank you, Aten Software, for your feedback.

• Updated the menu paths for integrating with Disqus for MSF and non-MSF storefronts.

Announcement

BigCommerce for WordPress Plugin Update Required!

We have deployed a fix for a recent vulnerability found with the BigCommerce for WordPress plugin.

To prevent security vulnerabilities, please upgrade your plugin by following the steps below.

1. Navigate to your WordPress website and log in as an admin.

2.  In the sidebar, select "Plugins".

3.  Select the "update now" hyperlink for the BigCommerce for WordPress plugin.

4.  Wait for the upgrade to finish.

Payments

• We’re happy to announce the ability to use stored Braintree ACH accounts in the Payments API. Now customers can store their bank accounts in a BigCommerce store and use it for recurring payments.

• The newly-released Square V2 payment gateway is available for stored instrument data. See the list of compatible payment gateways.

Announcement

• The Dev Center now contains a UX Writing Guide for developers using BigDesign in their apps and implementations. Developers can now make their apps feel more seamlessly integrated into the BigCommerce control panel. Many thanks to the Product Design team for all their work on this!

Developer Blog

• High-Risk Permissions Now Available!

Announcement

• Hi Devs! We added a submitContactUs mutation to our GraphQL Storefront API, enabling a frontend customer feedback experience. This feature relies on reCaptcha for security and requires the customer to supply, at minimum, an email and comments. It also supports optional fields such as fullName, phoneNumber, orderNumber, companyName, and rmaNumber. This mutation also provides descriptive results for errors that can occur, including the failing field, what caused the error, and a description of the error. For more details, see the GraphQL Storefront Playground for your store or sandbox and experiment with the submitContactUs mutation.

Bug Fix

• Fixed a typo in Deprecation and Sunset Support for Node-sass. Now, you can see potential changes and reevaluate changes by running the following commands.

  stencil scss-autofix --dry

  stencil scss-autofix

Announcement

• A valued partner has done the heroic work of making the OAS operation IDs programmatic across our public APIs. The operationId property is now consistently camelCase and relates to the plain-language name of the endpoint. You can use operation IDs as basis for the method name in a generated SDK.

Announcement

Attention, developers! Google Chrome is starting to restrict 3rd-party cookies. Google made the announcement some time ago, but it's now in effect for 1% of Chrome users, and we expect that number to grow. Many of our app store apps use cookies to manage things like user session or analytics. If you maintain apps or storefront integrations that use 3rd-party cookies, please see Google's article on the changes (developers.google.com) and update your code.

Announcement

As of December 27, 2023, you can find all the public BigCommerce DevDocs at https://github.com/bigcommerce/docs.

Previous docs repositories are now read-only due to the move into one repository. This change includes the following repositories:

• https://github.com/bigcommerce/api-specs

• https://github.com/bigcommerce/dev-docs

• https://github.com/bigcommerce/theme-context-object-schemas

This consolidation offers a more streamlined developer experience. We look forward to seeing your issues, discussions, and pull requests at bigcommerce/docs.

API

• The Webhooks Overview article now provides best practices for working with webhook responses. Use these response requirements to ensure the webhook delivery is successful. 

• Excited to announce that authorized users can now create API Keys or install apps like store owners. See the Single-Click App OAuth Flow article for details.

• Added the shipping_provider_display_name field to Orders V2 API. Now, you can expose a friendly human-readable name for the provider instead of the provider code.

Bug Fix

• Fixed a bug related to the category image URL length for the v3/catalog/trees/categories endpoint, allowing the img_url to contain a full path instead of a short one. The img_url is now consistent with the existing categories API and documented format.