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.

Enrico Sorcinelli

JSON REST API and XML-RPC API are powerful ways to remotely interact with WordPress.
If you don’t have external applications that need to communicate with your WordPress instance using JSON REST API or XML-RPC API you should disable access to them for external requests.
In the standard WordPress installation JSON REST API and XML-RPC API are enabled by default. 
In particular the REST API is turned on also for unlogged users. This means that your WordPress instance is potentially leaking data, for example anyone could be able to:
<ul>
<li>copy easily your published contents natively with the REST API (and not with a web crawler);</li>
<li>get the list of all users (with their ID, nickname and name);</li>
<li>retrieve other information that you didn’t want to be public (such as an unlisted published page or a saved media not yet used).</li>
</ul>
Even if you could do the stuff by writing your own code using native filters, this plugin aims to help you to control JSON REST API and XML-RPC API accesses from the administration panel or programmatically by a simple API filter.
<h3>Basic Features</h3>
<ul>
<li>Disable REST API interface for unlogged users.</li>
<li>Disable JSONP support on REST API.</li>
<li>Add Basic Authentication to REST API.</li>
<li>Remove REST <code><link></code> tags, REST <code>Link</code> HTTP header and REST Really Simple Discovery (RSD) informations.</li>
<li>Setup trusted users, IP/Networks and endpoints for unlogged users REST requests.</li>
<li>Change REST endpoint prefix.</li>
<li>Disable XML-RPC API interface.</li>
<li>Remove <code><link></code> to the Really Simple Discovery (RDS) informations.</li>
<li>Remove <code>X-Pingback</code> HTTP header.</li>
<li>Setup trusted users, IP/Networks and methods for XML-RPC requests.</li>
<li>Show user’s access informations in users list administration screen.</li>
</ul>
<h3>Usage</h3>
Once the plugin is installed you can control settings in the following ways:
<ul>
<li>Using the Settings->REST XML-RPC Data Checker administration screen.</li>
<li>Programmatically, by using <code>rest_xmlrpc_data_checker_settings</code> filter (see below).</li>
</ul>
<h3>API</h3>
<h4>Hooks</h4>
<code>rest_xmlrpc_data_checker_settings</code>
Filters plugin settings values.
<pre><code>apply_filters( 'rest_xmlrpc_data_checker_settings', array $settings )
</code></pre>
<code>rest_xmlrpc_data_checker_admin_settings</code>
Filter allowing to display or not the plugin settings page in the administration.
<pre><code>apply_filters( 'rest_xmlrpc_data_checker_admin_settings', boolean $display )
</code></pre>
<code>rest_xmlrpc_data_checker_rest_error</code>
Filter JSON REST authentication error after plugin checks.
<pre><code>apply_filters( 'rest_xmlrpc_data_checker_rest_error', WP_Error|boolean $result )
</code></pre>
<code>xmlrpc_before_insert_post</code>
Filter XML-RPC post data to be inserted via XML-RPC before to insert post into database.
<pre><code>apply_filters( 'xmlrpc_before_insert_post', array|IXR_Error $content_struct, WP_User $user )
</code></pre>

REST XML-RPC Data Checker

REST XML-RPC Data Checker allow to check JSON REST and XML-RPC API requests and grant access permissions.

GP routing – WP compatible REST API vs REST XML-RPC Data Checker