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)

Benjamin Intal

gambitph

When you activate this plugin, all REST API endpoints will be disabled for non-authorized requests.
Best used with any of these plugins:
<ul>
<li><a href="https://wordpress.org/plugins/jwt-authentication-for-wp-rest-api/" rel="ugc">JWT Authentication for WP REST API</a></li>
<li><a href="https://wordpress.org/plugins/oauth2-provider/" rel="ugc">WP OAuth Server</a></li>
</ul>
Blocks ALL REST API endpoints except for:
<ul>
<li>/jwt-auth/v1/token/validate</li>
<li>/jwt-auth/v1/token</li>
<li>/oauth/authorize</li>
<li>/oauth/token</li>
<li>/oauth/me</li>
</ul>
Allows all REST API endpoints if they come with a valid Bearer Token Authentication (authentication via GET URL variables are still blocked)
When used alone in your site, your REST API will essentially be disabled.
<blockquote>
Note that this plugin itself doesn’t provide JWT or OAuth authentication, it only whitelists them.
</blockquote>
<h4>Features</h4>
<ul>
<li>No settings page</li>
<li>You can whitelist other REST API endpoint via a filter hook (see FAQs below)</li>
<li>Blocks all REST API endpoints.. but</li>
<li>Allows requests with Bearer Token Authentication.. and</li>
<li>Allows <a href="https://wordpress.org/plugins/jwt-authentication-for-wp-rest-api/" rel="ugc">JWT Authentication for WP REST API</a> & <a href="https://wordpress.org/plugins/oauth2-provider/" rel="ugc">WP OAuth Server</a> authentication endpoints</li>
</ul>

Disable REST API and Require JWT / OAuth Authentication

Disables all REST API endpoints and requires JWT or OAuth Authentication.

REST API – Filter Fields vs Disable REST API and Require JWT / OAuth Authentication