Knowi has a native BigCommerce connector that authenticates with your store hash and API access token. Once connected, you can pull orders, products, customers, categories, brands, coupons, and more, with automatic pagination, date filtering, and cross-source joins built in.
Quick Summary (TL;DR)
- Knowi connects to BigCommerce using two credentials: your store hash and your API access token, both from a BigCommerce API account in your control panel.
- Available data types: Orders, Products, Customers, Categories, Brands, Coupons, Store Info, and Custom Query.
- Each collection supports date range filters, and incremental syncs are supported using Knowi date tokens such as {$c9_lastrun:yyyy-MM-dd}.
- Knowi handles pagination automatically (up to 250 records per page) and retries on rate limit errors.
- BigCommerce data can be joined natively with Stripe, Klaviyo, Google Ads, MongoDB, PostgreSQL, and 30-plus other sources in Knowi.
- The Custom Query option lets you access any BigCommerce endpoint not covered by the pre-built collections, such as catalog variants or price lists.
Table of Contents
How to Connect BigCommerce to Knowi
The BigCommerce connector is available natively in Knowi. You need an API account from your BigCommerce control panel to get started.
- In your BigCommerce control panel, create an API account. This gives you an Access Token.
- Find your store hash in your BigCommerce API path:
https://api.bigcommerce.com/stores/{store_hash}/v3/ - In Knowi, go to Queries and select New Data Source.
- Select the BigCommerce connector.
- Enter your Access Token and Store Hash.
- Save and start querying.
For full setup details, see the BigCommerce connector documentation.
What Data Can You Pull from BigCommerce?
| Collection | Key Fields | Available Filters |
|---|---|---|
| Orders | id, customer_id, status, status_id, total_inc_tax, subtotal_inc_tax, total_tax, currency_code, payment_method, items_total, date_created, date_modified | Order Status, Customer ID, Created After/Before, Modified After |
| Products | id, name, sku, type, price, cost_price, sale_price, inventory_level, inventory_warning_level, is_visible, availability, brand_id, total_sold, date_created, date_modified | Keyword, Visible (boolean), Availability, Modified After |
| Customers | id, email, first_name, last_name, company, phone, customer_group_id, registration_ip_address, date_created, date_modified | Email, Customer Group ID, Created After/Before |
| Categories | Catalog category hierarchy | Standard category filters |
| Brands | Brand catalog records | Standard brand filters |
| Coupons | Coupon code, discount type, usage tracking | Coupon Code (exact match), Type: per_item_discount, percentage_discount, per_total_discount, shipping_discount, free_shipping, promotion |
| Store Info | Single store-level profile object | None. Useful as a constant join key across multi-store setups. |
| Custom Query | Any BigCommerce endpoint | Specify your own resource path, e.g., v3/catalog/variants, v3/customers/addresses, v3/pricelists |
Technical Details
v2 vs v3 API Resources
BigCommerce has v2 and v3 API endpoints, and they format responses differently. Knowi handles both, but the Cloud9QL query format differs slightly.
- v3 resources (Products, Customers, Categories, Brands) wrap rows in a
dataarray. Queries begin withselect expand(data); - v2 resources (Orders, Coupons, Store Info) return flat arrays or single objects. No expand wrapper is needed.
Date Tokens for Incremental Syncs
Knowi provides date tokens that format automatically to BigCommerce’s ISO-8601 date requirement. Use these in filter fields to run incremental syncs:
{$c9_today:yyyy-MM-dd}: today’s date{$c9_today-30d:yyyy-MM-dd}: 30 days ago{$c9_lastrun:yyyy-MM-dd}: date of the last query run, for pulling only new records
Pagination and Rate Limits
- Knowi fetches all pages automatically (up to 250 records per page).
- When BigCommerce returns a rate limit error (429), Knowi retries automatically using exponential backoff.
Joining BigCommerce with Other Sources
Knowi supports cross-source joins natively, so you can combine BigCommerce data with other sources in a single query without a warehouse. Supported joins include Stripe, Klaviyo, Google Ads, MongoDB, PostgreSQL, and 30-plus additional sources.
Frequently Asked Questions
What credentials do I need to connect BigCommerce to Knowi?
Two credentials: an Access Token and a Store Hash. Create an API account in your BigCommerce control panel to get the access token. The store hash is in your BigCommerce API path: https://api.bigcommerce.com/stores/{store_hash}/v3/
What BigCommerce data can I pull into Knowi?
Orders, Products, Customers, Categories, Brands, Coupons, and Store Info. The Custom Query option also lets you access any BigCommerce endpoint not in the pre-built list, such as catalog variants, customer addresses, or price lists.
Does Knowi handle BigCommerce rate limits?
Yes. Knowi automatically retries requests when it hits BigCommerce’s rate limits (429 responses), using exponential backoff. You do not need to manage this manually.
Can I filter BigCommerce orders by date?
Yes. Use the Created After and Created Before filters on the Orders collection. For incremental syncs, use the {$c9_lastrun:yyyy-MM-dd} date token to pull only records modified since the last query run.
Can I combine BigCommerce data with Stripe or Klaviyo in Knowi?
Yes. Knowi supports cross-source joins natively. You can join BigCommerce orders with Stripe charges or Klaviyo campaign data directly in the query, without moving data to a warehouse first.
What is the Custom Query option?
Custom Query lets you access any BigCommerce API endpoint not covered by the pre-built collections. Specify the resource path directly, for example v3/catalog/variants, v3/customers/addresses, or v3/pricelists.
Ready to connect your BigCommerce store to Knowi? Read the BigCommerce connector documentation to get started, or schedule a demo to see it in action with your store data.