this is exactly the info i was looking for. thanks a ton for pointing it out. can't believe i missed that part of the documentation. this use of the masterkey is actually on one of our internal servers used as a management console so very protected from abuse or hacking.
unfortunately, i still have a failure -- it doesn't work. specifically, when i step through my Visual Studio debugger, as soon as i attempt to assign app.AccessToken.Token = "<my master token>", the debugger stops tracking the flow. it doesn't break, the debugger is still running, the application still runs. my code just doesn't continue past any attempt to mess with AccessToken. consequently, i cannot run anything against the telerik tables to retrieve data. i noticed just before attempting to assign the .Token (or .TokenType for that matter), the app.AccessToken object is 'null'. i expected to see the Token and TokenType structure vs. a 'null'. i didn't find anything in the documentation on the link that suggests other steps. am i still missing something?
var appSettings = new EverliveAppSettings()
ApiKey = "<our normal api key>",
UseHttps = true
var telerikApp = new EverliveApp(appSettings);
telerikApp.AccessToken.Token = "<our master key>"; //NOTE: debugger stops stepping through code here and will not continue
telerikApp.AccessToken.TokenType = "Masterkey";
var deviceList = telerikApp.WorkWith().Push().Devices().GetAll().TryExecuteSync();
var bob = deviceList.Value; //used just to provide an object list i can then start to understand and manipulate
EverliveException err = deviceList.Error;