equest shipstation API feature development(ETS Y)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2024 03:46 AM
I am an Etsy seller and I encountered a problem when using the Shipstation API. The process is as follows:
Please see below:
url = "ssapi.shipstation.com/orders/markasshipped"
Parameters:
payload = {
"orderId": 491876446,
"carrierCode": "sf-express",
"shipDate": "2024-11-12",
"trackingNumber":"9300120111412091388309 ",
"notifyCustomer": false,
"notifySalesChannel": true
}
Description: The order number is: 3476386026, (orderId: 491876446, orderNumber: 3476386026) is an order from the etsy channel.
notifySalesChannel is true, requiring the shipstation to notify etsy of the shipment, and the shipstation requests createReceiptShipment in the etsy api. The description of createReceiptShipment is as follows:
Shipstation API request results:{"orderId":491876446,"orderNumber":"3476386026"}
The shipstation UI shows:
From the above description, when Shipstation notifies Etsy to ship, when requesting Etsy API (createReceiptShipment), the value of field carrier_name is other, not sf-express. When I request Shipstation API (Mark an Order as Shipped), the value of field carrierCode is sf-express, maybe Shipstation has filtered it. I would like to make a request to you. Can I pass the same value of field carrierCode to field carrier_name of Etsy API (createReceiptShipment) when requesting Shipstation API (Mark an Order as Shipped), instead of other? Are you willing to develop this requirement?

