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.

Daniel Bachhuber

Ryan McCue

Jonny Harris

Joe Hoyle

Rachel Baker

This plugin uses the OAuth 1.0a protocol to allow delegated authorization; that is, to allow applications to access a site using a set of secondary credentials. This allows server administrators to control which applications can access the site, as well as allowing users to control which applications have access to their data.
This plugin only supports WordPress >= 4.4.
The latest stable version is also available from the <a href="https://wordpress.org/plugins/rest-api-oauth1/" rel="ugc">WordPress Plugin Directory</a>.
<h3>New to OAuth</h3>
We strongly recommend you use an existing OAuth library. You’ll be best off if you understand the authorization process, but leave the actual implementation to well-tested libraries, as there are a lot of edge cases.
Start reading from <a href="docs/introduction/README.md" rel="nofollow ugc">the Introduction</a> to get started!
<h3>For OAuth Veterans</h3>
If you already know how to use OAuth, here’s the lowdown:
<ul>
<li>The plugin uses OAuth 1.0a in</li>
<li>We use the three-legged flow</li>
<li>To find the REST API index, apply the <a href="http://v2.wp-api.org/guide/discovery/" rel="nofollow ugc">API autodiscovery process</a></li>
<li>The endpoints for the OAuth process are available in the REST API index: check for <code>$.authentication.oauth1</code> in the index data.
<ul>
<li>The temporary credentials (request token) endpoint is <code>$.authentication.oauth1.request</code> (typically <code>/oauth1/request</code>)</li>
<li>The authorization endpoint is <code>$.authentication.oauth1.authorize</code> (typically <code>/oauth1/authorize</code>)</li>
<li>The token exchange (access token) endpoint is <code>$.authentication.oauth1.access</code> (typically <code>/oauth1/access</code>)</li>
</ul>
</li>
<li>Your callback URL must match the registered callback URL for the application in the scheme, authority (user/password) host, port, and path sections. (Subpaths are not allowed.)</li>
<li>The only signature method supported is HMAC-SHA1.</li>
<li>OAuth parameters are supported in the Authorization header, query (GET) parameters, or request body (POST) parameters (if encoded as <code>application/x-www-form-urlencoded</code>). OAuth parameters are not supported in JSON data.</li>
</ul>

WP REST API – OAuth 1.0a Server

Hello, I have made an adapter for Parse Server under Node.js with which you can link the login of any installation of wordpress in Parse Server, for that I have used your plugin, which is the one that gives us access_token and allows us to verify the authenticity Of the user registered in the server.

https://github.com/enriquecerda/parse-server-wordpress-login

Links with Parse-server Node.js

Got this working after some good amount of work! Thanks for bringing this and making API calls secure.

Worked like a charm!

Really Useful And Good Plugin
But Please
1- Reply on The Support Forum
2- Update it To Work Good With Last WordPress Verison
3 – No Clear Docs
4 - not work with localhost

Good But

Connect applications to your WordPress site without ever giving away your password.

Better REST API Featured Images vs WP REST API – OAuth 1.0a Server