Overview
This article catalogs the error messages you may encounter when synchronizing data between Catsy and iPaaS.com, grouped by the mapping collection flow that produces them. Each error carries a stable code (for example, CTSY-VALD-1001) that you can search for on this page (Ctrl+F / Cmd+F) — the code stays the same even if the wording is refined later, so it is the most reliable way to find an error. Errors appear in the iPaaS.com Dashboard under Integration Monitoring and in the Error Logs.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Add/Update Catsy Category TO iPaaS.com
Add/Update Catsy Product TO iPaaS.com
Add/Update Catsy Product FROM iPaaS.com
Catsy API
Error Collection
Add/Update Catsy Category TO iPaaS.com
Invalid category ID
CTSY-VALD-1001 - Invalid category ID format (id: {Id}). The ID must begin with 'Cat' or 'Col' with exact casing.
Description: The category or collection ID does not start with the required type prefix. Category IDs must begin with Cat and collection IDs with Col, using exact casing.
Resolution: When entering an ID on the Manual Sync page, include the full ID with its prefix (for example, Cat4000696937 or Col4000012345) and verify the casing matches exactly.
Parent category not created
CTSY-EXTN-1003 - Unable to create the parent category. This will prevent the transfer of the product category.
Description: The incoming category names a parent category that could not be transferred to iPaaS.com. Because the parent could not be created, the child category is not transferred.
Resolution: Look for the parent category's own error in the same activity log and resolve it, confirm the parent category is valid in Catsy, then retry the transfer.
Duplicate category name
CTSY-BIZL-1003 - Unable to link to an existing iPaaS.com Category using Name. This may result in duplicate Category records.
Description: A category with the same name already exists in iPaaS.com, but the integration could not link the incoming Catsy category to it, so a duplicate category may be created.
Resolution: Review your iPaaS.com categories for duplicate names and ensure category names are unique and accurate so incoming records link to the correct category. If a duplicate was created, your Managed Integration Service Provider (MiSP) can reconcile the external-ID link.
Add/Update Catsy Product TO iPaaS.com
Duplicate product SKU
CTSY-BIZL-1001 - Unable to link to an existing Catsy product using sku: {sku}. This may result in duplicate product records in Catsy.
Description: A product with the same SKU already exists, but the integration could not link the incoming product to it, so a duplicate product may be created in Catsy.
Resolution: Check for duplicate SKUs and ensure each product has a unique SKU so records link correctly.
Duplicate variant SKU
CTSY-BIZL-1002 - Unable to link to an existing Catsy product variant using sku: {sku}. This may result in duplicate product variant records in Catsy.
Description: A product variant with the same SKU already exists, but the integration could not link the incoming variant to it, so a duplicate variant may be created.
Resolution: Check for duplicate variant SKUs and ensure each variant has a unique SKU.
Variant SKU matches parent SKU
CTSY-EXTN-1001 - Error running Product_POST(Sku:{sku}): "A variant sku matches the parent sku"
Description: The Catsy product has a base variant whose SKU is the same as the parent product's SKU. iPaaS.com requires every variant SKU to differ from its parent product's SKU, so Catsy rejects the product and none of it — parent or variants — transfers. This is one example of the general Catsy API error (see Catsy API error,
CTSY-EXTN-1001).Resolution: Turn on the Allow Suffix On Duplicate Variants setting on the subscription. The integration then appends -BASE to the colliding variant's SKU (for example, NOR1882104 becomes NOR1882104-BASE) and the product transfers with all of its variants; other variants are unaffected. Alternatively, change the variant's SKU in Catsy so it differs from the parent product's SKU.
Add/Update Catsy Product FROM iPaaS.com
Existing product could not be linked
CTSY-BIZL-1004 - Unable to link to an existing Catsy product using SKU {sku}. This may result in duplicate product records.
Description: The integration could not match the iPaaS.com product to an existing Catsy product by SKU, so a duplicate product may be created in Catsy.
Resolution: Verify the product's SKU matches the corresponding record in Catsy. If a duplicate was created, your MiSP can reconcile the external-ID link so future transfers update the correct product.
Product could not be created
CTSY-INTL-1001 - The product could not be created in Catsy.
Description: The integration attempted to create the product in Catsy and the create did not complete.
Resolution: Confirm the product's required fields (in particular a valid SKU) are mapped and present, then retry. If the failure persists, review the Catsy API errors recorded alongside this entry in the Error Logs (they carry the specific reason under
CTSY-EXTN-1001).
Product update missing identifier
CTSY-VALD-1002 - The product could not be updated because it has no identifier.
Description: An update was attempted for a product that has no Catsy identifier, so the update cannot proceed.
Resolution: Ensure the product has been created in Catsy before it is updated. If the product exists in Catsy but is not linked, your MiSP can reconcile the external-ID link between the iPaaS.com and Catsy records.
Catsy API
API quota exceeded
CTSY-EXTN-1002 - Catsy API quota exceeded. Too many requests. Available in {N} seconds.
Description: Catsy temporarily limited the number of requests the integration could make. Transfers resume automatically after the wait period shown.
Resolution: No action is usually required — transfers resume after the limit resets. If this happens often, lower the API Throttle Limit on the subscription settings so the integration sends requests more slowly.
Catsy API error
CTSY-EXTN-1001 - Error calling Catsy [action]: [response] (Http Code: [status])
Description: Catsy returned an error for a request. The message shown is Catsy's own response and describes the specific problem, such as a validation error, a missing required field, or the variant SKU matches parent SKU case above.
Resolution: Review the message Catsy returned in the error — it names the specific problem. Correct the underlying data or the mapping that produced the value, then retry. If the message points to a configuration your MiSP manages (mappings, presets), your MiSP can adjust it.