Apps compatible with multi-location inventory use our Inventory API for inventory adjustments. Now, you can indicate whether an app is MLI-compatible when you submit an app in the Dev Portal. See the Add supported features section for more information.
GraphQL
We're happy to announce that you can now create GraphQL Storefront API Tokens that are valid for multiple channels. For more information, see Create a Storefront API token and Create a Customer Impersonation Token.
Announcement
We removed the API rate limit content from the Best Practices section to streamline documentation and improve clarity for developers. API Rate Limits documentation now exists as its own reference article and dives deeper into API rate limit standards and best practices.
Bug Fix
Removed all pagination objects and replaced them with an empty meta object for the Get all themes endpoint.
Apps compatible with multi-location inventory use our Inventory API for inventory adjustments. Now, you can indicate whether an app is MLI-compatible when you submit an app in the Dev Portal. See the Add supported features section for more information.
GraphQL
We're happy to announce that you can now create GraphQL Storefront API Tokens that are valid for multiple channels. For more information, see Create a Storefront API token and Create a Customer Impersonation Token.
Announcement
We removed the API rate limit content from the Best Practices section to streamline documentation and improve clarity for developers. API Rate Limits documentation now exists as its own reference article and dives deeper into API rate limit standards and best practices.
Bug Fix
Removed all pagination objects and replaced them with an empty meta object for the Get all themes endpoint.
The Create an order shipment endpoint no longer supports UPSOnline as a shipper.
The newly-released product review mutation is now available. Now, you can create product reviews through the built-in comment system using the GraphQL Storefront API.
We are excited to announce Japanese language support. Now, BigCommerce’s Cornerstone Stencil theme supports uneditable strings in Japanese.
We’ve added a new query parameter, transaction_id
, in GET Refunds API endpoints.
The GraphQL Storefront API now supports creating cart/checkout redirect URLs.
Announcements
BigCommerce will deprecate support for Stencil CLI version 6 and older starting June 3, 2024. This decision is part of our ongoing efforts to ensure optimal performance and security for all platform users.
Action required: To facilitate a smooth transition, we encourage you to upgrade to the latest version of Stencil CLI before the deprecation date. Upgrading ensures you and your team access the latest enhancements and features.
How to upgrade: Run the following command in your terminal window to install the latest version.
npm i -g @bigcommerce/stencil-cli
If you have any questions or need assistance with the upgrade process, please don’t hesitate to contact our support team. We’re here to help ensure a seamless transition for your storefront.
We’ve updated our list of dev support options to include the Resource Hub.
Bug Fixes
Updated error responses and definitions for brands v3 endpoints.
Corrected the Create a product variant response body example.
Clarified the ambiguity around what it means to be a subscriber and added examples of POST/PUT requests for subscribers. See Customers and subscribers for details.
Updated data type from array to string for the name:link
parameter for Get All Price Lists.
Removed duplicated parameters in the following openAPI operations. Thank you @smack-riccardoc!
The Create an order shipment endpoint no longer supports UPSOnline as a shipper.
The newly-released product review mutation is now available. Now, you can create product reviews through the built-in comment system using the GraphQL Storefront API.
We are excited to announce Japanese language support. Now, BigCommerce’s Cornerstone Stencil theme supports uneditable strings in Japanese.
We’ve added a new query parameter, transaction_id
, in GET Refunds API endpoints.
The GraphQL Storefront API now supports creating cart/checkout redirect URLs.
Announcements
BigCommerce will deprecate support for Stencil CLI version 6 and older starting June 3, 2024. This decision is part of our ongoing efforts to ensure optimal performance and security for all platform users.
Action required: To facilitate a smooth transition, we encourage you to upgrade to the latest version of Stencil CLI before the deprecation date. Upgrading ensures you and your team access the latest enhancements and features.
How to upgrade: Run the following command in your terminal window to install the latest version.
npm i -g @bigcommerce/stencil-cli
If you have any questions or need assistance with the upgrade process, please don’t hesitate to contact our support team. We’re here to help ensure a seamless transition for your storefront.
We’ve updated our list of dev support options to include the Resource Hub.
Bug Fixes
Updated error responses and definitions for brands v3 endpoints.
Corrected the Create a product variant response body example.
Clarified the ambiguity around what it means to be a subscriber and added examples of POST/PUT requests for subscribers. See Customers and subscribers for details.
Updated data type from array to string for the name:link
parameter for Get All Price Lists.
Removed duplicated parameters in the following openAPI operations. Thank you @smack-riccardoc!
We’re happy to announce Promotions API is Generally Available (GA).
The GraphQL Storefront API now supports cart metafields.
Added a Localization document that describes how to localize a Catalyst storefront.
Webhooks
The newly-released delivery exception webhook alerts users of delivery issues at their primary delivery destination.
Announcement
BigCommerce will deprecate support for Stencil CLI version 6 and older starting June 3, 2024. This decision is part of our ongoing efforts to ensure optimal performance and security for all platform users.
Action required: To facilitate a smooth transition, we encourage you to upgrade to the latest version of Stencil CLI before the deprecation date. Upgrading ensures you and your team access the latest enhancements and features.
How to upgrade: Run the following command in your terminal window to install the latest version.
npm i -g @bigcommerce/stencil-cli
If you have any questions or need assistance with the upgrade process, please don’t hesitate to contact our support team. We’re here to help ensure a seamless transition for your storefront.
Developer Blog
]]>We’re happy to announce Promotions API is Generally Available (GA).
The GraphQL Storefront API now supports cart metafields.
Added a Localization document that describes how to localize a Catalyst storefront.
Webhooks
The newly-released delivery exception webhook alerts users of delivery issues at their primary delivery destination.
Announcement
BigCommerce will deprecate support for Stencil CLI version 6 and older starting June 3, 2024. This decision is part of our ongoing efforts to ensure optimal performance and security for all platform users.
Action required: To facilitate a smooth transition, we encourage you to upgrade to the latest version of Stencil CLI before the deprecation date. Upgrading ensures you and your team access the latest enhancements and features.
How to upgrade: Run the following command in your terminal window to install the latest version.
npm i -g @bigcommerce/stencil-cli
If you have any questions or need assistance with the upgrade process, please don’t hesitate to contact our support team. We’re here to help ensure a seamless transition for your storefront.
Developer Blog
]]>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.
Navigate to your WordPress website and log in as an admin.
In the sidebar, select "Plugins".
Select the "update now" hyperlink for the BigCommerce for WordPress plugin.
Wait for the upgrade to finish.
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.
Navigate to your WordPress website and log in as an admin.
In the sidebar, select "Plugins".
Select the "update now" hyperlink for the BigCommerce for WordPress plugin.
Wait for the upgrade to finish.
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
]]>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
]]>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
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
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.
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.
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.
]]>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.
]]>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:
This consolidation offers a more streamlined developer experience. We look forward to seeing your issues, discussions, and pull requests at bigcommerce/docs.
]]>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:
This consolidation offers a more streamlined developer experience. We look forward to seeing your issues, discussions, and pull requests at bigcommerce/docs.
]]>Recommended promotions usage information is available. Now you’ll have guidance on creating rules for active promotions.
Updated the Headless Checkout tutorial to improve understanding and readability.
Announcement
BigCommerce is excited to announce a move toward a more streamlined and consolidated public-facing docs repository in 2024. On December 27th, all our current docs repositories will become read-only in preparation for the move into one repository. This change includes the following repositories:
If you maintain API clients, your source for the most up-to-date API specifications will change.
]]>Recommended promotions usage information is available. Now you’ll have guidance on creating rules for active promotions.
Updated the Headless Checkout tutorial to improve understanding and readability.
Announcement
BigCommerce is excited to announce a move toward a more streamlined and consolidated public-facing docs repository in 2024. On December 27th, all our current docs repositories will become read-only in preparation for the move into one repository. This change includes the following repositories:
If you maintain API clients, your source for the most up-to-date API specifications will change.
]]>