A seller may be interested in various events related to an in-progress listing. One such an event is a change in the current price of a competitive-bidding listing (indicating someone has bid on the item or placed a higher bid). Another is the listing reaching the end of its duration (i.e., the end of the listing). An application can use GetSellerEvents to determine when such events have occurred and then retrieve the items for which these events have occurred and present them to the seller.
To retrieve a list of a seller's items for which seller events have occurred, use GetSellerEvents.
To specify a seller, use the eBay user ID for the seller. If the eBay user ID is not specified, seller events are retrieved for the seller identified by the authentication token.
You can use the following time-based filters to reduce the number of events returned:
For example, to retrieve only events for items that were modified during a specific time period, you can use ModTimeFrom and ModTimeTo.
Note: For information about best practices, refer to the Best Practices for GetSellerEvents and GetSellerTransactions Knowledge Base article.
At least one of the following filters must be specified:
Time-based filters can work in pairs (e.g., ModTimeFrom and ModTimeTo). If you do not specify the To filter, it is set to the time you make the call. For better results, the time period you use should be less than 48 hours.
To check if an item's current price has changed for an auction, compare the returned data with the data that was last stored.
Some baseline set of data is needed to determine what item values changed as this is not indicated in the property values of the returned ItemType objects. The ItemType objects hold only current values. For some purposes, the data values returned are of value (e.g., seeing the current price of a competitive-bidding listing,) without comparing the values to an older set of values. Many sellers wish to be able to make this determination not only to see what the current values are, but what the old values were before the seller event. To do that the application must store the returned values for a given item (e.g., to a database table,) for each GetSellerEvents call. Subsequent GetSellerEvents calls — using incrementally later date ranges — can then use this historical data in comparison with the newly returned data to highlight the changes.