Integrate iPaaS.com with BigCommerce to synchronize orders, products, inventory, customers, gift cards, payments, and B2B company data between BigCommerce and your connected systems. This article is the ongoing reference for the credentials and settings that drive the connection — use it when setting up a subscription, rotating credentials, or reviewing what each setting does.
How to Connect
Prerequisites
Before setting up the BigCommerce integration in iPaaS.com, ensure you have the following:
Active BigCommerce account: an account with admin permissions to add API accounts and manage store settings.
BigCommerce B2B Edition app (optional): if you use B2B functionality, install and configure the BigCommerce B2B Edition app. Additional fees may apply. See BigCommerce B2B Edition Support for what the integration covers.
Generate a BigCommerce API account
The integration authenticates to BigCommerce with a store-level API account token. To create one:
Log in to your BigCommerce admin account with a user that has admin permissions.
Navigate to Settings, then Store-level API accounts.
Click Create API Account.
Set Token type to V2/V3 API token.
Name it iPaaS.com (or similar).
Grant the following scopes (any scope not listed should be set to None): Orders: Modify, Order Transactions: Modify, Fulfillment Methods: Modify, Order Fulfillment: Modify, Create Payments: Create, Get Payment Methods: Get, Stored Payment Instruments: Modify, Products: Modify, Store Inventory: Modify, Store Locations: Modify, Customers: Modify, Content: Modify, Marketing: Modify, Channel Settings: Modify, Channel Listings: Modify.
Click Save. BigCommerce downloads a credentials file.
The downloaded file contains the API path, Client ID, and Access Token you will enter on the iPaaS.com subscription settings page.
Configure Subscription Settings
Navigate to the BigCommerce subscription settings in iPaaS.com and provide the following. The four credential fields are required to connect; the remaining fields are optional and control specific behaviors.
Field | Description | Required | Example |
Name | A unique name for the subscription. | Yes | BigCommerce Integration |
Versions | The iPaaS.com integration version to use. | Yes | 1.4.1 |
BC Api Url | The first part of the BigCommerce API path, through the top-level domain, with no trailing slash. | Yes | |
BC Api Store Hash | The store identifier from the API path. If the path is https://api.bigcommerce.com/stores/wqbagnaxsr/v3/, the store hash is wqbagnaxsr. | Yes | iqsi4hfvrv |
BC Api Client Id | The Client ID from the downloaded credentials file. | Yes | your client id |
BC Api Token | The Access Token from the downloaded credentials file. | Yes | your access token |
B2B Enabled | Enables BigCommerce B2B Edition support. Set to True to turn on B2B company, customer, and quote handling. | No | True |
B2B Api Url | The BigCommerce B2B Edition API base URL. Used only when B2B is enabled. | No | |
Allow iPaaS.com to delete company hierarchy | Permits the integration to delete a B2B company hierarchy. Leave unset unless you intend to allow hierarchy deletes. | No | True |
Group Order Shipments By | Controls how order shipments are grouped when an order is transferred. | No | (leave empty) |
Disable Gift Card Auto-Creation During Order To iPaaS Preprocessing | When True, stops the integration from automatically creating gift cards for gift-certificate line items while an order is being prepared for transfer. | No | False |
Ignore Price List Errors | When True, price-list errors are suppressed rather than failing the transfer. Defaults to False. | No | False |
Price List Field Separator | The character that separates fields within a price-list record when price-list data is provided as text. | No | , |
Price List Record Delimiter | The character that separates one price-list record from the next. | No | a pipe character |
Do Not Delete Price List Record | Prevents the integration from deleting existing price-list records. | No | True |
Permission Set For Product(MetaFields) | The permission set applied to product metafields the integration writes. | No | (your permission set) |
Namespace For Product(MetaFields) | The namespace applied to product metafields the integration writes. | No | (your namespace) |
Rectangle Grid Tags | No longer supported. | No | (leave empty) |
Swatch Grid Tags | No longer supported. | No | (leave empty) |
Swatch Color Values | No longer supported. | No | (leave empty) |
Note: The Price List settings apply only when you sync BigCommerce price lists. The metafield settings apply only when the integration writes product metafields. Leave them empty if you do not use those features.
Authentication Methods
The integration authenticates to BigCommerce using the store-level API account you created. iPaaS.com sends the Access Token (and, where applicable, the Client ID) on each request, scoped to the store identified by the BC Api Store Hash. Because the token is tied to the scopes you granted when creating the API account, the connection can only perform the operations those scopes allow — if a transfer fails with a permission error, review the API account's scopes in BigCommerce.
When B2B Enabled is True, the integration connects to the BigCommerce B2B Edition API at the B2B Api Url using the same access-token mechanism, together with the store hash, to read and write B2B company, customer, and quote data.
To rotate credentials, create a new API account in BigCommerce (or regenerate the token), then update the BC Api Client Id and BC Api Token fields on the subscription settings page.
Initialization Support
The following data types support initialization and can be transferred in bulk on first connect:
Product Category FROM iPaaS.com
Customer Category FROM iPaaS.com
Payment Method FROM iPaaS.com
All other data types are synchronized through their mapping collections rather than a bulk initialization.
Throttling
Throttling keeps the integration from overwhelming BigCommerce's API during heavy data transfers, preserving performance for your store. The throttle fields on the subscription are required, but their values are pre-populated by the integration and do not normally need to be changed. For details, see Subscription Configuration – Edit. The integration also processes BigCommerce API calls in bounded concurrent batches so that large transfers stay within the store's rate limits.