Integrate iPaaS.com with commercetools to synchronize customers and customer addresses, orders with their line items, addresses, taxes and payments, products, product variants, product attributes, product categories, inventory, and locations between the two systems.

This article is the ongoing connection reference for the integration. It describes what each credential and setting does, how authentication works, and how to maintain the connection over time, for example when rotating a client secret or moving to a different commercetools project. For the first-time setup walkthrough, subscribers or their MiSP should follow the commercetools Installation Instructions. For the commercetools endpoints this integration calls, see commercetools API Endpoints.

Before configuring the commercetools integration in iPaaS.com, complete the following in commercetools.

Gather the following four values. Each one corresponds to a field on the iPaaS.com subscription settings page.

The API Url follows this pattern:

For a project named my-project-key in the supported region, the value is https://api.us-central1.gcp.commercetools.com/my-project-key.

The Scope follows this pattern:

For the same project, the value is manage_project:my-project-key.

The Client_Id, Client_Secret, and Scope values must all belong to the same commercetools project as the API Url. A mismatch between the project key in the Scope and the project key in the API Url is a common cause of transfers failing with authorization errors.

The fields below configure your commercetools subscription in iPaaS.com. The first four establish the connection and authentication and must be supplied by the subscriber or their MiSP. The remaining fields control transfer pacing and arrive pre-populated.

The API Throttle Limit (To iPaaS) and API Throttle Seconds (To iPaaS) field names are reproduced exactly as they appear on the subscription settings page.

The Example column shows workable operating values, not the values your subscription ships with. The throttle and concurrency fields are pre-populated when the subscription is created, and the values supplied may differ from the examples above. Read the current values on your own subscription rather than assuming them, and change them only for the reasons described under Throttling below. Graduated starting points for a new installation are given in commercetools Installation Instructions.

The subscription also carries a Name and a Version, which identify and version the subscription within iPaaS.com. These are general iPaaS.com subscription fields rather than commercetools credentials, and they are covered in Subscription Configuration – Edit.

The integration authenticates to commercetools using OAuth 2.0 with the client credentials grant. There is no interactive sign-in step and no consent screen: iPaaS.com presents the Client_Id and Client_Secret you entered, together with the Scope, to the commercetools authorization service, receives an access token in return, and uses that token on every subsequent request to the address in API Url. Tokens are obtained and stored automatically, so no further action is required once the four values are saved.

To configure authentication:

Verify the credentials with a real transfer, not with the connection test. At the time this documentation was written, the commercetools connection check reports success whether or not the credentials are valid, so a passing check is not evidence that the connection works. An incorrect API Url, Client_Id, Client_Secret, or Scope, or a project in an unsupported region, will surface only when the first record fails to transfer, usually as an authorization error. After saving the settings, run a small Manual Sync from Dashboard → Integration Monitoring → Manual Sync and confirm the record transfers before enabling scheduled data flows. If it fails, re-check each of the four values and the project region, and review the failure in Dashboard → Integration Monitoring → Error Logs. Common failures and their resolutions are described in commercetools Error Messages.

Rotating credentials follows the same path: create a replacement API client in the Merchant Center, update Client_Id and Client_Secret on the subscription, save, and confirm with a Manual Sync before retiring the old client.

Currently, initialization is not supported for commercetools in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process.

To move an existing catalog or customer base across after the connection is established, use the bulk sync using Postman procedure rather than expecting a first-connection bulk load.

Throttling prevents the commercetools API from being overwhelmed by excessive calls, preserving performance during heavy data transfers.

The throttle fields are required, but their values are pre-populated by the integration settings, so most subscribers never need to change them. Adjust them only if transfers are being rejected for exceeding commercetools request limits, or if you need to slow the integration to reduce load. commercetools publishes its request limits in Limits (retrieved 2026-07-20). Transfers that are rejected for exceeding a limit are not automatically rescheduled or resumed, so lower the throttle limit or widen the throttle interval rather than relying on a retry.

For more details on these fields and how to edit them, see Subscription Configuration – Edit.

For help with your subscription, contact iPaaS.com Support at support@ipaas.com.