Braad

Note: You probably do not need this plugin. The REST API already supports adding the query param <code>?_embed</code> to your URL and the response will then include all “embedded media”, including the featured image, and the data you get there is exactly what this plugin gives you. The only reasons to use this plugin at this point are if you prefer to have the featured image data in a top level field in the response rather than among other embedded media in the <code>_embedded</code> field, and if you always want the featured image data in the response rather than having to ask for it with <code>?_embed</code>. I still use this plugin because I do usually want both these things, but definitely give <code>?_embed</code> a try before using this plugin. 🙂
Version 2 of the WordPress REST API returns a <code>featured_media</code> field (formerly featured_image) on the post object by default, but this field is simply the image ID.
This plugin adds a <code>better_featured_image</code> field to the post object that contains the available image sizes and urls, allowing you to get this information without making a second request.
It takes this:
<pre><code>"featured_media": 13,
</code></pre>
And turns it into this:
<pre><code>"featured_media": 13,
"better_featured_image": {
 "id": 13,
 "alt_text": "Hot Air Balloons",
 "caption": "The event featured hot air balloon rides",
 "description": "The hot air balloons from the big event",
 "media_type": "image",
 "media_details": {
 "width": 5760,
 "height": 3840,
 "file": "2015/09/balloons.jpg",
 "sizes": {
 "thumbnail": {
 "file": "balloons-150x150.jpg",
 "width": 150,
 "height": 150,
 "mime-type": "image/jpeg",
 "source_url": "http://api.example.com/wp-content/uploads/2015/09/balloons-150x150.jpg"
 },
 "medium": {
 "file": "balloons-300x200.jpg",
 "width": 300,
 "height": 200,
 "mime-type": "image/jpeg",
 "source_url": "http://api.example.com/wp-content/uploads/2015/09/balloons-300x200.jpg"
 },
 "large": {
 "file": "balloons-1024x683.jpg",
 "width": 1024,
 "height": 683,
 "mime-type": "image/jpeg",
 "source_url": "http://api.example.com/wp-content/uploads/2015/09/balloons-1024x683.jpg"
 },
 "post-thumbnail": {
 "file": "balloons-825x510.jpg",
 "width": 825,
 "height": 510,
 "mime-type": "image/jpeg",
 "source_url": "http://api.example.com/wp-content/uploads/2015/09/balloons-825x510.jpg"
 }
 },
 "image_meta": {
 "aperture": 6.3,
 "credit": "",
 "camera": "Canon EOS 5D Mark III",
 "caption": "",
 "created_timestamp": 1433110262,
 "copyright": "",
 "focal_length": "50",
 "iso": "100",
 "shutter_speed": "0.004",
 "title": "",
 "orientation": 1
 }
 },
 "post": null,
 "source_url": "http://api.example.com/wp-content/uploads/2015/09/balloons.jpg"
},
</code></pre>
The format of the response is nearly identical to what you would get sending a request to <code>/wp-json/wp/v2/media/13</code> or using <code>?_embed</code>. When no featured image has been set on the post the <code>better_featured_image</code> field will have a value of <code>null</code>.
I’ve done some basic performance tests that indicate the difference in response times with and without this plugin to be about 10-15ms for a collection of 10 posts and 0-5ms for a single post. For me this is much faster than making a second request to <code>/media/</code>, especially for multiple posts.
As of version 1.1.0, there is a filter <code>better_rest_api_featured_image</code> that allows you to add custom data to the better_featured_image field. The filter is directly on the return value of the function that returns the better_featured_image field. This can be used to do things like add custom image meta or an SVG version of the image to the response. Here’s an example of how you might use it:
<pre><code>add_filter( 'better_rest_api_featured_image', 'xxx_modify_rest_api_featured_image', 10, 2 );
/**
 * Modify the Better REST API Featured Image response.
 *
 * @param array $featured_image The array of image data.
 * @param int $image_id The image ID.
 *
 * @return array The modified image data.
 */
function xxx_modify_rest_api_featured_image( $featured_image, $image_id ) {

 // Add an extra_data_string field with a string value.
 $featured_image['extra_data_string'] = 'A custom value.';

 // Add an extra_data_array field with an array value.
 $featured_image['extra_data_array'] = array(
 'custom_key' => 'A custom value.',
 );

 return $featured_image;
}
</code></pre>
This plugin is on <a href="https://github.com/BraadMartin/better-rest-api-featured-images" title="Better REST API Featured Images" rel="nofollow ugc">on Github</a> and pull requests are always welcome. 🙂

Better REST API Featured Images

Does what id says, and it helps me a lot while building the theme in Angular2. Only one GET to have Post and Featured Image details!



Perfect! Must be in the API core

The Plugin works very well and saves time, thanks!



Works also with REST API V2

Thanks Martin.
This plugin does excectly what is says it would do.
And this should definitely be integrated in the main api code!!!



Great plugin, why is this not in the default API?

Awesome

Adds a top-level field with featured image data including available sizes and URLs to the post object returned by the REST API.

Pericor

Automatically stores the meta data from the <code>meta</code> field of a wordpress REST API posts (<a href="https://developer.wordpress.org/rest-api/reference/posts/#create-a-post" rel="nofollow ugc">/wp-json/wp/v2/posts</a>) or pages (<a href="https://developer.wordpress.org/rest-api/reference/pages/#create-a-page" rel="nofollow ugc">/wp-json/wp/v2/pages</a>) POST in the meta data associated with the created page or post using <a href="https://developer.wordpress.org/reference/functions/update_post_meta/" rel="nofollow ugc">update_post_meta</a>. The key / value information sent in the REST POST ‘meta’ object field is stored as both ‘key’ and ‘_key’ to support different plugin formats. 
For example, if trying to set the YOAST SEO Plugin values dynamically when creating a page from the REST API, you would simply add the fields to the meta field of the REST POST data when you POST the endpoint, and the plugin values will be added to the page:
<pre><code>{
...
 'meta': {
 'yoast_wpseo_title': "Title set from REST call"
 'yoast_wpseo_metadesc': "Meta description set from REST call"
 }
...
}
</code></pre>
Use this plugin when dynamically creating pages with the WordPress REST API to support modifying plugin settings for pages/posts created using the REST API!
A guide on how to use this plugin to generate a page/post with plugins configured from the REST API is <a href="https://www.pericror.com/software/generating-pages-posts-plugins-using-wordpress-rest-api/" rel="nofollow ugc">available at Pericror.</a>
Inspired as a broader alternative to <a href="https://github.com/ChazUK/wp-api-yoast-meta" rel="nofollow ugc">wp-api-yoast-meta.</a>
Compatible with the <a href="http://v2.wp-api.org/" rel="nofollow ugc">wordpress rest api version 2.</a>

REST API Meta Support

This plugin was developed and used to generate pages with a review plugin configured programatically using the rest API per page and works as described.

Works as Described

Stores meta data (i.e plugin settings) from the meta field of a WP REST API posts or pages POST creation call in the created page or post meta data.

Better REST API Featured Images vs REST API Meta Support