svrooij

Since wordpress version 4.9.? wordpress includes the functionality provided by this plugin in the core of wordpress.
Checkout https://developer.wordpress.org/rest-api/using-the-rest-api/global-parameters/#_fields for functionality included in the wordpress core, 
they made it even better by filtering the amount of data pulled from the database.
This plugin will no longer be maintained since it has been superseded by the core functionality.
The <a href="https://wordpress.org/plugins/rest-api/" rel="ugc">wp-rest-api-v2</a> returns a lot of properties. 
It could be very useful (or mobile-data-friendly) to only return the properties needed by the application.
If you only want titles and links of some articles it doesn’t make sense to return the content or the excerpt.
This isn’t limited to posts, it also works on custom posttypes, categories, pages, terms, taxonomies and comments.
Instead of returning:
<pre><code>{
 "id": 2138,
 "date": "2015-10-25T15:31:03",
 "guid": {
 "rendered": "http://worldofict.nl/?p=2138"
 },
 "modified": "2015-10-25T15:31:03",
 "modified_gmt": "2015-10-25T14:31:03",
 "slug": "rechtenvrije-fotos",
 "type": "post",
 "link": "http://worldofict.nl/tip/2138-rechtenvrije-fotos/",
 "title": {
 "rendered": "Rechtenvrije foto’s"
 },
 "content": {
 "rendered": ".. A lot of content .. "
 },
 "excerpt": {
 "rendered": " .. A lot of content ..."
 },
 "author": 2,
 "featured_image": 2139,
 "comment_status": "open",
 "ping_status": "open",
 "sticky": false,
 "format": "standard",
 //.. even more tags ....
}
</code></pre>
It can return (with <code>fields=id,title.rendered,link</code> as GET parameter)
<pre><code>{
 "id": 2138,
 "link": "http://worldofict.nl/tip/2138-rechtenvrije-fotos/",
 "title": {
 "rendered": "Rechtenvrije foto’s"
 }
}
</code></pre>
<h4>Notes</h4>
<ol>
<li>If you specify fields so it wouldn’t return data the default response is send back to the client.</li>
<li>(for developers) something wrong with this plugin? <a href="https://github.com/svrooij/rest-api-filter-fields/" rel="nofollow ugc">Github</a></li>
<li>If you liked the plugin <a href="https://github.com/sponsors/svrooij" rel="nofollow ugc">consider sponsoring me</a></li>
</ol>

REST API – Filter Fields

This is hands-down the best REST API extension available.

Best REST API plugin

Filter the properties returned by the Wordpress rest api V2 (only needed until wordpress 4.9)

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.

REST API – Filter Fields vs WP REST API – OAuth 1.0a Server