Integrate iPaaS.com with Zuper to synchronize customers, employees, products, inventory, locations, and billing records (invoices, deposit tickets, and jobs) between the two systems.
How to Connect
Prerequisites
Before configuring the Zuper integration in iPaaS.com, generate an API key in your Zuper account:
API Key: In Zuper, go to Settings > Account Settings > API Keys, click New API Key, provide a name, and click Create. Save the generated key securely — you will enter it in iPaaS.com.
Configuration Details
API URL: the base API URL for your Zuper account. It is region-specific — for example, https://us-west-1c.zuperpro.com/api. If you are unsure of your region's URL, see the Installation Instructions for how to look it up.
API Key: the API key you generated in Zuper above.
Configure Subscription Settings
In iPaaS.com, open the Zuper subscription settings and provide the following:
Field | Description | Required | Example |
Name | A unique name that identifies this Zuper subscription. | Yes | Zuper - Production |
Version | The iPaaS.com integration version to use. | Yes | v1.0 |
API Key | The API key generated from your Zuper account. | Yes | Your generated Zuper API key |
API URL | The base API URL for your Zuper account. | Yes |
Authentication Methods
Zuper uses API key authentication. iPaaS.com sends your Zuper API key with every request to authenticate the connection — there is no separate secret, token exchange, or OAuth step.
To configure it:
Open the Zuper subscription settings in iPaaS.com.
Enter the API URL for your Zuper account (for example, https://us-west-1c.zuperpro.com/api).
Enter the API Key you generated in Zuper.
Save the subscription configuration.
Initialization Support
Initialization (bulk import on first connect) is supported for Location data: all iPaaS.com locations can be transferred to Zuper in a single initialization run. Other data types are synchronized individually through automatic triggers, webhook events, or Manual Sync rather than a bulk initialization.
Throttling
Throttling limits how many requests the integration sends to Zuper at once, protecting performance during heavy data transfers. The throttle fields are required, but their values are pre-populated by the integration settings and do not normally need to be changed. For details on each throttle field, see Subscription Configuration – Edit.