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.

Dipankar Pal

<p>The WordPress REST API is more than just a set of default routes.But you want to add your Custom Endpoints/routes to the WP REST API ? Fantastic! Let’s get started with this plugin.</p>
<h4>Features</h4>
<p>✅ Make a API in one second only<br />
  ✅ API authentication with secret key<br />
  ✅ Deactivate secret key incase<br />
  ✅ Create Endpoint Url In 2 Seconds<br />
  ✅ Capture Api Request/Response Log into system<br />
  ✅ Creating Recent Activity<br />
  ✅ Auto Deleteting Log by the system</p>
<p>☛ <strong>You probably understand we requires lots of hours of work to make a plugins and technical supports, So if you like this plugin, you can buy me an Ice-Cream here – <a href="http://wcra.gmnckkp.in/" rel="nofollow ugc">http://wcra.gmnckkp.in/</a> <br />
   OR,<br />
   Directly here – <a href="https://www.paypal.me/dipoo7" rel="nofollow ugc">paypal.me/dipoo7</a></strong></p>
<p>☛ Firstly a Secret Key is needed to call the Custom Endpoints URL, However Admin can create ‘New Secret Key’ on plugin interface in the backend. After creating a new access, the plugin will be providing a SECRET KEY, which will be needed on requests. By default, the plugin will be providing a ROOT SECRET KEY. You can see those in ‘Endpoint URLs’ tab.</p>
<p>☛ Now coming to the Custom Endpoints URLs.This plugin provides an easy or simple way to create a Custom Endpoints/route by just one click. When You are creating an endpoint, this plugin register that ROUTE automatically with parameters(request) defined by the users in ‘Endpoint URLs’ Tab and the plugin builds an endpoint instantly. If you hit that endpoint URL, you will get a ‘Connection OK’ response instantly.That Means your endpoint uRL/Route is ready.</p>
<p>☛ Now one question could appear in your mind that what’s need to create a Custom Endpoints URL, though I need to write my own custom code to make a API .<br />
Yes, the answer is you could make a API in very less time with the Endpoint URLs, however you do not need to write/handle the API, you just hang your own code in the filter hook, provided by this plugin, once you have created an endpoint,  and enjoy the response. You can find that in Endpoint Listing panel. After defining the FILTER hook in any function page, you will be started receiving all request parameters and make functioning your API and return your output.</p>
<p>☛ This plugin exposes a simple yet easy interface to all settings. Users can control settings from the settings panel.</p>
<p>☛ One of the most features of this plugin is that it records all requests/responses and create a log, if it is TURN ON in the settings panel.Also, the plugin will remove/delete previously captured log VIA CRON, if CRON is enabled in the settings panel. The users can select their desired options to delete log in the settings panel. Please note WordPress CRON is not a real-time auto job, it could be a delay.</p>
<p>☛ There is a Recent activity tab in the admin panel. All recent actions will be recorded by this plugin and the activity would be recorded for maximum last 6 days. Admin can change the number of days from the settings panel.</p>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="869" height="418" src="https://www.youtube.com/embed/yBMjCD2Km2Q?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=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>


Ultimate Endpoints With Rest Api

The WordPress REST API is more than just a set of default routes.But you want to add your Custom Endpoints/routes to the WP REST API ? Fantastic! Let’ …

GP routing – WP compatible REST API vs Ultimate Endpoints With Rest Api