Extensibility & developer surface — found from sitemap — BigCommerce

Cited by

Facts read from this source

• Headless API support Report an error

  “If you need to build a custom solution, BigCommerce has APIs and SDKs available to support your headless architecture.”

• Headless starter solutions Report an error

  “If you want to build a headless storefront powered by a BigCommerce backend without starting from scratch, BigCommerce offers multiple starter apps and pre-built solutions.”

• Wordpress plugin Report an error

  “The BigCommerce for WordPress plugin is built by using an existing CMS and injecting a store’s catalog.”

• Backend scope Report an error

  “It can handle processing payments, storing customer data, and retrieving the catalog and order information.”

• Trusted proxy Report an error

  “The Trusted Proxy feature allows merchants to set up authenticated proxy servers in front of BigCommerce. When properly configured, BigCommerce will use the end user’s actual IP address instead of the proxy’s IP address, enabling more accurate traffic management and improved security.”

• Trusted proxy catalyst auto Report an error

  “If you’re using Catalyst, do not configure the X-BC-Trusted-Proxy-Secret header manually. Instead, set the BIGCOMMERCE_TRUSTED_PROXY_SECRET environment variable and Catalyst will send the header for you.”

• Correlation header Report an error

  “When you perform a multi-part operation on a headless storefront, group the constituent requests by generating one UUID to represent the whole operation, then use the X-Correlation-Id request header to send that UUID with every request in the group.”

• Wordpress no correlation header Report an error

  “When you’re using the BigCommerce for WordPress plugin, there is no need to send the X-Correlation-Id header.”

• Session sync Report an error

  “Built with JWT-based “Session Sync,” this enhancement enables transferring session details, such as customer and cart data, across various contexts.”

• Session sync rate limit Report an error

  “After three attempts with invalid session-sync JWT tokens, the system will block the IP address for five minutes.”

• Analytics visitor id Report an error

  “The GraphQL API supports including a visitor ID when creating a session sync JWT using the generateSessionSyncJwt mutation, enhancing tracking consistency across different contexts.”

• Multi language headless Report an error

  “After October 2025, new headless stores will have access to Multi-language features similar to Catalyst storefronts.”

• Graphql storefront API Report an error

  “The following example uses the GraphQL Storefront API to complete a checkout and generate a payment access token, then uses that payment access token to make the payment using the Payments API.”

1 fact read from this page is not shown because it could not be confirmed on the page as captured.

Scores citing this record

• The B2B Seller Extensibility & developer surface
• The Data Protection Officer Extensibility & developer surface
• The Developer Extensibility & developer surface
• The Merchant Extensibility & developer surface
• The Operations Lead Extensibility & developer surface
• The Skeptic Extensibility & developer surface