This is an old revision of the document!
Table of Contents
BigCommerce WebService Access
Before a BigCommerce store can be accessed using the APIs, the store must be configured to allow this access. The configuration process is described in the following section.
Some of the BigCommerce APIs can be accessed using basic authentication, but this is not advisable. BigCommerce is indicates that not all APIs are available with this type of authentication. And basic authentication will not be allowed at some point in the future.
Create BigCommerce API Account
This function can only be accessed by the store owner.
Click the [Create API Account] button to begin.
Create New API Account
The name can be anything that makes sense. The name shown here is simply an example.
The blurred portion of the API Path value is the store identifier.
oAuth Scopes (API Resources)
Save to continue
API Credentials
Bizweaver Configuration
BigCommerce uses its own form of authorization. The setup described above will provide the two values needed to access the web store from Bizweaver.
The two values needed are the Client ID and the Access Token.
The easiest way to set these values in a workflow is to add them as Variables at the beginning of the workflow. This is done along with the required URI. An example of this setup is shown below.
Note that hyphens (dashes) are not allowed in a variable name. So, an underscore is used instead.
The variables can now be used in the WebService workflow step.
- The information after the BaseURI variable is unique to the particular action to be performed.
- The authorization information is placed in the Header section as shown.
- The values “X-Auth-Client:” and “X-Auth-Token:” are case sensitive and use hyphens as shown.
