Hello! I have a custom piece of software integrating with the ShipStation API. Have spent all morning on figuring out why some of our orders are going through to the ShipStation and some aren't. We're giving our users the ability to select a specific carrier/service OR indicate to the shipper to use the cheapest available option.
When the user selects cheapest we omit the "carrierCode" and "serviceCode" params in the body of the request. Historically this has worked fine (since they're optional fields) but starting on March 22nd requests that omit those fields throw an "Object reference not set to an instance of an object" error. We'll remove the ability for users to select "Cheapest" as an option for the time being but I just wanted to bring this bug to your attention.
Thank you!
Hunter
When the user selects cheapest we omit the "carrierCode" and "serviceCode" params in the body of the request. Historically this has worked fine (since they're optional fields) but starting on March 22nd requests that omit those fields throw an "Object reference not set to an instance of an object" error. We'll remove the ability for users to select "Cheapest" as an option for the time being but I just wanted to bring this bug to your attention.
Thank you!
Hunter