Skip to main content
Published: October 16 2006, 3:00:00 PMUpdated: September 23 2022, 3:33:23 PM

How is an RuName linked to my Application and my Tokens?


To understand this relationship, lets first look at what each of these parameters are, how they are defined, and how they are used.

Application Name ( 'Application')

When you join the developers program, you are given a set of developer keys. The Developer Name defines your account, and is the same for Production and Sandbox. The Application Name defines a specific application you are creating. The certificate simply is a 'key' required when making API calls.  A developer account can have multiple Applications, each defined by its own Application Name. Typically however, there is a one-to-one ratio between Application Name and Developer Name.  All API calls you make are tracked by your Application Name.


An Runame is simply a 'key' that defines a set of parameters for your Auth and Auth signin flow. An Runame specifically defines the Accept and Reject URL to be used, the optional Privacy Policy, and the Token Return Method.  The Runame is linked directly to an Application Name. For example, when users are directed to an eBay Auth and Auth signin page such as, the Runame 'ProdTest' in this case, is used by eBay to determine the Application, and then all Auth and Auth settings which define the flow the user should be directed through.  As you can see, the Runame is the only identifying information on the signin url.

Authentication Token

An Authentication Token is tied directly to an Application and an eBay User. The token is not linked or tied to an Runame. The Runame is just a mechanism for determining the Auth and Auth settings and referring Application. Once a token is generated, there is no link to the originating Runame.  Additionally, all tokens for an application can be generated using the same Runame.

Additional Resources


How well did this answer your question?
Answers others found helpful