Skip to main content
Use the @bijection/connectors/bigcommerce entrypoint to declare BigCommerce resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Orders

pull: Carried date_modified walk, header-token webhook hints and unconditional shipments

The following example matches configuration standard.

Configuration: standard

Case: bigcommerce/orders/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: bigcommerce. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: orders
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: webhooks

Case: bigcommerce/orders/pull/webhooks. Connection and resource configuration are declared by this exact case. Credential kind: bigcommerce. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: orders
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: shipments

Case: bigcommerce/orders/pull/shipments. Connection and resource configuration are declared by this exact case. Credential kind: bigcommerce. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: orders
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Catalog products

pull: Carried date_modified walk with 404 withdrawal

The following example matches configuration webhooks.

Configuration: standard

Case: bigcommerce/products/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: bigcommerce. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: products
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: webhooks

Case: bigcommerce/products/pull/webhooks. Connection and resource configuration are declared by this exact case. Credential kind: bigcommerce. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: products
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Customers

pull: Carried date_modified walk without deletions

The following example matches configuration standard.

Configuration: standard

Case: bigcommerce/customers/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: bigcommerce. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: customers
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection holds a bigcommerce credential (bigcommerce.credential), an X-Auth-Token header envelope confined to https://api.bigcommerce.com, and the store hash as storeHash setup; every route is /stores/{storeHash}/…. Identity is GET /v2/store, whose id is the store hash. Each collection is a walk over the modification time, sorted ascending from an inclusive lower bound and carried between passes (sync.carry):
  • orders.pull: V2 GET /orders?sort=date_modified:asc&min_date_modified=…, 50 a page, RFC 2822 UTC times. V2 states no pagination, so a short page or 204 ends a pass. Totals (total_inc_tax, total_ex_tax, subtotal_*) are declared exact decimal text beside currency_code, default_currency_code and currency_exchange_rate; a total arriving as a JSON number refuses the page. status_id and status are kept as stated. An archived order (is_deleted: true) is withdrawn where a response states it.
  • products.pull: V3 catalog products, sort=date_modified&direction=asc from date_modified:min, ended by meta.pagination.total_pages. Prices are JSON numbers, kept as the received double’s text and not exact. Inventory adjustments do not change date_modified. A point read answering 404 withdraws a product.
  • customers.pull: V3 customers, sort=date_modified:asc. V3 has no read of one customer, so deleted customers are not withdrawn.
A pass begins five minutes before the latest time the previous pass read and re-reads its boundary; re-read rows deduplicate by date_modified, their opaque version. Only a page entirely at its own bound asks for the next page number of that bound. A pass that fails hands nothing on. With updates: "webhooks", a delivery must carry the Authorization value the operator set in the hook’s headers (BigCommerce signs nothing) and is identified by its hash. Integer ids are no record key a hint can carry, so a delivery requests an incremental pass of the collection. createShipment posts the given shipment body to /v2/orders/{id}/shipments. BigCommerce offers no idempotency key or precondition, so it is one unconditional attempt; a lost answer stays unknown. Nothing here has run against BigCommerce or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.