6
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.
4
The \r\n issue was solved when I changed to a POST request.
But, since I was retagging questions (didn't really need to change the body, just resend it), I ended up using the body_markdown, encoded with HTMLParser.HTMLParser().unescape()
body_markdown = str(HTMLParser.HTMLParser().unescape(question_data['items'][0]['body_markdown']))
And then sending it ...
3
You cannot use a standard GET request. You must obtain the access_token and then POST the necessary parameters.
The steps are currently:
Setup:
Register your app.
Link it with a post here on Stack Apps that has a legitimate [app] or [script] tag. In most cases you will also tag it with placeholder.
In your app:
Have the user authorize your app and ...
3
This is a documentation bug in my opinion. The "via Example App" was never included, nor should it be.
A user is fully responsible for his or her content, it doesn't, and shouldn't, matter how that content was posted. Whether via: the web page, the Android App, a custom Stack App, or via Pony Express -- the content is what matters.
A rogue app would ...
3
I've just done a couple of tests with my placeholder app. Even though the question is closed, I was able to generate a new access token (following the regular procedure) for my sockpuppet account, and with it I was able to edit an answer in the Sandbox. The token for my regular account continues to work as well.
When the post is deleted, write access is ...
3
It is not currently possible.
At the moment it is only possible to post comments with the API.
(and when/if posting answers can be done using the API, it will follow the restrictions of the site, if not even stricter)
2
Write methods have been added to an unreleased version of the API that's used by the official (albeit in-development) Android app, so it's expected that they'll be made available at some point after that app (and perhaps the one for iPhone) are released to the general public.
…which has now happened. Various write methods are available as of the 2.2 ...
2
Update: As of api-v2.2, it's also possible to write questions and answers via the API.
There are at least a few examples in use, of API 2.1 apps, that write comments. See:
The Quick Media Solutions app
The StackX Android app
The SX.el Emacs app
Re:
Am I correct in thinking that only comments can be written and not questions?
Yes, that's correct. ...
2
You should be POST'ing your parameters, form encoded, rather than putting them on the Url.
GET'ing should fail more gracefully than that though, I'll get a better error message in there in the next deploy.
2
See What can I do when getting “We are no longer accepting questions/answers from this account”?.
You didn't provide which site you ran the /docs/create-question post on.
But, looking at your network profile, I can see that you might well be question-banned on Stack Overflow (Lots of questions with few upvotes and none of them marked answered). It's ...
2
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 ...
2
Yes. You can pass a filter, and you should (for all the standard reasons).
First: On the doc page, changing the filter or preview, etc. will not change the URL for write methods.
Write methods must POST to the API, which means that parameters are supposed to be sent form encoded, not in the URL. (This API bakes some things, like post ID, into the route. ...
1
Is your app listed here? If so, you should edit its entry and paste the URL to this question in the field Stack Apps Post (optional). If you don't have any apps there, you need to create one first and add the question later.
1
Annoyingly, the problem was here: (url-request-method "post").
Changing that to (url-request-method "POST") fixes everything.
1
This has been implemented in API version 2.2.
To list the available close reasons, make a call to /questions/{id}/close/options. The result will list all valid close reasons, including pre-existing duplicate suggestions and off-topic comments.
You cannot assume that a close option will be available without calling this method to see if it actually is. ...
1
Just for posterity:
Version 2.1 (released 2012-09-04) supported posting comments.
Version 2.2 (released 2014-02-10) supports posting questions, answers, and comments.
More reading material on write access here.
Only top voted, non community-wiki answers of a minimum length are eligible
