Overview
This article catalogs the error messages you may encounter while synchronizing data between iPaaS.com and ShipHawk, grouped by the flow that produces them. Each entry lists a stable error code you can search for on this page, the message as it appears in the iPaaS.com error logs (under Dashboard > Integration Monitoring > Error Logs), what causes it, and how to resolve it. Values shown in braces (for example, a carrier name or a SKU) are filled in with the specific record's details when the error occurs.
Some resolutions refer to your Managed Integration Service Provider (MiSP) - the partner who owns your integration's mappings, configuration and credentials, and who reconciles data between the two systems on your behalf.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Add/Update ShipHawk Shipment TO iPaaS.com
Add/Update ShipHawk Order FROM iPaaS.com
Connection
API Communication (all flows)
Error Collection
Add/Update ShipHawk Shipment TO iPaaS.com
Tracking not linked to a transaction
SHHA-NFND-1001 - ShipHawk Shipment Tracking Number is not linked to any existing iPaaS.com Transaction
Description: The shipment's order could not be matched to a transaction in iPaaS.com, so its tracking number has nothing to attach to. This usually means the order has not been transferred into iPaaS.com yet, or it transferred under a different order number than the one on the shipment.
Resolution: Confirm the order exists in iPaaS.com and that its Transaction Number matches the order number on the ShipHawk shipment, then re-run the shipment sync. If the order is present but the numbers differ, ask your MiSP to review the order-number mapping between the two systems.
Shipping method does not exist
SHHA-NFND-1002 - Shipping Method {Carrier} needs to be created manually in iPaaS.com first
Description: The carrier on the ShipHawk shipment does not match any Shipping Method configured in iPaaS.com. The comparison is case-sensitive, so a Shipping Method that differs only in letter casing will not match.
Resolution: Create a Shipping Method in iPaaS.com whose name matches the carrier shown in the message exactly, including letter casing, then re-run the shipment sync. If a Shipping Method that looks correct already exists, check it character by character against the message - a casing or spacing difference is the usual cause.
Unable to link tracking number
SHHA-BIZL-1001 - Unable to dynamically link to existing iPaaS.com Transaction Tracking by matching the Tracking Number of iPaaS.com with the Tracking Number from ShipHawk. This may result in duplicate transaction tracking records.
Description: A tracking record matching this shipment already exists on the iPaaS.com transaction, but the integration could not link the ShipHawk shipment to it. Because the link was not established, a second tracking record may be written for the same shipment.
Resolution: Review the transaction's tracking records in iPaaS.com and remove any duplicate created for this shipment. Tracking is matched on tracking number, carrier and service name together, so a difference in any of the three prevents the link - ask your MiSP to confirm those three fields are mapped consistently between ShipHawk and iPaaS.com.
Add/Update ShipHawk Order FROM iPaaS.com
Unable to link order line
SHHA-BIZL-1002 - Unable to dynamically link to existing ShipHawk Sales Order Line for SKU {Sku} using Transaction Number. This may result in duplicate Transaction Line records.
Description: The line item for the SKU shown in the message matched an existing line on the ShipHawk order, but the integration could not record the link back in iPaaS.com. Because the link was not established, a duplicate line may be written on a later sync. Line items are matched by external ID, and by SKU when no external ID is present.
Resolution: Check the order in ShipHawk for a duplicate line with the SKU shown in the message and remove it if one was created. Confirm that the SKU is identical in both systems, since the SKU is what the match falls back to when the line has no external ID yet. If lines keep failing to link, ask your MiSP to review the line-item mapping for this collection.
Connection
ShipHawk connection unavailable
SHHA-AUTH-1001 - Unable to locate ShipHawk Call Wrapper
Description: The integration could not establish a connection to ShipHawk while updating the webhook subscription, so the ShipHawk connection was unavailable. This normally means the connection settings are missing or incorrect.
Resolution: Open the ShipHawk Subscription Settings page in iPaaS.com and confirm both the API Url and the API Key are present and correct, then retry. If the API Key may have expired or been revoked, generate a new one in the ShipHawk portal under Settings > Developer API and paste it into the API Key field.
API Communication (all flows)
ShipHawk rejected the request
SHHA-EXTN-1001 - Error calling ShipHawk CallWrapper.{action}: {ShipHawk response} (Http Code: {code})
Description: ShipHawk rejected or failed an API call while transferring a record. The message carries ShipHawk's own error detail and the HTTP status code, which together identify what ShipHawk objected to. A common example is "X-Api-Key header is missing or invalid", which means the API Key on the subscription is missing, expired or incorrect.
Resolution: Read the ShipHawk detail and HTTP status in the message and act on what it reports. For an API Key error, generate a new key in the ShipHawk portal under Settings > Developer API and update the API Key field on the ShipHawk subscription settings page in iPaaS.com. For a transient failure such as a timeout, a rate limit or an HTTP 5xx, re-run the sync. If the detail points to invalid data, correct the record in iPaaS.com and re-sync. If the same error persists after that, give the error detail and timestamp to your MiSP, who can investigate and raise it with iPaaS.com Support if needed.
ShipHawk could not be reached
SHHA-EXTN-1002 - Error calling ShipHawk CallWrapper.{action}: {transport error}
Description: The call to ShipHawk failed before ShipHawk could answer it - for example a network timeout, a DNS failure or a TLS handshake problem. The message names the ShipHawk call that was in flight and reports the underlying transport error.
Resolution: Re-run the sync; these failures are usually transient and succeed on a retry. If they continue, confirm the API Url on the ShipHawk Subscription Settings page points at your ShipHawk tenant and check whether ShipHawk is reporting a service disruption. If the API Url is correct and ShipHawk is healthy, pass the error and timestamp to your MiSP.