As a third party, I'd like the listing ID to populate on listings converted to transactions in the data feed

SkySlope treats listings and transactions as separate entities. So a listing has a listing ID, and converting it to a transaction gives it a transaction ID. Given that these later separate, they can become their own entities again. The problem is that when you create a listing and call the data feed you get a listing ID, and you create a transaction and call the data feed you get a transaction ID, but when you convert the listing into a transaction, you lose the transaction listing ID. Third parties cannot reliably connect a listing to a transaction when the ID is no longer visible.

0 Votes