Skip to content
Integrations/BigCommerce/Connection Guide
Connection Guide

Connect BigCommerce Without Breaking the Audit Trail

Use this guide to connect BigCommerce or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryPayments / PCI
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect BigCommerce and make sure the first collection lands cleanly.

  1. 1
    Create dedicated integration user (least privilege).
  2. 2
    Create a BigCommerce API account and copy the access token.
  3. 3
    Configure store_hash (for example, abc123) and paste access_token into Aurora secure credentials.
  4. 4
    Run validate; then enable incremental cadence.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

access_token

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.