New answers tagged support
No, Area51 isn't in the API; it's different enough from the Q&A sites that it'd have to have a rather different one anyway. There are currently no plans to make an Area51 API either.
I figured out my error. I did not have the client_id set. I had to remove the preview flag. I still can't create a question though: 404 when posting a question to the Stackexchange API
Did you url-encode the code and the client_secret? Here's a successful auth (from Firebug): POST: POST /oauth/access_token HTTP/1.1 Host: stackexchange.com User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:27.0) Gecko/20100101 Firefox/27.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: ...
It's a bit of a Catch-22. Work around it by making an app (or script) post for your app (or script), but put "(Placeholder)" in the title. Also, indicate in the post that the app is not yet ready for prime time. This has already been done a few times, for example: "Chatdump - a site monitor (placeholder)" "A small Stack Overflow browser for Android, for ...
Here is a Firefox plugin which purports such an ability: Print Pages to PDF I've tried it myself, and it works quite well for offline purposes. I think the terms of service only allow the resulting document to be used for personal, non-commercial use. Here's a screencap which demonstrates it's features:
Markdown. While you could use HTML (just like you can in posts), each time you use HTML instead of Markdown to format a post, Evan Carroll rapes a little kitten and sticks another needle in his Jeff Atwood voodoo doll.
You can use these endpoints to provide a user with preview functionality, since you can get back the submitted content as Stack Exchange would render it without the user having to actually create something in the system. I assume this is the primary use case.
Another very useful tool when working with APIs is the Chrome app "Postman - REST Client". You can even make POST requests, save the requests you make and organize them into collections. Check it out here!
The API allows you to set a pagesize of 0 to 100 (with the exception of the /sites route, which allows larger values), and defaults to a maximum of 30 items in the response. To get all of the items applicable to the API query, you need to check the has_more field to determine if you need to request subsequent pages via the page parameter. This is covered in ...
Top 50 recent answers are included