> 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/marketplaces/listing-in-external-marketplaces/bigcommerce-marketplace.md).

# BigCommerce Marketplace

Learn how to list and manage your Pandium-powered integration on the BigCommerce Marketplace, including configuration steps, listing requirements, and best practices for a successful app listing.

When submitting your app to the BigCommerce marketplace, you'll need to provide two critical URLs:

### 1. Auth Installation URL

The OAuth Installation URL initiates the connection flow when users install your app from the BigCommerce marketplace.

**Base URL Format**

Choose the appropriate base URL for your environment:

**Sandbox Environment:**

{% code overflow="wrap" %}

```
https://exmart.sandbox.pandium.com/v1/bigcommerce/auth/<account_name>/<integration_name>
```

{% endcode %}

**Production Environment:**

{% code overflow="wrap" %}

```
https://exmart.pandium.io/v1/bigcommerce/auth/<account_name>/<integration_name>
```

{% endcode %}

Replace `<account_name>` and `<integration_name>` with your specific values.

### 2. Load URL

The Load URL is used to route to the run logs for the user's tenant in their marketplace after the application is installed.

**URL Format**

```
https://exmart.pandium.io/v1/bigcommerce/marketplace/<account_name>/<integration_name>
```

### 3. Uninstall URL

The purpose of this URL will allow users to disconnect and uninstall tenants from Pandium after they disconnect their app in BigCommerce.

{% code overflow="wrap" %}

```
https://exmart.pandium.io/v1/bigcommerce/uninstall/<account_name>/<integration_name>
```

{% endcode %}

### Need Help?

If you encounter issues during the listing process, please feel free to contact your Pandium Technical Account Manager for assistance.


---

# 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/marketplaces/listing-in-external-marketplaces/bigcommerce-marketplace.md?ask=<question>&goal=<user_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.