E-commerce

Connect BigCommerce to Wilph

A store-level BigCommerce API account gives Wilph read access to orders, customers and products.

Roughly how long: About 5 minutes
Who can do it: A store owner or a user with the Manage API accounts permission.

Before you start

Create the API account
In the control panel go to Settings → API → Store-level API accounts and choose Create API account. Keep the token type as V2/V3 API token and name it Wilph.
Set read-only scopes
Set Orders, Customers, Products and Information & Settings to read-only. Leave everything else at none.
Save and keep the file
Saving downloads a .txt file containing the client ID, client secret, access token and the API path. This is the only time those values are shown.
Find your store hash
The API path in that file looks like api.bigcommerce.com/stores/abc123xyz/v3/ — the segment after /stores/ is your store hash.
Paste them into Wilph
In Wilph, open Dashboard → Integrations → BigCommerce → Connect and save the store hash and the access token.

The exact fields on the connection form, in order.

Store hash
The store identifier used in api.bigcommerce.com/stores/{store_hash}.
Access tokenStored encrypted
Use the access token from a store-level API account with the required read scopes.

The access token is encrypted before storage. Delete the downloaded .txt once Wilph has accepted the connection.

You cannot find the credentials again.

BigCommerce shows them only at creation. Delete the API account and create a new one — existing connections using it will need the new token.

Wilph reports the store hash is unknown.

Copy it from the API path rather than from the browser address bar; the control panel URL uses a different identifier.

Still stuck? Get in touch — tell us which step it failed on and what it said.

Shopify

3 min setup

WooCommerce

5 min setup

Magento / Adobe Commerce

10 min setup

Open Integrations in your Wilph dashboard and paste in what you collected.