Incorrect URL encoding ignores ruparams

Why are the ruparams that I use in the following eBay SignIn url being ignored?

https://signin.ebay.com/ws/eBayISAPI.dll?SignIn&runame=myruname&ruparams=VarA%3DB12309%2VarB%3DABC123

Summary

If you need to send parameters in the Auth & Auth SignIn url to get a User's token, you need to ensure that you use the correct encoding.  For example, URL encoding for & is %26, however in the above URL, it is specified as %2.  If the encoding is incorrect, the parameters will be ignored.  To return the parameters correctly in the AcceptURL, along with the token, the above example needs to be modified as below:
https://signin.ebay.com/ws/eBayISAPI.dll?SignIn&runame=myruname&ruparams=VarA%3DB12309%26VarB%3DABC123

When the user signs in successfully, the accept URL will return the paramaters similar to the following:

https://<accepturl>?ebaytkn=<token>&tknexp=2008-07-01+21%3A26%3A28&username=<username>&VarA=B12309&VarB=ABC123

• Documentation:  Authentication & Authorization

How well did this answer your question?

Answers others found helpful

• What does " Error 931 - Auth Token is Invalid" mean?
• Troubleshooting Auth & Auth signin issues
• What happens to a user's existing Auth Token if a new one has been created via the token authorization flow?
• Routing - An API URL Query String Parameter that can be ignored
• Troubleshooting User Token issues