Overview
This article catalogs the error messages the Zuper integration can record in the iPaaS.com error logs, grouped by flow. Each error carries a stable error code so you can find it here quickly — every entry lists the code, the message a subscriber sees, what causes it, and how to resolve it. Some resolutions refer to your Managed Integration Service Provider (MiSP), the partner who manages your integration's mappings, configuration and credentials, and reconciliation.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Connection and Authentication
Data Transfer to and from Zuper
Product Inventory From iPaaS.com
Error Collection
Connection and Authentication
Connection validation failed
ZUPR-AUTH-1001 - Unknown Issue
Description: Raised when iPaaS.com tests the connection to Zuper and the health check does not succeed. This usually means the API Key or API URL in the subscription settings is missing, incorrect, or the key is inactive, or Zuper could not be reached. The literal message recorded in the log is "Unknown Issue".
Resolution: Confirm the API Key and API URL in the Zuper subscription settings are correct for your region and that the key is active in your Zuper account. See the Zuper Connections and Settings article for how to obtain and enter these values.
Data Transfer to and from Zuper
Zuper API call failed
ZUPR-EXTN-1001 - Error calling Zuper {action}{: message from Zuper} (Http Code: {code})
Description: A call from the integration to the Zuper API failed. The message names the operation ({action}, for example creating a customer or fetching an invoice), the reason Zuper returned, and the HTTP status code. A code of BadRequest (400) usually means Zuper rejected the data — for example a missing required field, or a value that references a record that does not exist in Zuper; Unauthorized (401) means the API key is invalid or lacks access; NotFound (404) means a referenced record was not found.
Resolution: Read the message and HTTP code in the error to see what Zuper rejected, then correct the underlying data or mapping. Common causes are a required field that is not mapped, or a value (such as a product, location, or customer) that must already exist in Zuper before the transfer. For an Unauthorized (401) code, verify the API key in the subscription settings is active and has sufficient permissions.
No response from Zuper
ZUPR-EXTN-1002 - {transport error message}
Description: The request to Zuper could not be completed because of a network or connectivity problem, so no response was received. The message contains the underlying transport error.
Resolution: Retry the transfer. If it keeps failing, confirm the API URL in the subscription settings is correct and reachable. If the problem persists, your Managed Integration Service Provider (MiSP) can investigate the connectivity.
Product Inventory From iPaaS.com
Product Id is required
ZUPR-VALD-1001 - Product Id is required
Description: A product stock update was attempted without a Zuper product to apply it to. This happens when the product the inventory belongs to has not been synced to Zuper, so its identifier cannot be resolved.
Resolution: Ensure the product has been transferred to Zuper (see the Add/Update Zuper Product FROM iPaaS.com collection) before updating its stock, so the product identifier can be resolved.