bw:bigcommerce_api

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
bw:bigcommerce_api [2019/03/20 13:44]
runger [BigCommerce WebService Access]
bw:bigcommerce_api [2020/12/14 18:21] (current)
akoehler
Line 11: Line 11:
 This function can only be accessed by the **store owner**. This function can only be accessed by the **store owner**.
  
-{{:bw:bc_api1.png?700|BigCommerce API Setup 1}}+{{  :bw:bc_api1.png?700  |BigCommerce API Setup 1}} 
 + 
 +Click the [Create API Account] button to begin.
  
 ===== Create New API Account ===== ===== Create New API Account =====
  
-{{:bw:bc_api2.png?600|BigCommerce API Account}}+{{  :bw:bc_api2.png?600  |BigCommerce 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) ===== ===== oAuth Scopes (API Resources) =====
 +Next you will identify the specific API resources that will be available to this connection.  The resources shown here are the basic ones that are typically needed.
  
-{{:bw:bc_api3.png?400|BigCommerce API Resources}}+{{  :bw:bc_api3.png?400  |BigCommerce API Resources}}
  
 **Save to continue** **Save to continue**
  
 ===== API Credentials ===== ===== API Credentials =====
 +BigCommerce generates a set up credentials once the API connection configuration is complete.  A file with the values should be automatically saved on your local machine; most likely in your Downloads folder.  You can also copy/paste the values to a text file manually if you like.
  
-{{:bw:bc_api4.png?600|BigCommerce API Credentials}}+{{  :bw:bc_api4.png?600  |BigCommerce API Credentials}}
  
 ====== Bizweaver Configuration ====== ====== Bizweaver Configuration ======
Line 31: Line 39:
 BigCommerce uses its own form of authorization. The setup described above will provide the two values needed to access the web store from Bizweaver. 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 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.+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. Note that hyphens (dashes) are not allowed in a variable name. So, an underscore is used instead.
  
-{{:bw:bc_api5.png?600|Bizweaver BigCommerce Variables}}+{{  :bw:bc_api5.png?600  |Bizweaver BigCommerce Variables}}
  
 The variables can now be used in the WebService workflow step. The variables can now be used in the WebService workflow step.
Line 45: Line 53:
   * The values “X-Auth-Client:” and “X-Auth-Token:” are case sensitive and use hyphens as shown.   * The values “X-Auth-Client:” and “X-Auth-Token:” are case sensitive and use hyphens as shown.
  
-{{:bw:bc_api6.png?600|BigCommerce WebService Configuration}}+{{  :bw:bc_api6.png?600  |BigCommerce WebService Configuration}}
bw/bigcommerce_api.1553103872.txt.gz · Last modified: 2019/03/20 13:44 by runger