Andr&eacute; Boekhorst

This plugin combines the two of the best WordPress plugins: <a href="https://wordpress.org/plugins/advanced-custom-fields/" title="Advanced Custom Fields" rel="ugc">Advanced Custom Fields</a> and <a href="https://wordpress.org/plugins/json-rest-api/" title="WP REST API" rel="ugc">WP REST API</a>.
This plugin is based on the work from<a href="https://github.com/PanManAms/WP-JSON-API-ACF" title="Panman on Github" rel="nofollow ugc">Panman on Github</a>. He was right when he said it would be better as plugin, but it would be even better if it would be available through the WordPress Plugin Repository.
An addition made to this plugin is that each ACF Field van be filtered throug the hook: JSON_META_ACFFIELDNAME (where ACFFIELDNAME depends on the fieldname you’ve added in the Advanced Custom Fields backend.)

WP REST API Custom Fields

The plugin is installed but nothing is in the output of API

JUst does not work

Shows Advanced Custom Field output to the WP REST API for posts, pages, taxonomies and users.

Samuel Aguilera

The WordPress REST API is a great resource, but if you don’t want to use it probably you will want to close this door to your WordPress.
Unlike other popular plugins that aims to disable the REST API but only return an error, processed by the REST API, when a request is received, by default, this plugin removes all filters and actions related to WordPress REST API, and returns a 404 error for requests sent to the REST API URL endpoints, effectively blocking any use of the REST API.
Optionally you can set the REST API setting in Settings -> General page to “Logged In Only” for a less drastical action, to keep REST API access enabled but require the user to be logged in to accept the requests.
If you’re happy with the plugin <a href="https://wordpress.org/plugins/sar-disable-rest-api/reviews/?filter=5" rel="ugc">please don’t forget to give it a good rating</a>, it will motivate me to keep sharing and improving this plugin (and others).
SUPPORT: If you have any support question, please <a href="https://github.com/samuelaguilera/sar-disable-rest-api/issues" rel="nofollow ugc">create an issue at the Github repository</a>.
<h4>Requirements</h4>
<ul>
<li>WordPress 4.7 or higher.</li>
</ul>
<h4>Features</h4>
<ul>
<li>Disable WordPress core REST API for real by removing all filters and actions related to it and returning a 404 error for requests sent to REST API URL endpoints (e.g. https://example.com/wp-json/whatever ).</li>
<li>Option to require user to be logged in to use the REST API instead of completely disable it.</li>
</ul>
<h4>Usage</h4>
To disable the REST API completely simply install the plugin from the Plugins page and enable it.
If you don’t want to disable the REST API but require user to be logged in instead, go to Settings -> General page and set the REST API to option to “Logged In Only”, and click Save Changes.
You can change the option back to “Off” if you want to disable the REST API again.
To return to WordPress default, simply deactivate the plugin.

Disable REST API for Real

A simple way to disable WordPress REST API.



One click plugin

Really prevents the REST API from handling requests (default) or require user to be logged in.

WP REST API Custom Fields vs Disable REST API for Real