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 Managed Integration Service Provider (MiSP, the partner who owns the subscription's mappings, configuration, credentials, and reconciliation) 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

Orders sent from iPaaS.com are created in ShipStation as one shipment per shipping address. Each address is attempted on its own, so one address failing does not stop the others; the transfer then fails with a single message that lists every address that did not ship.

One or more shipments could not be sent

SHST-EXTN-1004 - {failed} of {total} shipment(s) for this transaction could not be sent to ShipStation. Details: Shipping address {address}: {reason} | ...

  • Description: One or more of the order's shipping addresses could not be created or updated as a ShipStation shipment. The message counts the failures, adds "Shipments for the other addresses were sent." when some succeeded, and lists each failed address with its reason. For a line item whose ShipToAddressExternalId value matches none of the order's addresses, the value itself is shown in place of the address. The reasons you will see are No shipping address on the transaction matches the ship-to address assigned to its line items (a line item's ShipToAddressExternalId custom field names an address that is not on this order), No ShipStation warehouse or ship-from address is set for this shipping address (the address's ShipStation Ship From Location custom field is empty or names a location that does not exist in your ShipStation account, and no Shipment_ShipFrom address fields are mapped), and ShipStation could not create or update the shipment: {message} (ShipStation rejected the shipment; its own message follows, for example a validation error on the ship-to address or the package weight, "Requested value '…' was not found" for a currency code or weight unit ShipStation does not accept, an SHST-EXTN-1001 error, or SHST-EXTN-1003 below; the same reason also carries SHST-AUTH-1002 when a V2 setting is missing, in which case ShipStation was not contacted). The addresses that are not listed shipped successfully and their shipments are recorded, so a retry updates them instead of creating them again. iPaaS.com also requeues the failed transfer and retries it automatically.

  • Resolution: Read each listed reason. For an address that was not matched, confirm the order source populates the ShipToAddressExternalId custom field on each line item with the exact external id registered on one of the order's addresses, or add the missing address to the order. For a missing ship-from location, populate the address's ShipStation Ship From Location custom field in the order source with the exact name of a Ship From Location in your ShipStation account. For a ShipStation rejection, correct the order data or mapping the ShipStation message points at; "Requested value '…' was not found" usually means the order's Currency, Package Weight Unit, or Weight Unit custom field holds a value outside the accepted list in the ShipStation Installation Instructions. Then re-run the transfer, or let the automatic retry pick it up; shipments that were already sent are updated, not duplicated. If the reason is unclear, your MiSP can escalate it to iPaaS.com Support.

Shipment created without a shipment id

SHST-EXTN-1003 - ShipStation accepted the shipment but did not return a shipment id for it, and it could not be found by its external shipment id either, so it cannot be linked back to iPaaS.com. Check ShipStation for the shipment before re-running the transfer.

  • Description: ShipStation accepted the request to create a shipping address's shipment, but its response did not contain the shipment's id. The integration then looked the shipment up in ShipStation by its external shipment id (the address's iPaaS.com reference) and did not find it either, so it cannot record which ShipStation shipment belongs to that address. When that lookup does find the shipment, its id is recorded and no error is reported. This error is reported for the address inside SHST-EXTN-1004 above.

  • Resolution: Look in ShipStation for a shipment carrying this order's number for that address. If there is none, the next attempt creates it normally. If there is one, because its id was never recorded, the next attempt to send the order creates a second shipment for the same address rather than updating the first. That attempt may be iPaaS.com's automatic retry, so the second shipment can appear without anyone re-running the transfer. Keep the most recently created shipment, which is the one later updates of the order go to, and cancel the earlier one in ShipStation. If the error repeats for the same address, capture the transfer from Integration Monitoring and, through your MiSP, escalate to iPaaS.com Support.

An order that ShipStation itself rejects (a malformed ship-to address, a missing package weight, or other required shipment data) surfaces inside SHST-EXTN-1004 with ShipStation's own text; read that text to identify the field at fault, 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. Only shipments for which a label has been generated in ShipStation can be retrieved by this flow.

  • Resolution: Confirm the shipment exists in ShipStation, has a label, 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. Shipments the integration created carry the originating order's identifier in the ShipStation order key and attach to it directly; any other shipment is matched by the ShipStation order id the shipment carries. When no order is found, the tracking record is written without a parent and the transfer fails with the platform error VALD-1002 - Required field (ParentId) is null or empty in your request, then requeues until the order exists. 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); for order transfers, also confirm the V2 API Base URL and V2 API Access Key.

V2 API setting missing

SHST-AUTH-1002 - The ShipStation {V2 API Base URL | V2 API Access Key} setting is empty. Enter it in the ShipStation subscription settings: orders are sent to ShipStation as V2 shipments and cannot be sent without it.

  • Description: Orders are sent to ShipStation as V2 shipments, which need both the V2 API Base URL and the V2 API Access Key settings. iPaaS.com does not save the subscription settings while either is empty, so this error occurs when a subscription's settings were saved before the two settings became required and one or both of them are missing. The message names the missing setting (the V2 API Base URL first, when both are missing), and the integration stops before making the V2 request. The error can appear on its own or inside the details of SHST-EXTN-1004.

  • Resolution: In the ShipStation subscription settings, enter the V2 API Base URL and the V2 API Access Key (see the ShipStation Installation Instructions for where to find the key), then re-run the transfer.

ShipStation API Errors

Error returned by ShipStation

SHST-EXTN-1001 - Error calling ShipStation for {operation}: {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. The operation is named as it appears in the transfer's activity log, for example CREATE SHIPMENT, LIST WAREHOUSES, or LIST STORES. When ShipStation cannot be reached at all, the message ends with the connection error instead of an HTTP code. When the failing call is a lookup made by a mapping, such as the Ship From Location lookup, the message appears inside the mapping error for that field, for example "applying mapping to Shipment_WarehouseId with error message SHST-EXTN-1001 - …". This is the catch-all for ShipStation rejecting a call on either API generation: a validation or invalid-request error (commonly a missing or malformed ship-to address, an invalid package weight, or a currency code or weight unit ShipStation does not accept, HTTP 400), an authentication failure (an unauthorized response caused by an incorrect API Key, API Secret, or V2 API Access Key), a referenced record ShipStation could not find (HTTP 404), or a rate limit exceeded (HTTP 429). During an order transfer this error is reported per shipping address inside SHST-EXTN-1004.

  • 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 credentials in the subscription settings are correct and active, using the V1 API Key and API Secret for inbound transfers and the store lookup, and the V2 API Access Key for creating and updating shipments. For a rate limit, reduce the Concurrent Batch Executions setting. 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.

Deprecated Errors

The following codes were raised by earlier releases and are no longer produced. They are listed so an older log entry can still be understood; the numbers are not reused.

  • SHST-VALD-1001 - OrderDate Is Required: orders are now created as shipments and no longer require an order date.

  • SHST-VALD-1003 - Ship To Address Is Required: an order with no destination address now creates no shipment and records the reason in the transfer's activity log instead of failing.

Related Documents

Related Articles
Did this answer your question?