GetUser API call cannot get access to Registration address for privacy reasons
Hi, I got a problem when I use the GetOrder API. When buyer haven't complete the payment, there is no shipping address detail return. So I decide to use the returned [BuyerUserID] as userID and ItemID as input condition to call GetUser, then I got this warning:  => Array ( [ShortMessage] => Invalid Request: Unavailable user information. [LongMessage] => Sorry, but you cannot get access to Registration address for privacy reasons. [ErrorCode] => 508 [SeverityCode] => Warning [ErrorClassification] => RequestError )  => Array ( [ShortMessage] => Unavailable user information. [LongMessage] => Sorry, but you cannot get access to seller payment address for privacy reasons. [ErrorCode] => 504 [SeverityCode] => Warning [ErrorClassification] => RequestError ) Seems like, I can't get access to the user's address details. Why??? If I got back to my ebay control panel (Selling manager pro) then select [Sold]->[awaiting payment] then I click one of buyer's purchase price. It display the completely address details. Also, if I use downloaded csv file to integrate. The address details is returned too. Why this address data can't show on API? I am using version 869 on Australia site. Please help! Best Regards Eric
For GetOrders we intentionally don't return the shipping details until the order is complete. This is to help protect the seller from shipping an item wrongly. Also we don't give registration information back for a user. See this comment, "RegistrationAddress for another user (except for Phone) is only returned if you have an order relationship with that user AND that user is registered on DE/AT/CH, regardless of your registration site and the site to which you send the request." You can find that info here,
http://developer.ebay.com/DevZone/XML/docs/Reference/ebay/GetUser.html#Response.User.RegistrationAddress. We do all of this for policy/privacy reasons and to help protect both buyers and sellers. The UI follows a bit different standards than the API because of the policy/privacy reasons.