JSON vs URL Encoded API Calls - JSON returns BAD CSRF

[sperok (Spero Koulouras)]

I was just prototyping using curl and a REST test tool before starting to code when I found this. It is obviously not a big deal to form encode, but wondering if this may be a generic defect in using the REST APIs with JSON data.

Nice catch on the int vs string @Mittineague, but removing the quotes around the category value does not have an impact on the 403 Forbidden error. If the BAD CSRF problem does get fixed it might then come into play.

Based on the example below, this may have worked at some point in time. It is failing with a fresh upgrade to 1.2.0.beta2.

@trident

While not very well documented, it is covered in the wp-discourse code.

Here’s an example in ruby (from some older stuff I was working on):

require ‘httparty’
@result = HTTParty.post(“<Discourse URL>/posts”,
:body => { :api_key => [‘discourse_api_key’], # Global API Key.
:api_username => [‘discourse_api_username’], # Username to post as.
:title => [“title”], # Title of topic.
:raw => “<contents as string>”,
:category => [‘discourse_api_category’], #Category to post to.
:skip_validations => ‘true’, #Ignores min post length, min title length… etc
:auto_track => [‘discourse_auto_track’] # User posted as will track the topic.
}.to_json,
:headers => { ‘Content-Type’ => ‘application/json’ } );