Proxy REST API Endpoints
BigCommerce for WordPress sets up several proxy REST endpoints that map requests to the BigCommerce API. This allows developers to build extensions using client-side requests without having to worry about cross-origin restrictions. This feature is useful for building extensions such as single-page store apps or progressive web apps, and it powers the AMP integration provided when the official AMP plugin for WordPress is active on the same site.
By default, these proxy REST endpoints are available under your-wordpress-site.com/wp-json/bc/v3/, with request routes mapping to those documented in the BigCommerce Dev Center’s API Reference. For example, your-wordpress-site.com/wp-json/bc/v3/catalog/products returns data from the corresponding BigCommerce API endpoint and accepts all the same parameters.
Most of the WordPress proxy REST endpoints are publicly queryable, with authentication happening automatically using plugin settings. For security purposes, however, some potentially sensitive data is filtered out of the WordPress response. Those fields are noted in the table below.
Caching and Webhooks
By default, GET requests under /catalog are cached for ten minutes in the object cache — or via WordPress transients if object caching is not available — and a BigCommerce webhook is used to bust cached data related to a product when it is updated in BigCommerce or its inventory data changes. This default caching implementation can be overridden using the bigcommerce/proxy/result_pre WordPress filter. See the plugin customization guide for details on overriding core plugin functionality.
