> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/connectors/connectors-101/bigcommerce.md).
# BigCommerce
Set up the BigCommerce OAuth2 connector in Pandium using your client ID, client secret, and access token so tenants can securely sync store, product, and order data.
## **Connector Overview**
BigCommerce is an eCommerce platform that makes it easy for businesses of all sizes to build, manage, and grow their online stores. With powerful customization, built-in marketing tools, and seamless shipping options, it helps brands sell more and scale faster.
## **Authentication Type**
OAuth2
## **Webhook Supported**
No
## **Secrets**
* PAN\_SEC\_BIGCOMMERCE\_ACCESS\_TOKEN
* PAN\_SEC\_BIGCOMMERCE\_CLIENT\_ID
* PAN\_SEC\_BIGCOMMERCE\_USER
* PAN\_SEC\_BIGCOMMERCE\_SCOPE
* PAN\_SEC\_BIGCOMMERCE\_CONTEXT
## **API Client Supported**
No
## **App Marketplace-Ready**
Yes. For more information, please see [here](https://docs.pandium.com/marketplaces/listing-in-external-marketplaces/bigcommerce-marketplace).
## **Requirements for Provisioning**
In order to provision your connector, the following Yotpo information must be gathered:
* Client ID
* Client Secret
To obtain the information required for provisioning, perform the following steps:
1. Log in to your [Developer Portal](https://devtools.bigcommerce.com/my/apps)
2. Select “View Client ID” > Your client ID and secret will be displayed\
\
## **API Resources**
For more information on how to utilize the BigCommerce API, feel free to reference the following [documentation](https://developer.bigcommerce.com/docs/api).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.pandium.com/connectors/connectors-101/bigcommerce.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
