Skip to main content

Zuper Error Messages

Error messages you may see in the iPaaS.com logs for the Zuper integration, what causes them, and how to resolve them.

Overview

This article catalogs the error messages the Zuper integration can write to the iPaaS.com error logs during data synchronization, what each one means, and how to resolve it.

Supported Flows

  • Connection and Authentication

  • Data Transfer to and from Zuper

  • Product Inventory

Connection and Authentication

Connection validation failed

Error message: The connection to Zuper could not be validated.

  • Description: iPaaS.com could not establish a valid connection to Zuper when the subscription was tested or used. This usually means the API key or API URL is missing, incorrect, or the key is inactive.

  • 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.

Unauthorized

Error message: Error calling Zuper (Http Code: Unauthorized).

  • Description: Zuper rejected the request because the API key is invalid or does not have access. The message includes the HTTP code Unauthorized (401).

  • Resolution: Verify the API key in the subscription settings matches an active key in your Zuper account with sufficient permissions.

Data Transfer to and from Zuper

Zuper request failed

Error message: Error calling Zuper [operation]: [message from Zuper] (Http Code: [code]).

  • Description: A request to Zuper did not succeed. The [operation] identifies what was being done (for example, creating a customer or fetching an invoice), the [message from Zuper] is the reason Zuper returned, and the [code] is the HTTP status. 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); NotFound (404) means a referenced record was not found.

  • Resolution: Read the message from Zuper included in the error to see what Zuper rejected, and correct the underlying data or mapping. Common causes are a required field that is not mapped, or a value (such as a product category, location, or customer) that must already exist in Zuper before the transfer.

No response from Zuper

Error message: [transport error message].

  • Description: The request to Zuper could not be completed because of a network or connectivity problem, so no response was received.

  • Resolution: Retry the transfer. If the problem persists, confirm the API URL is correct and reachable, then contact iPaaS.com Support.

Product Inventory

Product Id is required

Error message: 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.

Related Documents

Did this answer your question?