BigCommerce is a cloud e-commerce platform for established and rapidly-growing businesses. It combines enterprise functionality, open architecture, app ecosystem, and market-leading performance.
BigCommerce documentation: API guide, Authentication
Additional reference: Supported BigCommerce APIs
- A. Set up a BigCommerce connection
- B. Provide required BigCommerce account information
- C. Edit advanced BigCommerce settings
- D. Save and authorize
A. Set up a BigCommerce connection
Start establishing a connection to BigCommerce in either of the following ways:
- From the Resources menu, select Connections. Then, click + Create connection at the top right.
– or –
- While working in a new or existing integration, you can add an application to a flow simply by clicking Add source or Add destination.
In the resulting Application list, click BigCommerce.
The Create connection panel then asks you to name the new connection.
Be sure to provide a clear and distinguishable Name as soon as the connection is created. Throughout integrator.io imports and exports, you will have the option to choose this new connection, and a unique identifier will prove helpful later when selecting among a list of connections that you’ve created.
Click Next to configure the connection.
B. Provide required BigCommerce account information
At this point, you’re presented with settings for BigCommerce authentication.
Authentication type (required): Select OAuth 2.0. (BigCommerce basic and token-based authentication types are treated separately.)
Store hash (required): Enter the base API path. For example, if your URL is https://api.bigcommerce.com/stores/123456/, enter 123456.
Configure scopes (required): Scopes are permissions that the BigCommerce defines to limit the access to your account. To select the scopes for this connection,
- Click the Configure scopes button.
- To access all of the scopes in the API, click the » button.
– or –
Check the scopes you want to add, and click the > button.
Configure your client id and secret (required): Check this box to reveal iClient options.
iClient (required): Select the iClient pair that stores the client ID and client secret provided to you by BigCommerce. To add an iClient and configure your credentials, click the plus (+) button. Click the edit ( ) button to modify a selected iClient. Be sure to give the iClient a recognizable name for use in any other connections.
Callback URL (read-only): Copy this integrator.io callback URL to provide directions to BigCommerce for where to go after authentication. (This URL should be whitelisted with the authorization server.)
Sign in to your BigCommerce account at developer.bigcommerce.com.
Navigate to My apps from the main menu. Click Create an app to begin
Name your new BigCommerce app, and click Create.
Continuing to define your app in the Technical section, edit the user callback URL.
Paste the value you copied, above, in the connection’s Callback URL for all three fields.
Next, scroll down to click the scopes that you want to enable for the app. Save your settings by clicking Update & close.
Returning to your new app’s summary, click View client ID.
Finally, copy the Client ID and Client secret values to paste into your connection’s iClient pair.
C. Edit advanced BigCommerce settings
Before continuing, you have the opportunity to provide additional configuration information, if needed, for the BigCommerce connection.
D. Save and authorize
Once you have configured the BigCommerce connection, you have a couple options for continuing:
- Save & authorize – click this button to test the connection, commit the new connection so that it will be available to all integrations for your account (and applied to the current source or destination app, if you created it within a flow)
- Cancel – click to exit without saving any new changes
When you select Save & authorize, you are presented with a BigCommerce form in a new browser window.
Sign in, review the permissions for the integration, and click Confirm.
The browser window closes, and the new connection is now successfully added to your account. It will be applied to the current source or destination app, if you created it within a flow. Otherwise, you may proceed to register the connection with an integration.
Please sign in to leave a comment.