This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
bw:bigcommerce_api [2019/03/20 13:39] runger [Create BigCommerce API Account] |
bw:bigcommerce_api [2020/12/14 18:21] (current) akoehler |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== BigCommerce WebService Access ====== | ====== BigCommerce WebService Access ====== | ||
| + | Before a BigCommerce store can be accessed using the APIs, the store must be configured to allow this access. | ||
| + | |||
| + | <WRAP center round alert 60%> | ||
| + | Some of the BigCommerce APIs can be accessed using basic authentication, | ||
| + | </ | ||
| + | |||
| ===== Create BigCommerce API Account ===== | ===== Create BigCommerce API Account ===== | ||
| Line 5: | Line 11: | ||
| This function can only be accessed by the **store owner**. | This function can only be accessed by the **store owner**. | ||
| - | {{: | + | {{ : |
| + | |||
| + | Click the [Create API Account] button to begin. | ||
| ===== Create New API Account ===== | ===== Create New API Account ===== | ||
| - | {{: | + | {{ : |
| + | |||
| + | The name can be anything that makes sense. | ||
| + | |||
| + | 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. | ||
| - | {{: | + | {{ : |
| **Save to continue** | **Save to continue** | ||
| ===== API Credentials ===== | ===== API Credentials ===== | ||
| + | BigCommerce generates a set up credentials once the API connection configuration is complete. | ||
| - | {{: | + | {{ : |
| ====== Bizweaver Configuration ====== | ====== Bizweaver Configuration ====== | ||
| Line 25: | 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 | + | The easiest way to set these values in a workflow is to add them as __Variables__ |
| 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. | ||
| - | {{: | + | {{ : |
| The variables can now be used in the WebService workflow step. | The variables can now be used in the WebService workflow step. | ||
| Line 39: | Line 53: | ||
| * The values “X-Auth-Client: | * The values “X-Auth-Client: | ||
| - | {{: | + | {{ : |