BigCommerce

The BigCommerce connector is a Palantir-provided driver for BigCommerce.

To create a new BigCommerce source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for BigCommerce-specific configuration and networking. For the complete property reference, see the official BigCommerce driver documentation ↗.

Configuration

The properties below are mandatory or recommended.

PropertyRequired?DescriptionDefault
StoreIdMandatoryThe store hash for this BigCommerce account.
AuthSchemeRecommendedThe type of authentication to use when connecting to BigCommerce.PersonalAccessToken
IncludeCustomFieldsRecommendedA boolean indicating if you would like to include custom fields in the column listing.TRUE
InitiateOAuthRecommendedSpecifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working.REFRESH
OAuthClientIdRecommendedSpecifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server.
OAuthClientSecretRecommendedSpecifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server.

Networking

The table below lists the domains that the source needs to be able to access in order to successfully run.

For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead; the agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.

DomainRequired
login.bigcommerce.comAlways. Auth and token endpoints
api.bigcommerce.comAlways
store-{STORE_ID}.mybigcommerce.comAlways. Looks like it is used in some cases where you are inserting/updating data