The Jitterbit Harmony BigCommerce Connector establishes access to BigCommerce.
The BigCommerce connector provides an interface for creating a BigCommerce connection, the foundation used for generating instances of BigCommerce activities. These activities, once configured, interact with BigCommerce through the connection.
The BigCommerce connector uses a Store Hash, Client ID (optional), and Access Token for configuring a BigCommerce connection. These values are obtained from a store API account, as described in BigCommerce API Account Creation.
This connector is used to first configure a BigCommerce connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).
Together, a specific BigCommerce connection and its activities are referred to as a BigCommerce endpoint:
Query: Queries data from an object in BigCommerce and is intended to be used as a source in an operation.
Create: Creates a new object record in BigCommerce and is intended to be used as a target in an operation.
Update: Updates an existing object record in BigCommerce and is intended to be used as a target in an operation.
Delete: Deletes an object record from BigCommerce and is intended to be used as a target in an operation.
Verbose logging can be enabled for this connector. See Verbose Logging for Connectors for details.
Invoke verbose logging for this connector using this configuration entry:
<logger name="org.jitterbit.connector.verbose.logging.bigcommerce" level="DEBUG"/>
Prerequisites and Supported API Versions¶
The BigCommerce connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.
The BigCommerce connector uses the BigCommerce REST API v3.0. Refer to the API documentation for information on the schema nodes and fields.