renemanqueros

Allows developers to create REST-ish API’s that have access to all of WordPress and its plug-ins objects.
<h3>Usage</h3>
Install the plug-in as any other plug-in. 
Project is divided in two sets of files:
<pre><code>* index.php - This is where you register routes and/or middleware.
* routes/ - This is where you place your routes.
</code></pre>
<h3>Middleware</h3>
Middlewares are functions that will be executed on every call to the API, generally used to validate parameters or 
transform requests before they reach routes, code for middleware is structured like this:
<pre><code>app::middleware(function () {
 doSomething();
});
</code></pre>
<ul>
<li>Middlewares run for every Verb and do not automatically assign $_POST or $_GET to any variable</li>
</ul>
<h3>Routes</h3>
A route is where you would link a request to a function depending on its HTTP Verb. 
The routing engine will prepend /api/ to all calls and will append a trailing slash to all requests. 
A GET request would be matched like this:
<pre><code>app::get('/testget', function($req){
 return $req;
});
</code></pre>
In which:
<pre><code>* app::get - This will match up a GET request.
* '/testget' - the path the routing engine will look for.
* function(){ } ... - the function to execute when the route is matched.
* $req - parameters sent to the verb.
</code></pre>
To make a call to this route, the full path would be:
<pre><code>http://www.mysite.com/api/testget/
</code></pre>
<ul>
<li>The trailing slash is always required.</li>
<li>Parameters for all routes will be sent as the first parameter to the callback.</li>
</ul>
A route should be registered on the index file by placing a call to app::routes with the filename of the route (without the extension) as a parameter:
<pre><code>app::routes('test');
</code></pre>
<ul>
<li>All routes output their return value as a JSON encoded response.</li>
</ul>
<h3>Samples for all verbs</h3>
<ul>
<li>
GET:
app::get(‘/testget’, function($req){ 
 return $req; 
});
</li>
<li>
POST:
app::post(‘/testpost’, function($req){ 
 return $req; 
});
</li>
<li>
DELETE:
app::delete(‘/testdelete’, function($req){ 
 return $req; 
});
</li>
<li>
PUT:
app::put(‘/testput’, function($req){ 
 return $req; 
});
</li>
</ul>
<h3>Nested routes</h3>
Routes can be nested like this:
<pre><code>app::delete('/admin/machines', function($req){
 return $req;
});
</code></pre>
Which could be called by issuing a DELETE to:
<pre><code>http://www.mysite.com/api/admin/machines/<h3>Route and middleware registration</h3>
Code for the routes should be placed on a file inside the "routes" folder and then "registered" on the index.php file like this:
</code></pre>
function gp_registerapimethods() 
{ 
 app::middleware(function () {
<pre><code>});

app::routes('test');
</code></pre>
}
Only one instance of the gp_registerapimethods should exist on the index.php file. 
Middleware and Routes can have as many instances as needed. 
All routes inside the routes folder can be registered by doing this call instead of the individual route registration:
<pre><code> app::routes('*');
 <h3>Sample for everything</h3> The index.php file has the "test" route registered, and that test.php route a call for each verb which you could use as a starting point for your own services.
</code></pre>

GP routing – WP compatible REST API

Allows developers to create REST-ish API's that have access to all of Wordpress and its plug-ins objects.

Jeff Starr

