Skip to main content

Understanding ShipStation Errors in Hurree

Troubleshoot ShipStation integration errors in Hurree. Not for general ShipStation issues.

S
Written by Shauna Doherty

If you're experiencing issues with your ShipStation widgets, this guide explains the most common errors and how to resolve them. Each error below matches the message you'll see in Hurree.

If you encounter an error that isn't covered below, please contact our support team for assistance.

Your ShipStation connection could not be verified

Explanation: This happens when the credentials used to connect your account are missing, expired, or no longer valid, preventing your widgets from retrieving updated data.

How to solve: Reconnect your ShipStation account via Hurree to restore access. Reconnecting re-establishes the connection with valid credentials, and your widgets should begin retrieving data again. If the issue continues after reconnecting, please contact our support team for assistance.

You do not have permission to access this resource

Explanation: You don't have permission to access this ShipStation resource. This can occur if your user role has changed, access has been revoked, or you have not been granted the appropriate level of access within ShipStation.

How to solve: Check that your ShipStation account has the necessary access rights, or contact your administrator and ask them to review your permissions. Once the required access has been granted, refresh your connection and try retrieving the data again.

The requested resource could not be found

Explanation: The requested ShipStation resource could not be found. This may occur if an order, shipment, store, carrier, or other record has been deleted, or if the reference is incorrect.

How to solve: Review the relevant ShipStation account and verify that the resource still exists. If it has been removed, you may need to update your widget settings or select an alternative data source.

You've reached the ShipStation API limit

Explanation: ShipStation restricts the number of requests allowed within a given time window, and if your connected widgets are pulling data at a high frequency, this limit may occasionally be reached.

How to solve: Wait a moment before trying again; your access will resume automatically once the rate limit window resets. If you are consistently hitting this limit, please contact our support team so we can review your connector configuration.

ShipStation internal server error

Explanation: An unexpected error occurred on ShipStation's servers. This is not caused by any action on your part, and as the issue originates within ShipStation's infrastructure, it is outside of our control.

How to solve: Internal server errors are typically temporary and often resolve automatically. Wait a moment and try again, or check your widget after the next scheduled sync period. If the error persists after multiple sync attempts, please contact our support team for assistance.

Other Request Errors

Explanation: You may occasionally see 400: Bad Request or 405: Method Not Supported. These indicate that one or more elements of the request sent to ShipStation were invalid, incorrectly formatted, or missing a required parameter; they are typically handled automatically and are rarely caused by anything on your side.

How to solve: Review your integration settings for any incorrect entries and try again. If either of these errors persists, please contact our support team with the error name you're seeing, and we'll investigate.

Need Additional Support?

If you've completed the troubleshooting steps above and are still experiencing issues with your ShipStation widgets, our support team is here to help. Share the error message you're seeing along with any relevant details, and we'll work with you to identify and resolve the issue as quickly as possible.

⚠️ Note: This article is intended only for Hurree users troubleshooting ShipStation Widgets errors within the Hurree platform. If you're seeing ShipStation errors outside of Hurree, please visit ShipStation's Help Center.

Did this answer your question?