3 weeks ago - last edited 3 weeks ago
I am a Software developer and I'm working with a client to build out an internal user-facing application that integrates with ShipStation.
One of the issues we are running into with the API is the time-intensive and arduous process of performing bulk updates for tags, status and other properties of open orders.
Currently, the application has to make multiple API requests (one per order) to each of the following endpoints:
These operations need to be executed individually for hundreds of orders within a short span of time. However, the enforced API rate limits and the high latency of executing multiple individual API requests per order make using these endpoints at scale practically impossible.
I had hoped that the Create/Update Multiple Orders endpoint (see link to documentation below) would alleviate this issue, as I assumed it supported bulk update of all properties native to an order (specifically tagIds and orderStatus). But that does not appear to be the case - an issue I reported as a bug in another thread.
Moreover, my application needs to be able to update order status in bulk, toggling between the states awaiting_shipment and on_hold as needed. Again, the Create/Update Multiple Orders endpoint appears to support this, but in practice it does not.
I suspect that the API only allows order tags and order status to be set when creating orders in bulk - whereas setting these properties when updating orders in bulk have no effect. I am not sure if this is a bug or intended behavior. But assuming it is the latter, please enable the API to update order tags and order status (on existing open orders) via the Create/Update Multiple Orders endpoint.
3 weeks ago
Hello @PointOfSaleDev!
Thank you for your suggestion. We’ve passed it along to our development team for review.
Happy Shipping!
-Cara