Hi, Is there a reason why message calls such as GetMemberMessages and GetMyMessages don't return the user's EIASToken? Would this ever be added? It would make life a bit easier when connecting received messages up to the correct customer (i.e. not having to do GetUser just to get the EIASToken).
Hi @coopaupau Are you trying to track the entire thread between a buyer and seller. If so, here is a KB article :
https://ebaydts.com/eBayKBDetails?KBid=2092 If not, can you explain what is your exact use case and how would introducing EIASToken resolve that issue ? Thanks
Hi @vijayta.developersupport It's to connect a received message to a customer, where the customer has changed their user id. For example, consider this series of events: 1. Customer with id ABCD makes an order. In my customer management system they are now identified by their EIASToken and user id. 2. On eBay, the customer changes their id from ABCD to ZXCV. 3. Then they send a message to the seller. 4. There is no EIASToken in the messaging calls, so I have to check their eBay user id to see if it matches a customer already in my database. It doesn't (because they changed their id), so the message cannot be connected to an existing customer. A new customer is created. Now to avoid that I can do GetUser on every "new" eBay user id that comes in, to find out what their EIASToken is. It would be much simpler, and reduce the volume of calls, if the EIASToken was included in the messaging calls. Unless of course I'm missing something obvious, in which case let me know.
So I take it there is no comment or update on this? I am really confused as to why you don't want to include the EIASToken on all calls that have data about a specific user. Surely every call that has data should provide the unique id of the object?