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.

Acato

Richard Korthuis

yoeridekker

Are you facing speed issues, using the WordPress REST API? This plugin will allow WordPress to cache the responses of the REST API, making it much faster.
This plugin offers:
<ul>
<li>Caching of all default WordPress REST API <code>GET</code>-endpoints.</li>
<li>Caching of (custom) post type endpoints.</li>
<li>Caching of (custom) taxonomy endpoints.</li>
<li>Automated flushing of caches if (some of) its contents are edited.</li>
<li>Manual flushing of all caches.</li>
<li>Manual flushing of specific caches.</li>
<li>A counter how many times a cache has been retrieved.</li>
<li>Specifying after what time the cache should be timed out.</li>
<li>Registering custom endpoints for caching.</li>
<li>Automatic cache regeneration.</li>
</ul>
WP REST Cache Pro 
For more advanced features, check out our <a href="https://plugins.acato.nl/" rel="nofollow ugc">WP REST Cache Pro</a> plugin:
<ul>
<li>Configure custom endpoints for caching through the wp-admin interface.</li>
<li>Configure relationships within endpoints.</li>
<li>No coding required.</li>
</ul>
<h3>Installation from within WordPress</h3>
<ol>
<li>Visit ‘Plugins > Add New’ (or ‘My Sites > Network Admin > Plugins > Add New’ if you are on a multisite installation).</li>
<li>Search for ‘WP REST Cache’.</li>
<li>Activate the WP REST Cache plugin through the ‘Plugins’ menu in WordPress.</li>
<li>Go to “after activation” below.</li>
</ol>
<h3>Installation manually</h3>
<ol>
<li>Upload the <code>wp-rest-cache</code> folder to the <code>/wp-content/plugins/</code> directory.</li>
<li>Activate the WP REST Cache plugin through the ‘Plugins’ menu in WordPress.</li>
<li>Go to “after activation” below.</li>
</ol>
<h3>After activation</h3>
<ol>
<li>Visit ‘Plugins > Must-Use’ (or ‘My Sites > Network Admin > Plugins > Must-Use’ if you are on a multisite installation).</li>
<li>Check if the ‘WP REST Cache – Must-Use Plugin’ is there, if not copy the file <code>wp-rest-cache.php</code> from the <code>/sources</code> folder of the WP REST Cache Plugin to the folder <code>/wp-content/mu-plugins/</code>.</li>
</ol>
Optionally: 
The default timeout for caches generated by the WP REST Cache plugin is set to 1 year. If you want to change this:
<ol>
<li>Visit ‘Settings > WP REST Cache’.</li>
<li>Change the Cache timeout.</li>
</ol>

WP REST Cache

I have been using this plugin on a few projects and it has been extremely useful, but recently I came across a few more complicated scenarios I needed to cater for and the plugin author has been extremely helpful in discussing the extra config that I needed. Definitely recommend. 

Very good plugin, very good support

slow api requests now respond in an instant. running this tool on multiple sites and it works almost by simply installing it. noice!


Great plugin! I use it for a headless WordPress instance with Nuxt 3, and it works perfectly fine.



The only thing I needed to change was the API endpoint since I created a custom endpoint to the route. But the FAQ cleared this up quickly and it works flawlessly. As a small suggestion I'd propose to add this option to the plugin's settings page for easier access.


Works well with headless WordPress and Nuxt 3


Nice one! Decreased response time by almost 60%.


Does the job

Enable caching of the WordPress REST API and auto-flush caches upon wp-admin editing.

Better REST API Featured Images vs WP REST Cache