renemanqueros

<p>Allows developers to create REST-ish API’s that have access to all of WordPress and its plug-ins objects.</p>
<h3>Usage</h3>
<p>Install the plug-in as any other plug-in.<br />
Project is divided in two sets of files:</p>
<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>
<p>Middlewares are functions that will be executed on every call to the API, generally used to validate parameters or<br />
transform requests before they reach routes, code for middleware is structured like this:</p>
<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>
<p>A route is where you would link a request to a function depending on its HTTP Verb.<br />
The routing engine will prepend /api/ to all calls and will append a trailing slash to all requests.<br />
A GET request would be matched like this:</p>
<pre><code>app::get('/testget', function($req){
   return $req;
});
</code></pre>
<p>In which:</p>
<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>
<p>To make a call to this route, the full path would be:</p>
<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>
<p>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:</p>
<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>
<p>GET:</p>
<p>app::get(‘/testget’, function($req){<br />
   return $req;<br />
});</p>
</li>
<li>
<p>POST:</p>
<p>app::post(‘/testpost’, function($req){<br />
    return $req;<br />
});</p>
</li>
<li>
<p>DELETE:</p>
<p>app::delete(‘/testdelete’, function($req){<br />
    return $req;<br />
});</p>
</li>
<li>
<p>PUT:</p>
<p>app::put(‘/testput’, function($req){<br />
    return $req;<br />
});</p>
</li>
</ul>
<h3>Nested routes</h3>
<p>Routes can be nested like this:</p>
<pre><code>app::delete('/admin/machines', function($req){
    return $req;
});
</code></pre>
<p>Which could be called by issuing a DELETE to:</p>
<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>
<p>function gp_registerapimethods()<br />
{<br />
    app::middleware(function () {</p>
<pre><code>});

app::routes('test');
</code></pre>
<p>}</p>
<p>Only one instance of the gp_registerapimethods should exist on the index.php file.<br />
Middleware and Routes can have as many instances as needed.<br />
All routes inside the routes folder can be registered by doing this call instead of the individual route registration:</p>
<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.

miniorange

<p><strong>WordPress REST API endpoints</strong> are <strong>open and unsecured by default</strong> which can be used to access your site data. Secure WordPress APIs from unauthorized users with our <strong><a href="https://plugins.miniorange.com/wordpress-rest-api-authentication" rel="nofollow ugc">JWT Authentication for WP REST APIs plugin</a></strong>.</p>
<p>Our plugin offers below authentication methods to <strong>Protect WP REST API endpoints</strong>:<br />
– <a href="https://plugins.miniorange.com/wordpress-rest-api-jwt-authentication-method" rel="nofollow ugc">JWT Authentication</a><br />
– <a href="https://plugins.miniorange.com/wordpress-rest-api-basic-authentication-method" rel="nofollow ugc">Basic Authentication</a><br />
– <a href="https://plugins.miniorange.com/rest-api-key-authentication-method" rel="nofollow ugc">API Key Authentication</a><br />
– <a href="https://plugins.miniorange.com/wordpress-rest-api-oauth-2-0-authentication-method" rel="nofollow ugc">OAuth 2.0 Authentication</a><br />
– External Token based Authentication 2.0/OIDC/JWT/<a href="https://firebase.google.com/docs/auth/admin/create-custom-tokens" rel="nofollow ugc">Firebase</a> provider’s token authentication methods.</p>
<p>You can authenticate default WordPress endpoints and custom-developed REST endpoints and third-party plugin REST API endpoints like that of <a href="https://wordpress.org/plugins/woocommerce/" rel="ugc">Woocommerce</a>, <a href="https://www.learndash.com/" rel="nofollow ugc">Learndash</a>, <a href="https://wordpress.org/plugins/buddypress/" rel="ugc">Buddypress</a>, <a href="https://www.gravityforms.com/" rel="nofollow ugc">Gravity Forms</a>, <a href="https://wordpress.org/plugins/cart-rest-api-for-woocommerce/" rel="ugc">CoCart</a>, etc.</p>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/IsyKI7eEV-I?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&start=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<h3>WP REST API Authentication Methods in our plugin</h3>
<ul>
<li><a href="https://plugins.miniorange.com/wordpress-rest-api-jwt-authentication-method#step_a1" rel="nofollow ugc">JWT Authentication</a><br />
Provides an endpoint where you can pass the user credentials, and it will generate a JWT (JSON Web Token), which you can use to access the WordPress REST APIs accordingly.<br />
Additionally, to maintain a seamless user experience without frequent logins needed due to token expiry, you can use our <em>Refresh and Revoke token</em> mechanisms feature.<br />
When the access token expires, instead of forcing the user to log in again, the client can request a new access token using a valid refresh token.</li>
<li><a href="https://plugins.miniorange.com/rest-api-key-authentication-method#step_a" rel="nofollow ugc">API Key Authentication</a></li>
<li><a href="https://plugins.miniorange.com/wordpress-rest-api-basic-authentication-method" rel="nofollow ugc">Basic Authentication</a>:<br />
        – 1. <strong>Username: Password</strong><br />
        – 2. <strong>Client-ID: Client-Secret</strong></li>
