Integrate iPaaS.com with Clover to enable seamless data synchronization for customers, transactions (orders), and products.
This document is a subscription configuration reference. It describes the credentials and settings needed to connect Clover to iPaaS.com, how authentication works, and how ongoing operational settings behave. It overlaps with the Installation Instructions on first-time setup, but is intended as a standalone reference subscribers can return to when rotating credentials, switching between the Clover sandbox and production, or onboarding new team members.
How to Connect
Prerequisites
Before configuring the integration in iPaaS.com, subscribers or their MiSP must have the following in place on the Clover side:
A Clover merchant account with access to the merchant whose data will be synchronized.
A Clover app (a public app registered in the Clover Developer Dashboard) that supplies the application credentials used to authorize the connection. The app provides a Client ID and Client Secret, which iPaaS.com uses to complete the authorization exchange with Clover. For details on creating and configuring a Clover app, see Clover's developer documentation on OAuth 2.0.
Permission to authorize the app against the target merchant, so that the authorization step can complete and Clover can issue an access token.
Configuration Details
The integration connects to Clover using an access token obtained through Clover's OAuth authorization flow. Most connection values are captured automatically during authorization; the remaining settings tune how transactions are written to Clover. The values relevant to the connection are:
Environment URL: The Clover base URL that selects the environment the integration talks to — the Clover sandbox for testing or Clover production for live data. When left blank, the integration uses the environment default supplied by the platform. Example:
https://api.clover.comMerchant ID: The identifier of the Clover merchant whose data is synchronized. This value is captured automatically when the subscriber authorizes the Clover app. Example:
A1B2C3D4E5F6GAPI Key: The Clover access token used to authorize each request to Clover. This value is populated automatically when the subscriber authorizes the Clover app; it can also be supplied manually if a valid access token is already held. Example:
a1b2c3d4-5e6f-7a8b-9c0d-1e2f3a4b5c6d
Configure Subscription Settings
The subscription settings page in iPaaS.com presents the fields below. Values marked as populated during authorization do not need to be entered by hand when the subscriber completes the Clover authorization step.
Field | Description | Required | Example |
Environment URL | Clover base URL selecting the environment (sandbox for testing or production for live data). When blank, the integration uses the platform's environment default. | No |
|
Merchant ID | Identifier of the Clover merchant whose data is synchronized. Normally populated automatically when the subscriber authorizes the Clover app; may also be entered manually. | No |
|
API Key | Clover access token used to authorize each request. Normally populated automatically when the subscriber authorizes the Clover app, or entered manually if a valid token is already held. | No |
|
Employee Id | Clover employee associated with orders the integration creates. Captured automatically during authorization when available. | No |
|
Order Type Id | Clover order type assigned to orders the integration creates, so new orders carry the intended order type. | No |
|
Order Tax Id | Clover tax rate applied to orders the integration creates. | No |
|
DeleteAndRecreate | Controls how a simple product is converted to a variant product. When set, the integration deletes the existing Clover item and recreates it to apply the conversion, rather than converting it in place. This does not affect ongoing variant or inventory updates, which are always applied in place. Leave unset unless the delete-and-recreate conversion behavior is required. | No |
|
Authentication Methods
Clover connections use Clover OAuth. iPaaS.com does not store a static password; instead it obtains a Clover access token on the subscriber's behalf and sends it with every request. The flow works as follows:
The subscriber authorizes the Clover app for the target merchant. Clover prompts the subscriber to log in and grant access.
After the subscriber grants access, Clover returns an authorization code along with the merchant ID and employee ID for the authorized merchant.
iPaaS.com exchanges the authorization code for a Clover access token, using the Client ID and Client Secret from the Clover app. This exchange happens automatically — the subscriber does not handle the token directly.
The access token is stored securely with the subscription and is sent as a bearer token on every subsequent Clover request. The captured merchant ID and employee ID are stored alongside it.
Because the token is obtained automatically, the API Key and Merchant ID settings are normally populated for the subscriber during authorization. A subscriber who already holds a valid Clover access token may instead enter it manually as the API Key. For the underlying details of Clover's authorization model, see Clover's documentation on OAuth 2.0.
Initialization Support
Currently, initialization is not supported for Clover in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process. There is no bulk historical import on first connect; records synchronize going forward as transactions are polled and as outbound data flows dispatch records. Subscribers or their MiSP who need to load existing historical records can use bulk sync using Postman.
Throttling
Clover enforces rate limits on its REST API. When Clover reports that too many requests have been made in a short period (an HTTP 429 "Too Many Requests" response), the integration stops the affected call and records the condition so it can be reviewed. Subscribers do not need to configure Clover's limit directly.
Throttle fields on the subscription are pre-populated by the integration's settings and generally do not need to be changed. Subscribers who run large or frequent synchronizations should stagger their work to stay within Clover's limits. If throttling errors appear, they are surfaced in the Dashboard under Integration Monitoring in the Error Logs. For details on adjusting subscription-level throttle fields, see the Subscription Configuration – Edit article.
Related Documents