Skip to main content

ShipStation Error Messages

Catalog of error messages a subscriber or their MiSP may encounter when running the iPaaS.com ShipStation integration, with the likely cause and how to resolve each one.

Overview

This article catalogs the error messages a subscriber or their MiSP may encounter while running the iPaaS.com ShipStation integration. Each entry carries a stable code you can search for on this page (for example, SHST-EXTN-1001): ShipStation integration codes have three segments (SHST, a category, and a number), while platform errors raised by the iPaaS.com API itself use two segments (for example, EXTN-1002), so the number of segments tells you which catalog to look in. All of these errors surface in the iPaaS.com Dashboard, in Integration Monitoring, and in the Error Logs for the affected transfer. Reviewing the failed transfer in those locations is the starting point for every error below.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

Supported Flows

  • Add/Update ShipStation Order FROM iPaaS.com

  • Add/Update ShipStation Shipment TO iPaaS.com

  • Connection and Authentication

  • ShipStation API Errors

  • General and Identifier

Error Collection

Add/Update ShipStation Order FROM iPaaS.com

Order Date Missing

SHST-VALD-1001 - OrderDate Is Required

  • Description: An order was sent to ShipStation without an order date. ShipStation requires every order to carry a date, so the integration stops the transfer before it reaches ShipStation when the mapped Order Date value is empty.

  • Resolution: Confirm the source record has an order date and that the Order Date field is mapped on the Add/Update ShipStation Order FROM iPaaS.com collection. If the source can produce orders with no date, populate the Order Date mapping with a value that is always present, then re-run the transfer.

An order that ShipStation itself rejects (a missing or malformed ship-to address, or other required order data) surfaces as SHST-EXTN-1001 (see ShipStation API Errors); read the message ShipStation returned to identify the field at fault, confirm the order has a complete ship-to address, correct the source record or mapping, then re-run.

Add/Update ShipStation Shipment TO iPaaS.com

Shipment Not Found

SHST-NFND-1001 - Shipment Id {id} not found

  • Description: A Manual Sync was requested for a specific shipment, but ShipStation has no shipment with that identifier. This usually happens when the identifier was mistyped, the shipment was voided or removed in ShipStation, or the shipment had not yet been created when the sync ran.

  • Resolution: Confirm the shipment exists in ShipStation and that the identifier used for the Manual Sync is correct. If the shipment is valid and present, allow the regular inbound polling to pick it up, or re-run the Manual Sync with the correct identifier. If the shipment exists in ShipStation but still cannot be retrieved, your MiSP can escalate it to iPaaS.com Support.

Parent Order Missing For Shipment

  • Description: Inbound shipments attach to an order that must already exist in iPaaS.com. The integration does not automatically create a missing parent record, so a shipment whose order has not yet been transferred into iPaaS.com cannot be matched and the transfer fails. This is a record-matching outcome rather than a coded ShipStation error, so it has no SHST- code.

  • Resolution: Make sure the related order has been transferred into iPaaS.com before the shipment is processed. Re-run the order transfer first, then re-run the shipment transfer or allow the next inbound poll to retry. If the order is present in iPaaS.com but the shipment still cannot be matched, your MiSP can escalate it to iPaaS.com Support.

Connection and Authentication

Connection validation failed

SHST-AUTH-1001 - The ShipStation connection could not be validated.

  • Description: The integration established the connection but the validation check against ShipStation did not succeed. The message shown is the validation result returned during the check. This usually indicates an incorrect API Key, API Secret, or API Url, or a ShipStation-side availability issue.

  • Resolution: In the ShipStation subscription settings, confirm the API Url, API Key, and API Secret are entered correctly with no extra spaces, and that the API credentials are still active in ShipStation. After correcting them, verify the fix by running a test transfer. A live authentication failure returned by ShipStation during a transfer surfaces as SHST-EXTN-1001 (see below).

ShipStation API Errors

Error returned by ShipStation

SHST-EXTN-1001 - Error calling ShipStation CallWrapper.{action}: {ShipStation response} (Http Code: {code})

  • Description: ShipStation rejected a request during a transfer, or returned an error, and the integration surfaces the operation, ShipStation's message, and the HTTP status code. This is the catch-all for ShipStation rejecting a call — a validation or invalid-request error on an order (commonly a missing or malformed ship-to address, HTTP 400), an authentication/authorization failure (an unauthorized response caused by an incorrect API Key/Secret/Url), or a referenced record ShipStation could not find (HTTP 404).

  • Resolution: Open the failed transfer in Integration Monitoring and read the message and HTTP status code ShipStation returned to identify the cause. For a validation error, confirm the order data (especially a complete ship-to address) and correct the source record or mapping. For an authentication failure, confirm the API Url, API Key, and API Secret in the subscription settings are correct and active. Correct the data or configuration and retry. If the ShipStation message is unclear or the problem persists, your MiSP can escalate it to iPaaS.com Support.

General and Identifier

Invalid record identifier

SHST-VALD-1002 - Invalid key value at {location}. MappingCollectionType = {type}, ExpectedDataType = {expected}, PKValue = {value}

  • Description: A record's identifier (or an identifier entered for a Manual Sync) does not match the format the selected collection expects — for example a whole number where a number is required, or a composite identifier that must contain the correct number of separator characters. The transfer cannot proceed until the identifier is valid.

  • Resolution: Re-enter or correct the identifier in the format the collection expects. For composite identifiers, include each part separated by the required separator character. Confirm you are using the identifier type described for that collection in its mapping documentation.

Batch run exception

SHST-EXTN-1002 - Recieved an exception during batch run on of {action}. {message}

  • Description: A grouped batch of ShipStation calls failed, and the first underlying error is included in the message.

  • Resolution: Read the included underlying message to identify the failing record or field, correct it, and re-run the transfer. If the underlying error is itself one of the codes in this article, follow that code's resolution.

Some failures surface a message that describes the integration's internal handling (an internal field, type, or processing detail) rather than a subscriber-correctable cause; these are not something a subscriber or their MiSP can resolve by changing source data or mappings. Capture the message and the affected transfer from Integration Monitoring and, through your MiSP, escalate to iPaaS.com Support so the underlying cause can be investigated.

Related Documents

Related Articles
Did this answer your question?