<li><a href="https://plugins.miniorange.com/wordpress-rest-api-oauth-2-0-authentication-method#step_a" rel="nofollow ugc">OAuth 2.0 Authentication</a><br />
        – 1. <strong>Password Grant</strong><br />
            – 2. <strong>Client Credentials Grant</strong></li>
<li><a href="https://plugins.miniorange.com/wordpress-rest-api-authentication-using-third-party-provider#step_a" rel="nofollow ugc">Third Party Provider Authentication</a></li>
</ul>
<h3>Following are some of the integrations that are possible with WP REST API Authentication:</h3>
<ul>
<li>Learndash API Authentication</li>
<li>Custom Built REST API Endpoints Authentication</li>
<li>BuddyPress API Authentication</li>
<li>WooCommerce API Authentication</li>
<li>Gravity Form API Authentication</li>
<li>External/Third-party plugin API endpoints integration in WordPress</li>
</ul>
<p>You can also disable the WP REST APIs with our plugin such that no one can make API calls to your WordPress REST API endpoints.Our plugin also provides <strong>Refresh and Revoke Token</strong> that can be used to improve the API security.</p>
<h3>Benefits of Refresh Token</h3>
<ul>
<li>Enhances security by keeping access tokens short-lived.</li>
<li>Improves user experience with uninterrupted sessions.</li>
<li>Reduces login frequency.</li>
</ul>
<h3>Benefits of Revoke Token</h3>
<ul>
<li>Protects against token misuse if a device is lost or compromised.</li>
<li>Enables admin-triggered logouts or session control.</li>
<li>Useful for complying with stricter session policies.</li>
</ul>
<p>With this plugin, the user is allowed to access your site’s resources only after successful WP REST API authentication. JWT Authentication for WP REST APIs plugin will make your <strong>WordPress endpoints secure from unauthorized access.</strong></p>
<h3>Plugin Feature List</h3>
<h3>FREE PLAN</h3>
<ul>
<li>Authenticate only default core WordPress REST API endpoints.</li>
<li>Basic Authentication with username and password.</li>
<li>JWT Authentication (JSON Web Token Authentication).</li>
<li>Enable Selective API protection.</li>
<li>Restrict non-logged-in users to access REST API endpoints.</li>
<li>Disable WP REST APIs</li>
</ul>
<h3>PREMIUM PLAN</h3>
<ul>
<li>Authenticate all REST API endpoints (Default WP, Custom APIs,Third-Party plugins)</li>
<li><strong>JWT Token Authentication</strong> (JSON Web Token Authentication)</li>
<li>Login, Refresh and Revoke token endpoints for token management</li>
<li>API Key Authentication</li>
<li>Basic Authentication (username/password and email/password)</li>
<li>OAuth 2.0 Authentication</li>
<li>Universal API key and User-specific API key for authentication</li>
<li>Selective API protection.</li>
<li>Disable WP REST APIs</li>
<li>Time-based token expiry</li>
<li>Role-based WP REST API authentication</li>
<li>Custom Header support rather than just <em>Authorization</em> to increase security.</li>
<li>Create users in WordPress based on third-party provider access tokens (JWT tokens) authentication.</li>
</ul>
<h3>Privacy</h3>
<p>This plugin does not store any user data.</p>


JWT Authentication for WP REST APIs

This was the plugin that I was looking for. It is just plug and play!

Great plugin, does as it says!


Great support from the MiniOrange team! Atul and Vidushi are very helpful and lightning fast to respond.


Great Support

Secure and protect WordPress REST API from unauthorized access using JWT token, Basic Authentication, API Key, OAuth 2, or external token.

GP routing – WP compatible REST API vs JWT Authentication for WP REST APIs