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.

REST API Featured Image is a lightweight yet powerful plugin that simplifies how to retrieve featured images via the WordPress REST API. By introducing a top-level field called <code>featured_media_src_url</code>, this plugin embeds the direct URL of the featured image into your REST API responses. This eliminates the need for additional API calls to fetch featured images, resulting in faster load times and enhanced site performance.
Key Features:
– Direct Access to Featured Image URL: Adds <code>featured_media_src_url</code> to REST API responses, providing immediate access to the featured image URL. 
– Performance Optimization: Reduces the number of API requests, improving the speed and efficiency of your applications. 
– Custom Post Type Support: Fully supports custom post types, allowing you to enable or disable the featured image URL field for specific post types through the admin settings. 
– User-Friendly Configuration: Easy to install and configure without any coding.
Why Use REST API Featured Image?
When developing applications or themes that rely on the WordPress REST API, accessing the featured image typically requires an additional request for each post. This can be time-consuming and may negatively impact site performance. REST API Featured Image addresses this issue by including the featured image URL directly in the REST API response, saving you time and resources.
REST API Featured Image Field:
– <code>featured_media_src_url</code>

REST API Featured Image

Enhance your WordPress REST API by adding a featured image URL field directly to API responses, improving performance by eliminating extra requests.

GP routing – WP compatible REST API vs REST API Featured Image