Salesforce B2C Commerce Cloud
Salesforce B2C Commerce Cloud is a comprehensive e-commerce platform that enables businesses to create personalized shopping experiences, manage product catalogs, process orders, and analyze customer behavior across multiple channels.
Power end-to-end data operations for your Salesforce B2C Commerce Cloud API with Nexla. Our bi-directional Salesforce B2C Commerce Cloud connector is purpose-built for Salesforce B2C Commerce Cloud, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Salesforce B2C Commerce Cloud or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Salesforce B2C Commerce Cloud workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Before creating a Salesforce B2C Commerce Cloud credential, you need to obtain your OAuth2 Client ID, Client Secret, and other required configuration parameters from your Salesforce B2C Commerce Cloud account. Salesforce B2C Commerce Cloud uses OAuth2 2-legged authentication (Client Credentials flow), which allows Nexla to access your account using client credentials without user interaction.
To obtain your Salesforce B2C Commerce Cloud OAuth2 credentials, follow these steps:
-
Sign in to your Salesforce B2C Commerce Cloud account using your administrator credentials.
-
Navigate to your account settings or API management section in the Salesforce B2C Commerce Cloud interface.
-
Look for the API or OAuth2 Applications section in your account settings, or navigate to Settings > API or Developers > OAuth2 Applications.
-
If you don't have an OAuth2 application yet, look for the option to create or register your OAuth2 application.
-
Click Create OAuth2 Application or Register OAuth2 Application to create a new OAuth2 application.
-
Configure your OAuth2 application settings:
- Enter a name for the application (e.g., "Nexla Integration")
- Review and select the permissions or scopes for the application (if applicable)
- Select Client Credentials or 2-legged OAuth as the grant type
-
Click Create or Register to create the OAuth2 application.
-
Your Client ID will be displayed immediately after creation. Copy the Client ID.
-
Your Client Secret will be displayed immediately after creation. Copy the Client Secret immediately, as it may not be accessible again after you navigate away from the page.
-
Navigate to your Salesforce B2C Commerce Cloud account settings to find your Organization ID, Realm ID, Instance ID, Short Code, and other required parameters. These can typically be found in your account settings or API configuration page.
-
Store all credentials securely, as you will need them to configure your Nexla credential. The Client ID, Client Secret, and other configuration parameters are sensitive information and should be kept confidential.
The Client ID and Client Secret are used to authenticate with the Salesforce B2C Commerce Cloud API authentication endpoint (/dwsso/oauth2/access_token) to obtain an access token. The access token is then sent in the Authorization header with the Bearer prefix for all subsequent API requests to the Salesforce B2C Commerce Cloud API. The access token is automatically obtained and refreshed by Nexla as needed. If your credentials are compromised, you should immediately revoke them in your Salesforce B2C Commerce Cloud account settings and generate new ones. For detailed information about Salesforce B2C Commerce Cloud OAuth2 authentication, API access, and available endpoints, refer to the Salesforce B2C Commerce Cloud API documentation.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| Client ID | Yes | No | Please enter your Client ID |
| Client Secret | Yes | Yes | Please enter your Client Secret |
| Scope Parameter | No | No | Please include a space-separated list of requested scopes |
| Organization ID | Yes | No | Please enter the organization ID - This is a short string that identifies your B2C Commerce instance |
| Realm ID | Yes | No | Please enter the Realm ID - The four character string, part of the organization ID following the second underscore (_) character |
| Instance ID | Yes | No | Please enter the Instance ID - The three character string, part of the organization ID following the third underscore (_) character |
| Short Code | Yes | No | Please enter the short code. This is an eight-character string that is assigned to your entire realm, across all instances. |
| Version | Yes | No | Version |
Create a credential in Nexla
- After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Salesforce B2C Commerce Cloud

- Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Salesforce B2C Commerce Cloud uses OAuth2 2-legged authentication for all API requests. Your Client ID and Client Secret are used to authenticate with the Salesforce B2C Commerce Cloud API authentication endpoint to obtain an access token, which is then used for all subsequent API requests.
-
Enter your Salesforce B2C Commerce Cloud Client ID in the Client ID field. This is the Client ID you obtained from your Salesforce B2C Commerce Cloud account settings (Settings > API or Developers > OAuth2 Applications). The Client ID is used along with the Client Secret to authenticate with the Salesforce B2C Commerce Cloud API authentication endpoint and obtain an access token.
-
Enter your Salesforce B2C Commerce Cloud Client Secret in the Client Secret field. This is the Client Secret you obtained from your Salesforce B2C Commerce Cloud account settings. The Client Secret is used along with the Client ID to authenticate with the Salesforce B2C Commerce Cloud API authentication endpoint and obtain an access token. The Client Secret is sensitive information and must be kept confidential.
-
Enter the scope parameter in the Scope Parameter field (optional). This should be a space-separated list of requested scopes. The scope parameter determines which resources and operations your application can access. Leave this field empty if you want to use the default scope.
-
Enter your Organization ID in the Organization ID field. This is a short string that identifies your B2C Commerce instance. The Organization ID is part of your B2C Commerce instance identifier and is required for API requests.
-
Enter your Realm ID in the Realm ID field. This is a four-character string that is part of the organization ID following the second underscore (_) character. The Realm ID is required for constructing the OAuth2 scope.
-
Enter your Instance ID in the Instance ID field. This is a three-character string that is part of the organization ID following the third underscore (_) character. The Instance ID is required for constructing the OAuth2 scope.
-
Enter your Short Code in the Short Code field. This is an eight-character string that is assigned to your entire realm, across all instances. The Short Code is used in the API base URL.
-
Enter the API version in the Version field. This should be the API version you want to use (default:
v1). The version determines which API version will be used for all API requests.Your Salesforce B2C Commerce Cloud OAuth2 credentials can be found in your Salesforce B2C Commerce Cloud account settings under Settings > API or Developers > OAuth2 Applications. The Client ID and Client Secret are used to authenticate with the Salesforce B2C Commerce Cloud API authentication endpoint (
/dwsso/oauth2/access_token) to obtain an access token. The access token is then automatically sent in theAuthorization: Bearer {token}header for all subsequent API requests to the Salesforce B2C Commerce Cloud API.The access token is automatically obtained and refreshed by Nexla as needed. If your credentials are compromised, you should immediately revoke them in your Salesforce B2C Commerce Cloud account settings and generate new ones. The Client ID, Client Secret, and other configuration parameters provide access to your Salesforce B2C Commerce Cloud account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.
For detailed information about Salesforce B2C Commerce Cloud OAuth2 authentication, API access, and available endpoints, see the Salesforce B2C Commerce Cloud API documentation.
-
Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Salesforce B2C Commerce Cloud connector tile from the list of available connectors, then select the credential that will be used to connect to your Salesforce B2C Commerce Cloud account, and click Next; or, create a new Salesforce B2C Commerce Cloud credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Salesforce B2C Commerce Cloud endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
Salesforce B2C Commerce Cloud data sources can also be manually configured to ingest data from any valid Salesforce B2C Commerce Cloud API endpoint, including endpoints not covered by the pre-built templates or chained API calls. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Salesforce B2C Commerce Cloud API endpoints typically use the GET method for retrieving data and POST for search endpoints. The endpoint URL follows the pattern https://{short_code}.api.commercecloud.salesforce.com/product/catalogs/{version}/organizations/{org_id}/catalogs, built from the Short Code, Version, and Organization ID in your credential. For the Response Data Path, use $.data[*] to extract items from list endpoints, $.hits[*] for search endpoints, or $ for single-record endpoints. Most endpoints support offset-based pagination using offset and limit parameters.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Salesforce B2C Commerce Cloud data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.