I forgot to add the scope in the authentication url according to this document
1.Send a user to https://stackexchange.com/oauth, with these query string parameters
◦redirect_uri - must be under an apps registered domain
◦state - optional
Sorry about that. Turns out, return URLs were broken on stackexchange.com entirely during signup and login. A fix is out now, so any API app auth redirect issues should also be resolved with it.
Please let me know if you see any other problems. Thanks for the report, and my apologies for the delay in fixing the issue.
You have to create a post describing your application, and edit it into your application's registration.
Basically, the first arrow needs a value; and you can set it when you edit (with the second arrow). Click "Manage your applications" in the homepage sidebar of Stack Apps to get to your application list.
We require this so that:
we always have a ...
In a nutshell and don't know ask me how to write this in C#:
That first "500 error" page is normal. You must display that to the user and the user must approve.
When the user approves, the page will redirect to a page (nominally stackexchange.com/oauth/login_success) with the access_token in the URL parameters. For example:
I am aware that the last activity in this thread was more than four years ago, but since it still shows up in Google searches, I would like to point out some errors in the conversion.
I have no comments to the JSON.net related part of the converter, since that is what I searched for. But the conversion from and to UNIX timestamps is wrong.
A UNIX timestamp ...
As Brock Adams stated in his answer, you can't do this via the StacMan library.
Might I suggest an alternative?
You should be able to add new questions via the SEStandard library at SEStandard - A .NET Standard 1.1 compliant Stack Exchange client library that supports API v2.2.
using Scopes = ...
Not working on Windows (8x64)
Firstly, it doesn't not install in C:\Program Files (x86)\StackWatcher but the executable is found in C:\Users\<user>\AppData\Roaming\StackWatcher.exe
Then I wasn't able to set the the user up as it couldn't get the site list
I guess it's suffering from the same sort of error StackApplet is
You can use the API without a key, you'll just have lower limits without it. From the application registration form:
Upon registering, you'll be provided an API key which grants your app a much larger per-day request quota than using the API anonymously.