[FEATURE] Access to orders convos as READ ONLY

[turboturtleD]

Lack of access to buyer messages/convos (especially pertaining to an order) is crippling for any app made for accurate production and order fulfillment. I've had to reship countless orders because this data cannot be accessed through the API. If it were made to be a READ-ONLY feature, it should prevent any issues with spam, but still allow for crucial information regarding order fulfillment to be displayed. Was really hoping to see something under receipts, I know the v3 api being used in the browser has a feature that links relevant convos to orders. Would kill to see something like that offered as an endpoint or as part of the receipt data.

Like the data that shows up from here:

https://www.etsy.com/api/v3/ajax/shop/:shopid/mission-control/orders/convos/:orderid

[etsyachristensen]

@turboturtleD I'm picking up a lot of these older Github issues now. In reviewing above I do see that the getShopReceipt does have the message_from_buyer, message_from_seller and message_from_payment. As I'm not sure of your exact use case, I can't say with certainty that this is completely fixed for you. If this is still an issue, can you elaborate more on what information you are wanting to see in the receipt specifically in this regard (not including the other association stuff asked for in the other Github issues)?

[turboturtleD]

Hey Andrew, glad to see it.

When an order comes through on the front end gui, and you are looking at the order, the browser loads data from the endpoint that I noted above: https://www.etsy.com/api/v3/ajax/shop/:shopid/mission-control/orders/convos/:orderid

This endpoint returns Etsy convo data pertaining to that order (this is not hypothetical, this actually happens - you can see the requests from the browser doing this by watching the network tab in chrome). This data is obviously critical for not missing something like a buyer requesting an address change, or other specifics or alteration requests for the order AFTER or BEFORE it has been placed, and clearly this is known to be important because your front end already provides this.

Currently the only data available via the API is data created at the moment of sale. You folks clearly have determined a way to ascertain (with relatively high accuracy) if there is a greater conversation that is associated with the sale To perform accurate order fulfillment, this additional data is really critical to be able to access. Please provide the same data to the API that you are already providing to the seller gui backend.

Will add a few screen shots if I can to show exactly what I'm talking about.

[etsyachristensen]

That is exceptionally helpful! Thanks for that. I'll make sure this is on our list of discussion topics.

[turboturtleD]

Thank you for your attention to this! I appreciate all of you folks' hard work. Many of us rely on the API so heavily for our businesses, and we are thankful for your continued openness to new ideas big and small.

[XAMelleOH]

+1 for exactly that feature.

@etsyachristensen Any updates on this topic?