This plugin does one thing: disables the WP REST API for visitors who are not logged into WordPress. No configuration required.
This plugin works with only 22 short lines of code (less than 2KB). So it is super lightweight, fast, and effective.
Note: This plugin completely disables the WordPress REST API. So it is not recommended if you need the WP REST API for any functionality.
<h3>Features</h3>
<ul>
<li>Disable REST/JSON for visitors (not logged in)</li>
<li>Disables REST header in HTTP response for all users</li>
<li>Disables REST links in HTML head for all users</li>
<li>100% plug-and-play, set-it-and-forget solution</li>
</ul>
The fast, simple way to prevent abuse of your site’s REST/JSON API
How does it work? That depends on which version of WordPress you are using..
WordPress v4.7 and beyond
For WordPress 4.7 and better, this plugin completely disables the WP REST API unless the user is logged into WordPress.
<ul>
<li>For logged-in users, WP REST API works normally</li>
<li>For logged-out users, WP REST API is disabled</li>
</ul>
What happens if logged-out visitor makes a JSON/REST request? They will get only a simple message:
“rest_login_required: REST API restricted to authenticated users.”
This message may customized via the filter hook, <code>disable_wp_rest_api_error</code>. Check out <a href="https://wordpress.org/support/topic/not-entirely-for-non-techies/#post-12014965" rel="ugc">this post</a> for an example of how to do it.
Older versions of WordPress
For WordPress versions less than 4.7, this plugin simply disables all REST API functionality for all users.
More information available below in the FAQs section.
<h3>Privacy</h3>
This plugin does not collect or store any user data. It does not set any cookies, and it does not connect to any third-party locations. Thus, this plugin does not affect user privacy in any way. If anything it improves user privacy, as it protects potentially sensitive information from being displayed/accessed via REST API.
Disable WP REST API is developed and maintained by <a href="https://x.com/perishable" rel="nofollow ugc">Jeff Starr</a>, 15-year <a href="https://plugin-planet.com/" rel="nofollow ugc">WordPress developer</a> and <a href="https://books.perishablepress.com/" rel="nofollow ugc">book author</a>.
<h3>Support development of this plugin</h3>
I develop and maintain this free plugin with love for the WordPress community. To show support, you can <a href="https://monzillamedia.com/donate.html" rel="nofollow ugc">make a donation</a> or purchase one of my books:
<ul>
<li><a href="https://wp-tao.com/" rel="nofollow ugc">The Tao of WordPress</a></li>
<li><a href="https://digwp.com/" rel="nofollow ugc">Digging into WordPress</a></li>
<li><a href="https://htaccessbook.com/" rel="nofollow ugc">.htaccess made easy</a></li>
<li><a href="https://wp-tao.com/wordpress-themes-book/" rel="nofollow ugc">WordPress Themes In Depth</a></li>
<li><a href="https://books.perishablepress.com/downloads/wizards-collection-sql-recipes-wordpress/" rel="nofollow ugc">Wizard’s SQL Recipes for WordPress</a></li>
</ul>
And/or purchase one of my premium WordPress plugins:
<ul>
<li><a href="https://plugin-planet.com/bbq-pro/" rel="nofollow ugc">BBQ Pro</a> – Blazing fast WordPress firewall</li>
<li><a href="https://plugin-planet.com/blackhole-pro/" rel="nofollow ugc">Blackhole Pro</a> – Automatically block bad bots</li>
<li><a href="https://plugin-planet.com/banhammer-pro/" rel="nofollow ugc">Banhammer Pro</a> – Monitor traffic and ban the bad guys</li>
<li><a href="https://plugin-planet.com/ga-google-analytics-pro/" rel="nofollow ugc">GA Google Analytics Pro</a> – Connect WordPress to Google Analytics</li>
<li><a href="https://plugin-planet.com/head-meta-pro/" rel="nofollow ugc">Head Meta Pro</a> – Ultimate Meta Tags for WordPress</li>
<li><a href="https://plugin-planet.com/simple-ajax-chat-pro/" rel="nofollow ugc">Simple Ajax Chat Pro</a> – Unlimited chat rooms</li>
<li><a href="https://plugin-planet.com/usp-pro/" rel="nofollow ugc">USP Pro</a> – Unlimited front-end forms</li>
</ul>
Links, tweets and likes also appreciated. Thank you! 🙂

Disable WP REST API

while the plugin si deadsimple and very low resource impact, keep in mind that there are plugins that need the rest to work with no auth (ex. contact form 7).

dead simple and efficient, but be aware

Disables the WP REST API for visitors not logged into WordPress.

GP routing – WP compatible REST API vs Disable WP REST API