It looks like your copy of the Endpoint Example SmartApp was installed at 2014-09-29 20:47:24 UTC, which is pretty recent, so I’m guessing as part of repairing your network, rejoining devices, etc., you ended up deleting those devices and then also uninstalling your existing Endpoint Example SmartApp. Is that correct? The URLs that you copy/paste from that “exampleOauth.php” page have the id of the installed SmartApp in your account built in, so when you uninstall that SmartApp, those URLs will no longer function, as that id has been deleted on our side. Our error messaging of “This request is not authorized by the specified access token” doesn’t make that particular scenario clear, admittedly. The access token should still be valid, but your URL’s would have to be altered to contain the new installed SmartApp id. For reference, here is an example URL I just copied off of that page for a switch, with identifiers substituted with colon-prefixed placeholders:
The :installed_smart_app_id placeholder would have to be substituted with a new value, and probably also switch_id if it were a device that had been deleted, in order for that :access_token to still cause the same effect as before.
If you want to go this route and need to know which id to substitute for the :installed_smart_app_id, we have an endpoint setup for such a purpose (https://graph.api.smartthings.com/api/smartapps/endpoints), documented here in Step 8, which should work with the access token you already have: http://docs.smartthings.com/en/latest/smartapp-web-services-developers-guide/implementation.html
You also could reenter that OAuth flow initiated here http://labs.smartthings.com/exampleOauth.php and copy/paste the new URL’s.
So in summary: http://labs.smartthings.com/exampleOauth.php causes a SmartApp to be installed to your location, and if you uninstall it, issues will arise in the places you have related URL’s hardcoded.