Ryan McCue

To clarify what’s been said above, uploading attachments is a separate step to setting a featured image. The documentation covers media creation, which is a two-step process: first, POST the image data to /media, which will create the post; then, update the returned post with any necessary attachment post data. The first step will give you a Post entity which will include:

{
    "ID": 4,
}

As for setting this as the featured image on a post, you can then set this on a post via the featured_image value, which should be the image ID:

{
    "featured_image": 4,
}

You’ll need to either send the X-WP-Nonce header, or the _wp_json_nonce query parameter with your request. You’ll need to generate this on the server with wp_create_nonce( 'wp_json' ), which you can then output on to the page for your script using wp_localize_script.

(This assumes you’re accessing the data from the site’s frontend, not from an external site.)

Hey chirinyu,

Due to security/privacy concerns, custom meta is now only available to authenticated users. You’ll need to authenticate as a user, then pass ?context=edit with the request.

If you need this data when unauthenticated, you can make a quick plugin to filter json_prepare_post and add in the fields you’d like:

add_filter( 'json_prepare_post', function ($data, $post, $context) {
	$data['myextradata'] = array(
		'somekey' => get_post_meta( $post['ID'], 'abcdef', true ),
	);
	return $data;
}, 10, 3 );

This data would then be available as the myextradata key in the post. 🙂

Hope that helps!

I am using the Fishpig integration of wordpress for Magento

I’m not sure on how this is integrated, however you basically want to hit the /wp-json/ rewrite in WordPress.

According to your site’s RSD, the API should be available at http://www.iamalpham.com/index.php/topics/wp-json

However, it doesn’t appear to be. 🙁 I’d ask the developer of the integration how to access it.

This is currently planned, but not yet implemented.

This is currently planned, but not yet implemented.

This has now been fixed and will be included in the next release, marking as resolved.

This should be fixed as of #50. Can you confirm please? 🙂