Shipping Label endpoint (map between Receipt and shipping_label LedgerItems)

[morganjury]

Currently we are able to retrieve shipping_label_id from the ledger items endpoint, which includes the cost associated with the label. I want to be able to attribute these costs to the order that the label was created for. The receipt endpoint includes a receipt_shipping_id and tracking_code but these do not include reference to the shipping_label_id in the ledger with the cost of that label.

This is preventing me from providing accurate financial reports because shipping label costs are having to be aggregated daily rather than at the order level; shipping costs have to be attributed to the date of fulfillment rather than the order date which means profit lines spike up and down depending on orders in vs orders out on any given day (e.g. weekend orders cause profit to spike up and monday fulfillment then spikes down).

I've found this post from 2013 requesting this feature but no updates are being posted anymore and I can't see a discussion in this repo on this topic: https://groups.google.com/g/etsy-api-v2/c/R7X6ZtCzjqc?pli=1

When you inspect the order in the web app, under the shipment section (e.g. "Royal Mail 2nd Class") you can see the shipping_label_id at the bottom which aligns with the refernce id in the ledger items:
Reference Label ID: #231606731492

[morganjury]

There are a few places I'm smashing data together from to try and achieve this but none of it is a complete solution, currently what I am seeing is:

1. the shipments data in the receipt object contains fields for courier name and tracking ref along with a "shipped_timestamp" whose value is end of day of the date the label was purchased
2. the receipt transaction contains fields for the expected_ship_date and shipped_timestamp (shipped_timestamp here is the timestamp when the shipping label is purchased which aligns with the created_timestamp of the ledger_entry)
3. the ledger entry contains the cost of the label and the shipping_label_id

My current approach of matching the transaction.shipped_timestamp to the ledger_entry.created_timestamp works for cases where only one postage label is purchased for the order.
In cases where a second shipping label is created, the transaction timestamps are not updated. The receipt.shipments.shipped_timestamp is updated, however, I cannot use the updated receipt.shipment.shipped_timestamp since it defaults to the end of the working day which then doesn't align with the ledger_entry.created_timestamp. This means that if the wrong postage is purchased and the second label is of a different cost compared to the first label purchased then the original label value is applied to both shipments in error.

An extension to the above is that if a shipping label is cancelled/refunded then when the next shipping label is purchased THEN the transaction.shipped_timestamp is updated.

PROPOSED SOLUTION
I am hoping someone will see this request soon and implement either:

1. Add the shipping_label_id to receipt.shipments
2. Create a GET endpoint for shipping labels which responds with: shipping_label_id, ledger_entry_id, receipt_id